discuss.answer
-
☆ A M B ☆
- 24,524 Posts
At this point, I would just delete that 404 resource, create a new one, and change the System Setting. While it's a curious situation and it would be nice to figure out what the problem is, it's not worth the time and trouble.
If, on the other hand, that doesn't solve the problem, then something else is at play. Permissions? Something in the core got broken during the transfer? I'd try the above first, before getting all involved in anything complicated.
Thank you @sottwell, I replaced the error_page resource, pushed to production boxes, cleared the cache folders on the boxes, and that did the trick. I don't know what the issue was, but it works now. Thank you.