search needs 4 letters - really?

Thanks for the hint.

I still don't understand why the Joomla search detects a different number of chars than the FC search.

I was not able to find ft_min_word_len on my WAMPP in any file except for my-innodb-heavy-4G.ini but changing it there did not make any difference.

hede wrote: Thanks for the hint.

I still don't understand why the Joomla search detects a different number of chars than the FC search.

It is simply different, but if want to know:

-1- Joomla standard search view (which uses the Joomla content search plugin) uses:
LIKE %someword%
which allow any word size but is very slow in large sites

-2- FLEXIcontent advanced search view, uses MATCH-AGAINST which on a full indexed column which is fast in large sites, but it will ignore words smaller than ft_min_word_len

-3- Joomla Smart search view uses a custom CODE match which is even faster, allows small words,
-- but indexing is very slow on large sites,
-- the search DB tables tend to become very big
... using smart search in large site is not best option , flexicontent search view will do better, but in very larges site it maybe desirable to use other solutions ...

hede wrote: I was not able to find ft_min_word_len on my WAMPP in any file except for my-innodb-heavy-4G.ini but changing it there did not make any difference.

OK i have updated the FAQ article ...

After changing the value run in phpmyadmin
REPAIR TABLE ppp_flexicontent_items_ext
REPAIR TABLE ppp_flexicontent_advsearch_index

this will make the search indexes to recreated/updated

Thank you very much! Your skills and support are phenomenal!

I will have a site with 50.000 fc items. Is the fc search a good option for that size? I dont know how to break down "small", "large", "very big" sites ... Thank you.

Hello,

yes but do not add many filters in the search / category views

Thanks again - but I have to ask again ... what are "many" filters? 5, 10, 50? I will probably need 20 filters.

Hello,

that is a lot,
you can test ... performance

also you may want to enable the debug/information statistics in FLEXIcontent component configuration to see details about effect in performance