- Issue created by @MarelPup
Experiencing the same behavior here. Our content author raised this to the devs recently. Not sure when this started occuring.
I am still experiencing this issue.
A workaround was for us to manually delete the URL alias associated the page A. After flushing the cache, the redirect was working correctly.
I was going through the same issue, I think the redirection for path aliases is not working with this module, so i guess when you are trying to redirect from an aliased path, let assume from /a to /b it will not work but if try to add the redirect with the node ids like from /node/1 to /node/2 the redirection will heppen and your unpublished content can be redirected to a published content as per your requirement.
But if you want to add the redirections from alias to alias then you can try the patch given in comment number #142 → of this → issue.
I think this will resolve the problem you are facing now Please let us know whether it's working for you or not.
Thanks