flyingpylon

Good news… an update to WP Rocket (v2.9.1) fixes the problem.

https://wp-rocket.me/changelog/

I can verify that it works for me.

I’m having a similar issue with 4.7.6. I am also a Pro user, but came here to see if anyone else is having the same problem.

On my site, the issue occurs when I have WP Retina 2x and WP Rocket activated at the same time. On posts or pages that contain images in the content area or sidebar, only part of the HTML is sent to the browser so only a blank white page is displayed. On pages without images in the content area or sidebar, everything works fine. This includes featured images, for example both archive pages and posts with featured images work as long as they do not have images in the content area or sidebar.

Here is an example from the PHP error log:

[Tue Dec 27 12:49:38.910114 2016] [proxy_fcgi:error] [pid 24285] [client 127.0.0.1:53723] AH01071: Got error ‘PHP message: PHP Fatal error: Call to undefined function wr2x_getoption() in [removed]/wp-content/plugins/wp-rocket/inc/front/plugin-compatibility.php on line 169\nPHP message: PHP Fatal error: ob_end_flush(): Cannot use output buffering in output buffering display handlers in [removed]/wp-includes/functions.php on line 3673\n’

When I deactivate either WP Retina 2x or WP Rocket, the problem goes away.

Hope this additional info helps. If this is totally unrelated to the original poster’s issue, then my apologies for jumping into the thread.

To resolve the problem, I went ahead and commented out lines 204 and 572 in ms-robotstxt-manager.php.

//if ( $get_blog_path != "/" ) { $readonly = 'readonly="readonly"'; }

I think your plugin is incorrectly assuming that:

• Sites with a path that is anything other than “/” are not mapped
• That there is no way for a site in a subdirectory to have its sitemap or robots.txt file appear in the root of the site (perhaps it could be called a virtual root)

Other than that, it’s a great plugin. Thanks for creating it.

I just noticed that I’m having the same problem. The following thread says that it may be fixed in the development version:

https://www.ads-software.com/support/topic/settings-do-no-stick

Personally, I will need to wait for the released version.

+1 for the ability to disable the default CSS.

I am wondering the same thing. There are lots of reasons you might want to exclude certain pages.

Also, is there any documentation for the filters that are available?

Thanks for the quick fix! Seems to work great.

I’m seeing this problem too, but XMLRPC does seem to be installed and working on my Dreamhost site. For example, I am able to log in and view/edit posts via the WordPress Android app.

I am using WP 3.2.1. The errors are not a real problem for me, but I saw this thread and thought I’d mention that enabling XMLRPC doesn’t seem to be the issue.

Is there really nobody that knows anything about this problem?

bump… surely I’m not the only one to have this problem?