hard to say, here are a couple of remarks/ questions;
* does this break your front-end or your wp-admin?
* check the PHP errorlog for relevant errors
* make sure you have no “competing” plugins active, meaning make sure not to have plugins that also do JS/ CSS/ HTML optimization
* could be a plugin conflict, try enabling AO when all other plugins are deactivated?
frank
Hello. Some quick responses:
* does this break your front-end or your wp-admin?
yes, both
* check the PHP errorlog for relevant errors
nothing noted
* make sure you have no “competing” plugins active, meaning make sure not to have plugins that also do JS/ CSS/ HTML optimization
All other optimization plugins deactivated/removed
* could be a plugin conflict, try enabling AO when all other plugins are deactivated?
The plugin WP Preloader seemed to break when enable. Site is online now with plugin activated, but I would not think that the above mentioned plugin should break it.
-
This reply was modified 6 years, 7 months ago by
RobAdams.
Ugly .. is WP Preloader available here on wordpress.org?
Looking through the PHP errors, even today looks like there may be some remnants.
[30-Sep-2019 13:35:50 UTC] PHP Fatal error: Uncaught Error: Call to undefined function wp_hash() in /home/XXXXXXXXXXXX/public_html/wp-content/plugins/autoptimize/classes/autoptimizeMain.php:129
Which refers to this line in that file:
if ( ! defined( ‘AUTOPTIMIZE_HASH’ ) ) {
define( ‘AUTOPTIMIZE_HASH’, wp_hash( AUTOPTIMIZE_CACHE_URL ) );
}
given wp_hash is a core wordpress function, the only conclusion I can make is that your site is somehow broken I’m afraid .. :-/
That is a very general response. Looked to me that one of the core functions that was being called from this plugin was corrupt or missing. Upon investigating it I discovered that the wp_load file was missing. So now I have the file back and minus the above php error, it still breaks.
Well, that general response lead to you discovering things indeed were broken, so it seems general can be good too, no? 😉
re. “it still breaks”; based on one of your earlier replies breakage was caused by a conflict with “WP Preloader”? any news there?