-
Notifications
You must be signed in to change notification settings - Fork 61
UrlTracker won't redirect to new URL after pages has been renamed #69
Comments
Thank you very much @abjerner for the detailed bug report 👍 |
Hi Stefan and thanks for a quick answer, Here is a ZIP of the test solution: The username for the backoffice is |
Thanks! I'll get back to you about it today! |
Try v3.6 :-) |
Sorry for not being able to test and answer sooner. The fix works like a charm - thanks a lot ;) 👍 |
I don't think this fixes the issue (or potentially introduced a new issue for Umbraco 7.1.2). I've uploaded some images that explain the problem but here is the gist:
|
I can't tell whether this relates to one of the existing issues, so here goes.
I have a client with a solution running Umbraco 6.1.6 and UrlTracker 3.5. The solution uses an Azure SQL database. If I rename a page, the old URL isn't redirecting the user to the new URL.
To test this further, I tried setting up a fresh installation of Umbraco 6.1.6 and UrlTracker 3.5. This time with a SQL CE database though.
The content tree looks like:
The page
Hello World
was originally namedHej med dig
, but accessinghttp://urltracker1.omgbacon.dk/hej-med-dig.aspx
just returns a 404 error as if UrlTracker wasn't installed.The same is the case for the page
This is definitely a page
under the other site. The page was originally namedThis is a page
, buthttp://urltracker2.omgbacon.dk/this-is-a-page.aspx
also just returns a 404 error.Both these pages are direct children of a site node (with configured host names). If I change the name of a node, that is a descendant, but not a direct child, it appears to be working correctly.
For all three pages, a redirect is saved to the database, and visible in the dashboard. The difference seems to be that for the direct children, the site is set incorrectly. If you see the screenshot below, the second and third entries have the site set to the node that I edited, whereas for the first entry, the site is set correctly.
I have enabled logging, but there doesn't appear to be anything related to UrlTracker for the redirects, that don't work.
The text was updated successfully, but these errors were encountered: