Custom slugs shouldn't be changed

[agilbert]

1. I have a page under About called Staff.
2. I give that page a custom slug called /our-awesome-staff.
3. I decide to move that page underneath the contact section.
4. Now the slug is /contact/our-awesome-staff. This isn't what I wanted!

The redirect still works for this kind of situation, but we should avoid rewriting these custom slugs.

[boutell]

How does a custom slug stop being custom, if ever? Is there any way to take that decision back? Is it a boolean that stays stuck on 'true'?

My current rules of thumb aren't 100% perfect but most of the time they do what is wanted.

I could adjust it to be more conservative. Something like "if the current slug consists of the old parent's slug plus the slugification of the current page title, we can update it automatically, otherwise we mustn't."

Thoughts?

[agilbert]

Right, the conservative approach makes sense to me. If the slug of the page matches the straight slugification of its position in the page tree, then it is eligible for renaming.

Otherwise, leave it alone.

This should accommodate most, if not all, scenarios.

[geoffd]

Check each section of the permalink and preserve anything that was changed.