Must be 'Menu' class?

[gvanto]

Must be 'Menu' class?

[Mihai-P]

Yes, you can name the model in any way you desire. The point of this behavior is that you can attach it to any model and it makes the model work with nested sets.

I use it as product categories, website menus, a restaurant menu (first level are the times of day, the second the categories, the 3rd level the meals), etc. None of my models are actually called "Menu".

[Mihai-P]

Depends on the requirements, sometimes the products table have a category_id field (when products belong to 1 category only) or with a category_product relationship table when a product can belong to multiple categories.

[gvanto]

Awesome thanks @Mihai-P this what I was hoping for ...

If you don't mind can I ask how you link your products to product categories? I have a model called BlogSite (resembles a blog/website) which I want to categorize and have it listed under a directory with something like /directory/{cat_level_1} and /directory{cat_level_1}/{cat_level_2} which lists the appropriate blogSites.

[Mihai-P]

I have not done that, but you could try using the sluggable behavior http://www.yiiframework.com/doc-2.0/yii-behaviors-sluggablebehavior.html .

[gvanto]

Cool thanks will check it out. How if I may ask do you link your products to categories?

…

On 3 Oct 2017 10:27 pm, "Mihai-P" ***@***.***> wrote: I have not done that, but you could try using the sluggable behavior http://www.yiiframework.com/doc-2.0/yii-behaviors-sluggablebehavior.html . — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#113 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH_CtnSoYXnRzOjNrLO01dKIZe9sSvh4ks5sopitgaJpZM4Pqvjg> .

[gvanto]

OK thanks much thought that might be case just wanted to confirm :D