How to make it work on WP 4.3+

  • Open the plugin in the WordPress Plugin Editor and find half way down these lines:

    
...
		static function configure_plugin() {
            if ( version_compare( get_bloginfo( 'version' ), '4.2', '>=') ) {
                self::debug( 'Not yet qualified with this version of WordPress. Bypassing UGL.' );
                return;
            }
...

    Then simply delete the lines 

    
if ( version_compare( get_bloginfo( 'version' ), '4.2', '>=') ) {
      self::debug( 'Not yet qualified with this version of WordPress. Bypassing UGL.' );
      return;
}

    Save the file and it should start working again.

Viewing 10 replies - 1 through 10 (of 10 total)

  • Thanks RavanH!

    Can someone update the plugin with this change?

    Ben Linders

    Looking at this for 30 seconds leads me to believe that only the author can do that, and he hasn’t for awhile….

    Thanks for the heads up!

    Since deleting this line I get this at debug.log:

    Use Google Libraries: WordPress appears to be requesting a non-standard version of swfobject (version 2.2-20120417). Using version provided by WordPress to ensure compatability.

    Is it ok?
    My WordPress version is the latest (4.7.2).

    Please let me know.
    Thanks!

    • This reply was modified 7 years, 9 months ago by catmaniax.
    Thread Starter Rolf Allard van Hagen

    (@ravanh)

    Hi @catmaniax I have no idea… Any reason why your site would be using swfobject at all?

    Hello @ravanh

    I modified the code as you mentioned in your comment. I’m currently testing this plugin in localhost to see if this plugin is compatible or not. How can I check if this plugin is working or not? I’m using latest WP (4.7.1).

    Thanks

    Thread Starter Rolf Allard van Hagen

    (@ravanh)

    Hi @ayush4450 you can look the source code of your front page (for example) by pressing the keys Ctrl+U while having that page open in your browser. Then you can search through the source code by pressing Ctrl+F and type “google” (without the quotes) … this way, you may find a line like

    
<script type='text/javascript' src='//ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js'></script>

    which means your site is using the jQuery library (because your theme or a plugin needs it). If your site is not using jQuery, you may find other libraries this way. In any case, it means the Use Google Libraries plugin successfully forces WordPress to use the one hosted by Google.

    If you do not find anything hosted on googleapis.com then either the plugin is not working or your site does not need any libraries.

    To find out, you can search through the source code for libraries like “jquery”, “prototype”, “swfobject” or “scriptaculous”. If they are there, but hosted on your own domain, then it means the plugin has not successfully replaced them by the Google hosted ones.

    This can happen because (1) the Use Google Libraries plugin is failing for some reason or (2) the libraries are not embedded correctly by the plugin or theme that needs them. You’ll have to dig into the code (and error logs maybe) to find out what is going wrong…

    Hello @ravanh

    Awesome, I checked the source code of my site and guess what. I found this
    <script type='text/javascript' src='//ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js'></script>

    So it means this plugin is working perfectly on local host and I can install it on my live site.

    One more question, I this one is off topic. I want to add leverage browser cache code. So do I need to add it into parent directory (public_html) Or Can I add it into my domain directory (I’ve hosted 5 websites on my hosting account)

    Thanks for the help.

    • This reply was modified 7 years, 9 months ago by Ayush.

    The plugin will work fine on WP 4.7.3, just modified the main plugin PHP file and tested on local dev.

    Plugin Author Jason Penney

    (@jczorkmid)

    Plugin now works fine without edits. Sorry for the way too long delay. It’ll need to be updated again at 4.8.

    Before these checks the plugin would occasionally hit up against core changes and break peoples sites entirely. More than once it was a last minute change that went in between the beta and the release, so even thought I tested the heck out of it, it still ended up breaking sites.

    It took more time to deal with the angry emails than to fix in most cases.

    That’s great, it’s back from the dead! ??

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘How to make it work on WP 4.3+’ is closed to new replies.

Tags