Blank web page if don't view after saving

I'm having a problem with blank pages appearing if the user saves but doesn't hit view before trying to view it anonymously. Basically, the editor goes in and makes a change then saves the page. A non-logged in user hits refresh to see the changes, but gets a blank page (no source code, no 404, just blank). From that point on, all pages you try to access will be blank.

The only way to restore the blank page is clear cache, refresh URIs, clear cache. Then save and view.

I've been through all the posts for blank pages, but none of those match my issue and the solutions have done nothing.

I am on Revo, 2.4.0. Default ModX .htaccess. No errors in either the ModX log or host log (BlueHost, VPS 0 Apachie 2.2.27, php 5.4.28, MySQL 5.5.46). Database seems fine. Extras installed are Simple File Upload TV, Quickstart Buttons, and TinyMCE - nothing else. This is a client site for internal use, so I can't really share any URLs.

Is there anything I'm missing here? It's alot to ask the client to remember to push two buttons.

Thanks.

Okay, just a little more digging. I do not understand caching, but this appears to be related to caching. If I clear the cache through the manager, the pages disappear. If I uncheck "Empty Cache" and "Cacheable" the page stays up - though the changes never show.

I've now found that I can bring back any page that has disappeared by selecting Manage > Clear Cache > Refresh URI, then View. After that, it will appear fine even if people are logged out.

It sounds like it might be a problem with your base href statement.

In the head section of every template you should have this:



It you have multiple front-end contexts, it should be:




Is there anything useful in the MODX error log?

This might also help: http://bobsguides.com/blog.html/2015/11/16/the-modx-white-screen-of-death/

Quote from: BobRay at Nov 17, 2015, 04:11 PM

It sounds like it might be a problem with your base href statement.

I only have one context, but tried both versions just in case - no luck. Lets it with the single context version.

Is there anything useful in the MODX error log?

I only had 2 errors. One was from an issue with the template I used for the home and error pages - now fixed.

The other:


That one wasn't there yesterday. Quick online search doesn't really tell me what, if anything, to do with that. I'll look into it further.

This might also help: http://bobsguides.com/blog.html/2015/11/16/the-modx-white-screen-of-death/

I have the same symptoms - right down to having one line in the source code...but debug on returns nothing. (xdebug isn't available to me.)


Not sure what to try next.

You could try adding this to .htaccess, though some hosts will ignore it:

Fully agree with BobRay

I had the same issue recently when I was using MinifyX http://docs.modx.pro/en/components/minifyx/snippet
and clearing cache brought site back working.

I had some junk CSS that needed to be deleted. So try get error reporting showing and try to disable plugins and snippet one
by one.

The most likely culprit is a plugin attached to a Manager page event. You can disable plugins by right-clicking on them in the Elements tree. If there aren't to many, you can disable all of them, and if that fixes the problem, bring them back one at a time until the problem shows up again.

Thanks. I only have the extras...so I disabled the plugins and un-installed the one remaining extra. Still no luck.

Quote from: BobRay at Nov 18, 2015, 04:09 PM

You could try adding this to .htaccess, though some hosts will ignore it:

php_value error_reporting 999999999
php_flag display_errors On

Unfortunately, that leads to an internal server error. Maybe I'm doing something wrong though, we're a little beyond my knowledge.


Quote from: mrhaw at Nov 18, 2015, 04:17 PM

I had some junk CSS that needed to be deleted.

mrhaw - You might be on to something there, thanks. The error page has no CSS at all and isn't experiencing this problem. The pages with the problem have inline CSS plus some odd styling required for this project. That might be part of the problem. (Before anyone says anything about the "proper" way to do CSS - this install is being used so anyone can generate a responsive HTML email, email requires some highly specific styling including inline and in body.)

Thanks for the direction to look at mrhaw. I'll try redoing things with a stylesheet and see if that solves the problem. In which case, back to the drawing board. [ed. note: cwhissen last edited this post 10 years, 10 months ago.]

Well, shoot. Put proper HTML in there - no dice. Same issue. Back to the drawing board for me.

In my case the CSS was being processed and halted in error.

Have a look at this and your php.ini: https://my.bluehost.com/cgi/help/109