Blank web page if don't view after saving

Quote from: mrhaw at Nov 18, 2015, 05:08 PM

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

display_errors is on already. No errors are showing, but I don't know enough to force an error and check that it's actually reporting.

I wish I could share the site for some help, but my client agreement prevents that.

I'm wondering if I did something stupidly wrong along the way - this was my first modx install (I've done two more since that are working fine though). Or, perhaps, something changed on the hosting end that I'm not aware of. It is my client's hosting, so I don't get notified of these things.

If anyone can think of anything else to try, thanks. Otherwise...I'll think of something. Thanks for the help all.

Here are some things to try:

Delete all files in the core/cache directory
Turn off the compress_js and compress_css System Settings

If that doesn't help:

Install th UpgradeMODX extra, set the 'settings_version' System Setting to an earlier version, and "upgrade" to your current version. That will install all new copies of the MODX files and leave your content alone.

Quote from: BobRay at Nov 20, 2015, 12:41 AM

Here are some things to try:

Delete all files in the core/cache directory
Turn off the compress_js and compress_css System Settings

If that doesn't help:

Install th UpgradeMODX extra, set the 'settings_version' System Setting to an earlier version, and "upgrade" to your current version. That will install all new copies of the MODX files and leave your content alone.

Thanks BobRay. I set them up with a temporary workaround so I could set this aside until after the holiday. I take a look at your latest suggestions next week and post my results.

Quote from: BobRay at Nov 20, 2015, 12:41 AM

Here are some things to try:

Delete all files in the core/cache directory
Turn off the compress_js and compress_css System Settings

If that doesn't help:

Install th UpgradeMODX extra, set the 'settings_version' System Setting to an earlier version, and "upgrade" to your current version. That will install all new copies of the MODX files and leave your content alone.

Finally got a chance to try both of these fixes, and it's still not working. I'm at a loss here. It might be time to try it on another host and see if there's something there. Thanks for trying to help me fix this.

As a temporary fix, is there any way to force the resource to view when someone clicks save?

A plugin OnDocFormSave to redirect the user to the new resource's page in a new window should work.

Quote from: sottwell at Dec 02, 2015, 03:40 PM

A plugin OnDocFormSave to redirect the user to the new resource's page in a new window should work.

Thanks, that's definitely beyond my current capabilities though. Guess I have something new to learn!

Mine too; I spent some time trying to figure out how to move the user. Since the save is done in Javascript/AJAX and the page isn't reloaded, sendRedirect and sendForward don't do anything. I suspect it would have to be done in Javascript, but getting that into the jungle that is ExtJS and Smarty is way beyond me.

I think what is happening here is that the first view by the Manager user is caching the page, but why the first view by a non-Manager user should have the effect it does is a puzzle. So maybe we're looking at the wrong thing, we should be thinking about how to automatically generate a cache for the page upon save. Or even better, what is really going on here and why. Might be better to take this to the Slack channels http://modx.org if you aren't already there.

This may be a solution... run this in a plugin OnDocFormSave. https://gist.github.com/opengeek/ec3f885cefe17e470aa1

http://devries.jp/blog/2013/03/23/cash-in-big-with-modx-cacheing/