Hi @tfilos I was going to ask if it was nested

That's exactly it.

I partially wanted to put this here for posterity in case anyone else runs in it. Not sure why that happened

I thought I needed the nested but I don't really anymore, but not sure what someone would do if they did need it

for reference this can happen too when the tree is "broken", as in the columns that manage the hierarchy are not correct anymore, see https://github.com/lazychaser/laravel-nestedset#checking-consistency

Aha

Well, glad this is all in one place for the next guy. Appreciate it

👍

Hello mates, hope everyone is doing well basically I want to add nesting module and I successfully created now but in navigation I can't add sub menu how do created sub menu I go through docs but didn't find any resource about submenus

Hi @saeed-sikandar please share how you admin routes file is looking like for these modules

sure 👍

here is the admin route

This section is giving an example of using the sub navigation https://twill.io/docs/getting-started/navigation.html

You need to wrap your routes in groups with a prefix and then use that same structure in your navigation file

Oh wait I see services.articles, this is to be able to create articles directly attached to a service

not the same thing as the navigation organization of your modules

yes

So there wouldn't be a "articles" item in the navigation for this, since it is each service that has a link to the articles belonging to that service

yes, exactly

so, do I need to wrap article route with services prefix ?

That depends on what you're trying to achieve. Are you wanting to have Services in the top navigation, and in the secondary navigation, "Services" and "Articles". Or are you trying to have articles in the secondary navigation be a link to a listing of all articles (as in not scoped by their respective service)? I'm not sure I'm following what you're trying to do.

I think you might have mistakingly used nested modules with the purpose of nesting the navigation, but that's probably not what you wanted. if your articles can live on their own without having to be child of services (as in, at the model level with a foreign key), then you should create articles as a normal module like services (so not nested with that dot notation in the route) and instead use a route group around the articles module route

that might all be a bit confusing if you recently started using Twill, let me know if you need more clarification

basically I want one primary menu Services and all services title with their articles belonging to the specific services/cleaning/articles/ etc

ha so you definitely want services.articles for that

so right now when you go to services in your primary nav you are able to create articles for each service, right?

in secondary navigation ?

yes

yes