Given a Page tree with slugs:
- section-1
- subsection-1
- page-1
- page-2
- subsection-2
- page-3
- section-2
The path for page-2 would be "/section-1/subsection-1/page-2/". However, I
would rather it be "/section-1/page-2/", while maintaining the navigation
hierarchy. At the moment, I'm accomplishing this by setting "Overwrite URL"
to "section-1/page-2" in "Advanced settings" for page-2. But, if the slug
for section-1 ever changes, I have to manually its child pages.
I found one related discussion
<https://groups.google.com/d/msg/django-cms-developers/4DysrNgkBL4/T21ZDMzDhsMJ>
from ~2 years ago. Somebody else suggested
<https://groups.google.com/d/msg/django-cms-developers/4DysrNgkBL4/T21ZDMzDhsMJ>
using a separate app to maintain a section tree. I see that the 3.5 roadmap
<https://www.django-cms.org/en/roadmap/> includes "Multiple menus", and
there's a Menus/pagetree refactor issue
<https://github.com/divio/django-cms/issues/4597> on GitHub.
With all of that said: can any of the developers elaborate on the future of
the Page tree and Menus? Will it address the use case described above?
Thanks!
--
Message URL:
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to
django-cms-developers+unsubscr...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit
https://groups.google.com/d/msgid/django-cms-developers/072eeee5-76d5-4464-aceb-bab07f7c2bbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
