|
I have my flat catalog on No.
But when i want to add a new attribute it is saying i allready have 65 filtarable attributes.
It shouldn’t matter because i don’t need a flat catalog and therefore have it turned off.
Why is it still complaining?
I also thought it was odd it was allready complaining because i dont have that many attributes.
after some research i learned that every attribute which has either ‘is_filterable’ OR ‘is_filterable_in_search’ OR ‘used_for_sort_by’ set to >1 gets an index in the flat catalog table.
I did a select on my `inpt_eav_attribute` table
SELECT * FROM `inpt_eav_attribute` WHERE `entity_type_id`=4 AND `is_filterable_in_search`=1 AND `is_filterable`!=1
It returned 46 rows. All non user defined attributes.
Attributes like ‘news_from_date’ are set to be filterable_in_search while it isnt even off the type dropdown, multipleselect etc.
My second question:
Why do these attributes have is_filterable_in_search set to 1?
Did something mess up my table or is this default?
Can i change these values to 1 for most attributes without breaking something?
|
