Error 500 after update to version 1.3.7.4

  • Resolved relle

    (@relle)


    3 years, 9 months ago

    Hello,

    Thanks for this great plugin.

    After updating to the latest version 1.3.7.4 my site becomes unresponsive – 500 internal server error.

    I’ve rolled back to version 1.3.7.3 and everything is fine again.

    My WP install is 4.9.16

    Besides, in the settings I’ve activated the “WordPress version” meta tag” and “Remove All “generator” meta tags” though in Wappalyzer the version numbers are showing

    Please advise, cheers

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Gabe Livan

    (@gabelivan)

    @relle thanks for letting me know about a potential bug, although it seems like an isolated case as other users didn’t have the same problem obviously

    What I would want from you is to re-install version 1.3.7.4 and enable “Test Mode” so your visitors won’t be affected in any way (only you should see the 500 internal server error). Then, install and setup the “Error Log Monitor” plugin which is very useful to log other errors from any other plugin or theme.

    It should print you within the Dashboard main page (in one of the widgets), any errors related to the Asset CleanUp plugin. Can you do that and let me know if any errors are printed there?

    Thread Starter relle

    (@relle)

    Hello,

    Thanks for getting back to me.

    I’ seeing the following:

    Fatal error: Uncaught Error: Call to undefined method WP_Scripts::print_translations() in /home/username/mydomain.com/wp-content/plugins/wp-asset-clean-up/classes/OptimiseAssets/OptimizeJs.php:1112

    Stack Trace
    1.
    WpAssetCleanUp\OptimiseAssets\OptimizeJs::getInlineAssociatedWithScriptHandle(‘jquery-core’, Array, ‘handle’)
    /home/username/mydomain.com/wp-content/plugins/wp-asset-clean-up/classes/HardcodedAssets.php:207
    2.
    WpAssetCleanUp\HardcodedAssets::getAll(‘<!DOCTYPE html>…’, false)
    /home/username/mydomain.com/wp-content/plugins/wp-asset-clean-up/classes/OptimiseAssets/OptimizeCommon.php:220
    3.
    WpAssetCleanUp\OptimiseAssets\OptimizeCommon::alterHtmlSource(‘<!DOCTYPE html>…’)
    /home/username/mydomain.com/wp-content/plugins/wp-asset-clean-up/classes/OptimiseAssets/OptimizeCommon.php:169
    4.
    WpAssetCleanUp\OptimiseAssets\OptimizeCommon::WpAssetCleanUp\OptimiseAssets\{closure}(‘<!DOCTYPE html>…’, 9)
    [internal function]:0
    5.
    /home/username/mydomain.com/wp-c in /home/username/mydomain.com/wp-content/plugins/wp-asset-clean-up/classes/OptimiseAssets/OptimizeJs.php on line 1112

    Plugin Author Gabe Livan

    (@gabelivan)

    @relle that explains it! I just checked the code and the error is showing up because you’re using a WordPress version lower than 5. Now, I’m not saying you should upgrade because you likely had your reasons to keep the WP version you’re currently using. So, this is a bug as Asset CleanUp should have worked.

    I’ll do an update for the development version and let you know when you can download it. Thanks for reporting this and my apologies for this inconvenience! I’ll get back to you as soon as possible!

    Plugin Author Gabe Livan

    (@gabelivan)

    @relle a new tag, 1.3.7.5 was released which has the fix for the problem you mentioned. Please update to the latest version and let me know how it goes!

    Thread Starter relle

    (@relle)

    Thanks for fixing this so fast! My site is up and running again ??

    One more question: in the HTML Source Cleanup settings I’ve activated the “WordPress version” meta tag” and “Remove All “generator” meta tags” though in Wappalyzer (browser extension) the version numbers are still showing ?

    Cheers!

    Plugin Author Gabe Livan

    (@gabelivan)

    @relle I’m glad this has been fixed and it works fine now ??

    As for removing the meta generator tags, the plugin does remove them from the HTML source. Can you check if it does that? However, the feature has been completed a long time ago and perhaps things changed meanwhile and WordPress is leaving other traces and Wappalyzer detected them. I’ll check it out for sure and get back to you if I find anything. It would be a good idea to start a new topic about it to keep things organized. I’ll mark the current one as “resolved” since there is no more 500 internal server error showing up.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Error 500 after update to version 1.3.7.4’ is closed to new replies.