search : Advanced option button appears if not on home page

Hello

if you have FC Search view menu items A and B

and you set module to use menu item A

-- then when searching from module word "someword" should give you same results as when searching via menu item A (of course i mean not having any other filters active, we talk about text-search results only)
after the search list is presented then of course the user can select more filters, but i don't mean this, i mean before any filters are used , the search result should be same (please note the parameter "how to use search", e.g. show exact etc, as this will yield different results)

Yes, that's exactly what i expect :

FC search Module A is link to FC search menu item A

and

FC search Module B is link to FC search menu item B

For testing, i deactivated the B menu and module. But it has no change.

The difference are on the NUMBER OF RESULTS (type filter of the fc search menu item not taken in account) and on the DISPLAY of results (some fields, like category, not displayed).

I make exactly the same research. More : i enter "test" in the module text field, i obtain that :

[attachment=2:2qqga2st]<!-- ia2 -->a.jpg<!-- ia2 -->[/attachment:2qqga2st]
[attachment=1:2qqga2st]<!-- ia1 -->b.jpg<!-- ia1 -->[/attachment:2qqga2st]

and, in the result page, i RE-click on the "search" button, and i obtain that (same result as if i use the menu link):

[attachment=0:2qqga2st]<!-- ia0 -->c.jpg<!-- ia0 -->[/attachment:2qqga2st]

Hello

so for some reason the configuration used is different

you may send me a PM for this,

include:
-- the 2 frontend links (search menu item and page with the search module)
-- FC search module id and FC search menu item id (and state the name of the menu that this menu item is placed)

Hello

the difference is because
the search coming from module does not limit search to FLEXIContent items only,

so it lists content from other site areas too e.g. from section "weblinks" too

temporary workaround disable search plugins from other areas: com_weblinks, com_content, etc

Hi and thank you for your answer...

The solution you gave me doesn't solve problem as i need to make search in specific Flexicontent categories (e.g. training, tutorial, etc.).

And as you can see the result display doesn't feet the menu item parameters (filters, fields to displays in results...).

Sorry for all this problems, but it's a real need, and, i thing, an important function...

Have a good day!

Hi...

So is there a solution to create a FC search module field which can search on specific item type (i said category, my mistake, i want a type filter)?

Any workaround to my display problem?

Sorry for being insistent, but it's a real need for me and the site will be available next week...

Thank you!

did you create a link to search (not display) and link your module to item id ?
after you can check more option (more option in search link)
if it doesn't existe and you realy need you can paid for specific dev
regards

Hello

1. i have noted what needs to be done,

2. yes it is an annoying inconsistency,
it should be little work to fix this

i will be fixing along with a couple of other improvements for search view
(1.) warn if a word is ignored
(2.) enable text-search auto-complete like we have already in category-like views

PS: you can install v2.1.0 r1774 has other search view related improvements and bugfixes (for all reported issues) also includes performance too in regards to FACETED filters and backend search index listings

Thanks for your answers, i didn't saw them before.

My english isn't perfect, so i'm not sure to clearly understand :

The noticed bugs should be corrected in a future version, and the v2.1.0 r1774 give some improvements (which one?) on research, but not for the bugs mentioned... that's it?

Thank you and have a good week!

Hello

please use v2.1.0 r1778,

www.flexicontent.org/downloads/l ... rsion.html

it has fixed all known issues for search view / filtering,

-- this last issue of different configuration when coming of module will be address on next public package