WordPress.org

Ready to get started?Download WordPress

Forums

Quick Page/Post Redirect Plugin
[resolved] /?ver=pprjq1 ?!?!?! 5.0.2 comes with extra page requests (9 posts)

  1. four2oh
    Member
    Posted 1 year ago #

    After most recent upgrade to 5.0.2 (on WP 3.3.2), i've noticed that after every page request is an additional hit to:

    http://mysite/?ver=pprjq1

    which returns

    //not set

    i see that in your code it's related to jQuery_Cache function, which i'm guessing is your current hack to fix the jquery conflicts.. But it adds up to duplicate pagehits on my webstats now..

    please fix! The plugin wasn't creating additional HTTP GETs like this before.

    http://wordpress.org/extend/plugins/quick-pagepost-redirect-plugin/

  2. prophecy2040
    Member
    Plugin Author

    Posted 1 year ago #

    Yes, this has to do with the jQuery fix.
    We will be putting out a fix soon, but probably not before Dec 1st. We don't want to have too many updates at one time - so we are holding off for a few weeks now that the major plugin bugs have been fixed.

    I suggest that you just edit the plugin code and comment out the enqueue script. That way you won't have to wait, and when we update it will just silently replace your fix.

    Here is what you do:

    1. Go to the plugin editor and select the Quick Page Post Plugin
    2. edit line 149 - looks like this:
      add_action( 'wp_enqueue_scripts',array($this,'ppr_do_jQuery'), 1, 2);
    3. comment out the line by adding // in front of it, like so:
      //add_action( 'wp_enqueue_scripts',array($this,'ppr_do_jQuery'), 1, 2);
    4. Update the file.

    That will stop the jQuery from outputting the empty script call.

    Warm regards,
    Don

  3. four2oh
    Member
    Posted 1 year ago #

    Thanks for the quick replay and fix!

    \m/ You Rock \m/

  4. prophecy2040
    Member
    Plugin Author

    Posted 1 year ago #

    You are very welcome!

    Warm regards,
    Don

  5. photoMaldives
    Member
    Posted 1 year ago #

    Hi prophecy2040

    I'm seeing this in my logs too, and wondered what it was - a quick google brought me here.

    Has the fix been rolled out yet, or should we apply manually ?

  6. baeldung
    Member
    Posted 1 year ago #

    Hi,
    I am seeing the same issue - is the manual fix required or should I wait for an update of the plugin?
    Thanks.
    Eugen.

  7. knappen
    Member
    Posted 1 year ago #

    Thanks prophecy2040!

  8. netigate
    Member
    Posted 1 year ago #

    +1

  9. prophecy2040
    Member
    Plugin Author

    Posted 1 year ago #

    The newest version, 5.0.3 resolves this issue without the need to fix it manually.

    Regards,
    Don

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic