PackageNotFoundManager.config values setting to 0 automatically
Hi all,
I was really pleased to stumble across this package as I'm using Umbraco with multiple websites and needed to set custom 404 pages for all of them.
After some teething issues, I got it working but the values stored in PageNotFoundManager.config other than the first one, seem to set themselves (not sure yet what's causing this) to 0 after some amount of time, meaning all websites start pointing to the same 404 page (not what I want). I'm not exactly sure what's causing this, but I thought I'd ask if anyone else has encountered this and, if so, whether they managed to fix it.
I had a similar issue a year ago. The problem was, that the config file was in source control with id 0. Only on live environment I had set the 404 page to the correct node id. Because this, after every deployment to live, the id was reset to 0. Maybe this can help you?
PackageNotFoundManager.config values setting to 0 automatically
Hi all,
I was really pleased to stumble across this package as I'm using Umbraco with multiple websites and needed to set custom 404 pages for all of them.
After some teething issues, I got it working but the values stored in PageNotFoundManager.config other than the first one, seem to set themselves (not sure yet what's causing this) to 0 after some amount of time, meaning all websites start pointing to the same 404 page (not what I want). I'm not exactly sure what's causing this, but I thought I'd ask if anyone else has encountered this and, if so, whether they managed to fix it.
Thanks in advance, Ed
Code examples:
goes to
Hi Edward,
I had a similar issue a year ago. The problem was, that the config file was in source control with id 0. Only on live environment I had set the 404 page to the correct node id. Because this, after every deployment to live, the id was reset to 0. Maybe this can help you?
Best, Sören
Hi Sören,
Thanks for your reply. I'll keep that in mind moving forward - hopefully keeping the source control up-to-date will solve the problem.
I'm currently just waiting to see if it does it again! Fingers crossed it won't...
Kind regards, Ed
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.