site not showing up

It seems to me as if you must have your site set to not allow public access somewhere. Either in the document settings or the site start and error pages or the site offline setting. I’m not sure how it happened, but it seems like the only reasonable explanation.

You haven’t made any changes to the standard MODx .htaccess file, right?

If you PM me and give me access to your manager I’ll look around and see if I can figure it out for you.

check your PMs.
right, no changes to htaccess.

Hmm...

Well your System Events log was chock full of Parser errors (almost 2000 pages of them!). They are all Too Many Forward attempt errors like this one:



And your 500 Server Error page also remarks that there was an additional 500 error attempting to forward to an error document.

All of which makes me surmise that what is happening is that your pages are being considered off-limits to the public (despite the fact that they seem to be set up correctly as far as I can tell), which then forwards to your 401 page, which is also off-limits to the public, etc. And given that you can see these pages in the Preview window of the Manager (or in another tab of a browser that has a manager session open), this definitely seems like an internal MODx problem to me.

I’m going to keep sniffing around and see what I can figure out, but if any of you coders has any idea what might cause this please chime in so we can get it corrected.

Aha! I think I found the problem. I disabled the PageHitCounter Plugin and the site now loads.

I don’t actually see why that Plugin would cause this, but somehow it seems to have been the root of the problem. I also disabled the Template Switcher Plugin and changed your suffix to nothing (in case you want to restore those changes). You were getting 1292 errors every time you tried to load a page outside of the Manager (over 2 megs of errors per page load), which also seems like something that should never happen under any circumstances and might need looking at...

Let us know if you have any other issues.

Check the settings database table and the value of site_status

Wow, I do remember trying to install the PageHitCounter plugin but never getting it done successfully, but that must have been it. Thanks so much Zap!

You’re very welcome. Glad this issue is resolved. Besides the fact that it was obvious you were pulling your hair out over this (and I certainly know how that feels), it’s important to figure these things out in case they ever happen to anyone else.

Quote from: ZAP at Jan 01, 2007, 08:29 PM

I don’t actually see why that Plugin would cause this, but somehow it seems to have been the root of the problem. I also disabled the Template Switcher Plugin and changed your suffix to nothing (in case you want to restore those changes). You were getting 1292 errors every time you tried to load a page outside of the Manager (over 2 megs of errors per page load), which also seems like something that should never happen under any circumstances and might need looking at...

I’m not seeing exactly why this plugin would cause the problem either, but, the real problem is definitely with the $modx->messageQuit() function, which apparently has been changed to try and continue processing MODx tag content when a manager is logged in, or try and load/forward to the error page otherwise. This is the cause of the error loop where 2 megs of errors are being reported, and I am working to completely change this behavior as soon as possible. Right now, we are using this as an error handler and then trying all kinds of things that may have been the original cause of the error in the first place (i.e. trying to connect and log to database, trying to parse MODx tag content, trying to forward to another MODx page). This goes back to a similar recent issue where an unreliable database server would often trap MODx into a loop like this trying to get a db connection to log the fact that it couldn’t get a database connection.

I remember seeing that post and your comments on how the error handling is being revamped for future versions, so I think this is just one of those things to keep in the back of your head to remind you that you’re doing the right thing by reworking that logic.

I just tried to log back in to this site to see if I could figure out why this Plugin was causing the problem, but arty has since removed it. So I can’t say for sure why this would cause such a meltdown, but my suspicion was that it was being called on an incorrect System Event or the Plugin configuration was corrupt or wrong. It only does its query when you are not logged into the Manager, so that’s where the trouble probably originated.

It’s a shame that arty had to suffer so long on this one, but at least it’s resolved now.

Hi guys,

I get about 2000 to 3000 "Too many forward attempts." everyday since I upgraded to MODx 0.9.5 (rev 2106). I DO NOT have any plugins installed/running. I just had TinyMCE, but disabled that too. Still get those errors anyway.

Is this a serious issue? Why could this be happening? Is there a fix for the same.

regards + best wishes for the new year.
-Raavi