Hi I have 2 contexts and need to set one page as 404 error page for both (without having to use redirects or links or anything else).
As I can see the page is working only within the context its placed. Can't get the logic of this behavior as 404 page id is unique for any context.
May be I missed something?
[ed. note: sladdals last edited this post 12 years, 10 months ago.]
Is the 404 page published and not protected by any ACL entries?
Do all users have a Context Access ACL entry giving them access to each front-end context?
Have you tried creating a weblink or symlink for the page in the other contexts?
The page is published and do not protected.
Weblink opens the page from any context, symlink works only within the same context.
Keeping the error page in one context, then creating the Weblink in another and setting the Weblink as a custom error page setting for this context do not solve the issue. The custom context error setting seems to be overriden by system error_page setting.
I believe there's a setting to make symlinks work across contexts.
Steve
I think error page should work across all contexts without having to set symlinks or weblink. It is just the page and as every page It has a unique id and could be accesed from any context.
Are your error and unauthorized pages in the web context?
Do all users, including the (anonymous) user, have a Context Access ACL entry giving them access to *all* front-end contexts?
I think the problem is that when a resource isn't found during the request process, MODX calls the context object's makeUrl() method and the context object doesn't know about resources in any other Context.
I think I would just have two identical 404 pages, one in each context.
