Hi Stephen and Mathias,
Thanks for your reply and that's really good suggestion.
Currently I think customizing @processor_for(Category) is better for my
current scenario.
Use Category as location is higher level controller I think very useful
when all products are involved in just on
Hi,
I’d rather not use a variation option to store the location:
- it can be costly to retrieve every one of them when filtering products
for a given category;
- it will display on the product page and can be redundant if you have a
dropdown elsewhere.
Instead, I’d rather use
Might even be able to do something simple using locations as categories.
On Fri, May 29, 2015 at 11:12 PM, Mathias Ettinger
mathias.ettin...@gmail.com wrote:
Hi,
I’d rather not use a variation option to store the location:
- it can be costly to retrieve every one of them when filtering
Indeed,
Category can be the (already existing and SQL cheaper version of the)
ManyToMany field I was referring to. You can use the PAGE_MENU_TEMPLATES
checkboxes to make sure they don't appear in the menu if you don't want
them to.
Le samedi 30 mai 2015 08:17:57 UTC+2, Stephen McDonald a
