Has anyone ever experienced their secured pages stop working out of the blue? All resources that I secure via the access permissions tab now throw up a 500 error, and I don’t get a parse errors in the manager. Does this even sound like it could be an IIS problem?
-
☆ A M B ☆
- 24,524 Posts
Oddly enough, I’ve been noticing a few of these questions suddenly show up on the forums. Something has just been done to servers, I suspect.
So in summary:
The bad news is no one has a fix for this yet.
The good news is I am not alone with this issue.
I guess I will have to live with that for now.
-
☆ A M B ☆
- 24,524 Posts
The thing is, I don’t see how that could have anything to do with it... the security system is strictly an internal MODx thing. The server shouldn’t know or care if a document is secured or not. A page is requested, the request is passed on to index.php with the ID or the alias, and MODx checks to determine if the visitor has viewing rights or not. If not, the Unauthorized Page (as specified in your site’s Configuration; document #1 by default unless you installed the demo site content) is served.
I suppose it could be a problem if you’ve deleted the documents that are supposed to be your Error (404) page, and your Unauthorized page. Check your Configuration and make sure those documents do exist.
The first thing I checked was to make sure the docs existed. I am completely lost on this one.
-
☆ A M B ☆
- 24,524 Posts
Does it cause the error if the user is logged in?
-
MODX Staff
- 10,725 Posts
Can you go directly to the page set as the unauthorized_page? Or is this also a 500? If it is a 500, then you simply have something on your unauthorized_page that is crashing your web server and causing it to return a 500 error.
I can go directly to all me error pages. The host uses a "web.config" file for error page redirects, user friendly URLs, etc. I have that page setup correctly, including the user friendly URLs.
My client told me that nobody could get to the secured pages anymore (even while logged in), as they would get the error page I created telling them this page doesn’t exist. When I went into the web.config file and commented out the redirect for 500 errors and then tried to click on a secured page (logged in or out), I now would get the standard browser generated 500 error.
Just to clarify:
This happens logged in or out.
With the web.config redirect, I get my error page for missing pages (which is also set for 500 errors). Without the web.config redirect, I get the browser generated 500 error.
I have a bad feeling the only option I have left is to do a fresh MODx install and hope it works.
