It will regenerate, but it's advisable to leave it alone, because I can't guarantee it would regenerate how it was before, so could break some URLs. E.g. if you have two resources that would naturally have the same moniker, but one had to be suffixed due to that conflict, they could flip around. Or if we've changed the algorithm (we have), they might come out different.
Generally it is also good that old content monikers are left behind, so new content does not end up using old URLs that might have been for something completely different.
Lastly, when content is renamed, a redirect is set up inside the table, to make sure previous URLs continue to function.
Was I helpful?
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.