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
I encountered this with 2.0.0, but at a glance it seems the issue should exist in 2.1.
If I use CleanSweep separately at the root / website level and a blog located at /blog/ and want both to use the same 404 page, I don't think I have a way to distinguish whether the target page was within /blog or not. Attempts to visit a nonexistent page /blog/missingpage.html will result in the 404 page being loaded with ?target=missingpage.html.
I initially tried to resolve this by setting the 404 page for the blog to /404.html?basedir=blog, but that will then result in an erroneous URL ending in /404.html?basedir=blog?target=missingpage.html. We'll either need to test for a trailing question mark at
Trying to deal with website/blog hierarchy is always something that's been in the back of my mind. (pre-2.0.0 even!) I added 12c8163 recently to try to better handle it. I have also previously thought that setting an environment variable for each blog ID (based upon folder structure) could be a way to communicate the blog ID to CleanSweep that is then used to look up results for each blog. But simply, I don't have enough clients using CleanSweep to justify the time!
I encountered this with 2.0.0, but at a glance it seems the issue should exist in 2.1.
If I use CleanSweep separately at the root
/
website level and a blog located at/blog/
and want both to use the same 404 page, I don't think I have a way to distinguish whether the target page was within/blog
or not. Attempts to visit a nonexistent page/blog/missingpage.html
will result in the 404 page being loaded with?target=missingpage.html
.I initially tried to resolve this by setting the 404 page for the blog to
/404.html?basedir=blog
, but that will then result in an erroneous URL ending in/404.html?basedir=blog?target=missingpage.html
. We'll either need to test for a trailing question mark atmt-plugin-cleansweep/plugins/CleanSweep/lib/CleanSweep/CMS.pm
Line 123 in 5a25d75
The text was updated successfully, but these errors were encountered: