How to make a content item used as 404 page, or any other item, to be unsearchable

I'm using FC 3 Beta 6b, latest sh404SEF and Falang.

Is it possible to prevent 404 pages (both in default and translated language) to be displayed in the search results if someone searches for a term included in that pages?

Hello

try putting this content into "Archived" state

Hi,
i was having the same probleme.
i changed the Document type for 404 page.
Then i did'nt choose this Document type in my menu search parameters (Search Form: Content Types)

Hello

most complete way:

1. it is good to make item state to be "Archived"

2. For Search view
-- in your search MENU item (search module also requires a menu item, and uses it for configuration)
do not add the content type of the item to searchable types

3. For category-like views that also have text search, do this
-- assign the item to a category that you have configured to be non-linkable (* see below)
and also make sure the category is top level (no parent) and it has no direct menu items to it

(*) go to FLEXIcontent Advance Route plugin and select not to create links to the category

[Update]
- i ll make a new FAQ article

If I make the 404 page as archived, it doesn't work.
Whenever a non existent page is accessed, the default 404 Joomla page is shown and not this one.
Another negative effect is that search also stops to work, which doesn't make any sense.

I also created another type and didn't select it in the menu options.
It is still being shown in the search results, whatever plugin is enabled.
By the way, which search plugins should be enabled among these 3: flexisearch, flexiadvsearch and falang?
If more than one is enabled, then search results get duplicated.

Hello

- only enable 1 plugin of those searching Joomla content (articles),
- the searchable content types configuration (MENU item) is respected by flexiadvsearch plugin, enable only this
- flexisearch or other "content search" plugin will not respect it

Thanks, now flexiadvsearch is the only plugin enabled with "Active language only" set as Yes and "Search archived" set as No.

I created a type named __404__ and set the 404 page as the only item of this type.
In the menu, User selection is set to "No, Use all below" and the Searchable Types contain 3 different type less the __404__ one.

As I already told, the 404 page continues to be displayed in the search results! :ohmy:
Also told that I cannot archive the 404 page created by sh404SEF because then it doesn't work and whenever a non-existent page is browsed, the default Joomla 404 page is being shown.
When I archive the 404 page, the autocomplete also seems to stop working (if I enable it again, autocomplete works fine - tested this 3 times).

Additionally, when the flexiadvsearch plugin is the only one enabled, the English version of the site cannot find anything (it always gives "No records found").
The only way I can have record found in English is when I have the Falang search plugin enabled.
In English, the autocomplete still continues to retrieve only suggestions in the default Portuguese language, whatever configuration I've tried so far.

Hello

you should not enable language filtering if you are translating items via Falang ?
-- because in that case the query will return no items

are you using Falang to tranlate FLEXIcontent items (=Joomla articles) ?

If I disable language filtering it is worse, since still no English results are given and Portuguese results start to be displayed.

Yes, I am using Falang to translate menus, modules, categories and FC items/Joomla articles.
If instead of using Falang for items, I use only FC, would it be as easy for end users to insert contents in both languages, I mean, by creating/editing only a single item and translating the translatable fields via tabs?

Hello

falang data are not added to FLEXIcontent text-search indexes,
- text auto-complete will not work it needs the text-search index
- text search can work by using falang "Content" search plugin, but only in Title and description,
- field filtering will work

you can do this,
- either do not use the Falang for translating items,
- or enable the falang content search plugin,
that will allow searching in title and descriptions via a rather slow DB search query that it has
but also make sure that falang search area is allowed in our search view