It’s not unusual for the content team to need to change a slug. Particularly as we migrate out of wordpress and into Strapi, it’s an opportunity to change poorly named slugs. Obviously this can cause a problem, and so the ideal behavior would be that Strapi maintains a list of altered slugs and 301 redirects to the new slug. Is there a convenient way to make this happen?
Without it, we are tempted to build a trigger on slug fields and onto a varchar indexed table and do the 301 redirect in our own middleware. But i’d prefer not to be adding database constructs like triggers to the strapi database without it being part of strapi. Is it a case of a change request / pull request? The slug functionality works great, it would just be also great if there could be a separate list maintained where it 301 redirects rather than url-rewrites.
Any suggestions welcome. But of the 4 questions i’ve asked so far, zero have gotten replies, so expections are already quelled.
Thanks anyway,
Pete.
This topic has been created from a Discord post (1280772864001183848) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord