You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if PagePathHistory could support urlsegments so that a URL like:
/subscribe/testcoupon/
would be rewritten to:
/buy-now/testcoupon/
if the page with name subscribe was renamed to buy-now and the page's template makes use of urlSegment1 to get the value for a coupon code entered in the url.
I am curious whether you ever tried to support this or not. I expect it will be a little tricky but my hunch is that it should be doable. Let me know if you interested in supporting or not and if not, I might see about supporting it via a third party module.
Thanks for considering.
The text was updated successfully, but these errors were encountered:
PS I know there will be lots of problems to support all possible scenarios, but perhaps if only first level pages (those directly under home) were supported, we could simply strip off everything after the second forward slash and assume those are urlsegments and simply find the page that matches the ID of the page whose name was changed and then re-append all those segments as they were in the original URL. I know this wouldn't solve the problem for all setups but I bet it would handle most.
Short description of the enhancement
It would be great if PagePathHistory could support urlsegments so that a URL like:
would be rewritten to:
if the page with name
subscribe
was renamed tobuy-now
and the page's template makes use ofurlSegment1
to get the value for a coupon code entered in the url.I am curious whether you ever tried to support this or not. I expect it will be a little tricky but my hunch is that it should be doable. Let me know if you interested in supporting or not and if not, I might see about supporting it via a third party module.
Thanks for considering.
The text was updated successfully, but these errors were encountered: