Soldato
Hi,
I'm slightly updating our in house CMS's URL strucrure. Before, a page simple had a slug as follows: site.co.uk/privacy-policy - this was the same even if the page had parent and child pages and was globally unique.
My aim is have urls in the following format: site.co.uk/about/privacy-policy - that is auto generated if I set the "about" page to be the parent of "privacy policy". This is currently all working fine, even if it was a pain in arse to write and was a bit of good practice.
My question is this, when a user updates say the privacy page, which has a parent page, what would you do about the slug? I currently have it set to regenerate the URI (which I store in my db). This is fine, but it's just struck me, that updating the URI automatically poses a few potential issues:
I'm slightly updating our in house CMS's URL strucrure. Before, a page simple had a slug as follows: site.co.uk/privacy-policy - this was the same even if the page had parent and child pages and was globally unique.
My aim is have urls in the following format: site.co.uk/about/privacy-policy - that is auto generated if I set the "about" page to be the parent of "privacy policy". This is currently all working fine, even if it was a pain in arse to write and was a bit of good practice.
My question is this, when a user updates say the privacy page, which has a parent page, what would you do about the slug? I currently have it set to regenerate the URI (which I store in my db). This is fine, but it's just struck me, that updating the URI automatically poses a few potential issues:
- the page at site.co.uk/about/privacy-policy, which is potentially already indexed and linked to, wouldn't exist anymore
- the child page uri's, whilst still valid wouldn't apply (or make any sense now as the parent page's URI has changed). I could easily update these in one fell swoop, but I'd have the latter issue again, but on multiple pages