[already exists] Pass ALPHABETIC FILTER via query string

Similar to the change in the filter please consider passing the alphabetic filter via query string.

This is done already

the search box words is the variable filter=
and
the alpha-index characters is the variable letter=

Maybe you have outdated template files

Must be that. Thanks

In r1354,
i have fixed an issue in J1.5, with category filtering variables containing accented utf-8 characters and causing the pagination URLs not be generated properly.

No template changes needed

Just saw it today, we have been careful readying the change log in the SVN. We try to know when the templates are updated.

Just some more time to finish Search-index and Advanced Search index stuff, (we might include search ranges), and of course close a few more bugs and it will be final version.

We have decided that simple search index (includes search text from all searchaable fields) will also be updated via a button. The advanced search index seperates searchable text per field and allows using the category view filters in the advanced search view too, plus ranges?

Regards

Would ranges be available as moudule? how about in the category view?

Please clarify me, I didn't understand "update via button"??

1. DB table flexicontent_items_ext has a single row per item.
-- This table has a column called "search_index" which contains text from all --searchable-- fields, e.g. title and description
-- If you define some more fields, (e.g. the mark image field as searchable) then this column is not updated until you resave the items, so it makes sense to rebuild the data in this column.
-- It was usually not needed to do, so because only title and description generated searchable text

2. DB table flexicontent_search_index contains the searchable text of every --advanced-searchable-- field
-- e.g. 4 advanced searchable fields mean 4 rows per item in this table
-- this index allows searching fields separately which the old common search_index column did not allow


To answer your question about ranges,
(a) the idea is to make some filterable fields get a new parameter to display their category FILTERS as a range
(b) i have mostly finished module that can accept category FILTERs and a search box, will see if this is merged with search module, will see

Make a lot of sense now.

Yes the button is very needed, just consider multi-lingua how is this going to work.

About the search range we understand if you can't, just be strong you can do it

thanks for explain