Might be a bit out of the scope of this package but all the mechanics appear to be there so wondered if they could be re-used.
If a content item is deleted rather than moved then a "410 Gone" response could be returned. This is different to a 404 as it specifically says that content no longer exists. Handy for search engines etc.
More a nice to have than a must have but something I though might be a good addition.
I hate to bring up an old thread, but the 4.10 Gone error isn't something I want when I have a redirect in place for deleted content. I even tried recreating the page and the 4.10 still came up. That is not good. And I can definitely trace the error back to this module because of what comes up on the error page:
The UrlTracker (v1 and v2) only does stuff when the request's status is 404, so if a page is found in umbraco or a redirect is set, the UrlTracker is designed to not do anything.
I'll try to reproduce this, meanwhile maybe you could help by turning on logging and investigate what the UrlTracker logs...
Please enable logging by adding an appSetting with key="urlTracker:enableLogging" and value="true" and also set umbracoDebugMode to true.
I fixed the problem by deleting the offending records in the DB. As close as I can figure, the problem may lie in the fact that the page I deleted had a umbracoUrlName property where I was overruling Umbraco's friendly URL's. Instead of the start-here as the title would have suggested, I told it to do starthere. But the strange thing was after I deleted the page, I created a 301 redirect in URL tracker so I actually had two entries in the DB for it. The 410 from the delete and the 301 from the creation. So I'm wondering if the record order has something to do with what happened.
Return "410 Gone" Response for deleted content?
Might be a bit out of the scope of this package but all the mechanics appear to be there so wondered if they could be re-used.
If a content item is deleted rather than moved then a "410 Gone" response could be returned. This is different to a 404 as it specifically says that content no longer exists. Handy for search engines etc.
More a nice to have than a must have but something I though might be a good addition.
Cheers
Pete
Hi Pete,
Thanks for the nice suggestion, I like it :-)
It's on the todo list.
Greets
Version 1.5 is up and contains the 410 Gone response for content move to the recycle bin :-)
I hate to bring up an old thread, but the 4.10 Gone error isn't something I want when I have a redirect in place for deleted content. I even tried recreating the page and the 4.10 still came up. That is not good. And I can definitely trace the error back to this module because of what comes up on the error page:
The UrlTracker (v1 and v2) only does stuff when the request's status is 404, so if a page is found in umbraco or a redirect is set, the UrlTracker is designed to not do anything.
I'll try to reproduce this, meanwhile maybe you could help by turning on logging and investigate what the UrlTracker logs...
Please enable logging by adding an appSetting with key="urlTracker:enableLogging" and value="true" and also set umbracoDebugMode to true.
I fixed the problem by deleting the offending records in the DB. As close as I can figure, the problem may lie in the fact that the page I deleted had a umbracoUrlName property where I was overruling Umbraco's friendly URL's. Instead of the start-here as the title would have suggested, I told it to do starthere. But the strange thing was after I deleted the page, I created a 301 redirect in URL tracker so I actually had two entries in the DB for it. The 410 from the delete and the 301 from the creation. So I'm wondering if the record order has something to do with what happened.
I think the record order was the problem indeed. There should be better validation to prevent duplicate entries, which is planned for the future.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.