WordPress.org

Ready to get started?Download WordPress

Forums

Update Notifier plugin still sending email notices... (22 posts)

  1. Eric Rasch
    Member
    Posted 4 years ago #

    I installed this plugin, activated it, received my first email notice to upgrade, logged in to WP Admin to upgrade to v2.9.2, and now I'm still getting emails saying I have to upgrade 'from version abc to 2.9.2'.

    I'm assuming this is a bug in the plugin. Other than deactivating the plugin, is there anyway to make sure the plugin recognizes that I really am using the latest WP version?

    http://wordpress.org/extend/plugins/update-notifier/

  2. Jon Cave
    WordPress Dev
    Posted 3 years ago #

    I believe you must have the WP-Security-Scanner plugin running. This changes the global $wp_version to be 'abc'.

    The fix for this is commenting out line 53 in securityscan.php, the line which reads:
    add_action("init",mrt_remove_wp_version,1);

    I'm updating this plugin to include a warning about this and some stuff in the FAQ.

    Thanks

  3. Jon Cave
    WordPress Dev
    Posted 3 years ago #

    Looking at this again quickly, it seems as if this won't occur in version 1.3 even if WP Security Scan plugin is installed. This is because wp_cron is called before the init action (to which the version removal is hooked).

  4. carl_pilk
    Member
    Posted 3 years ago #

    yes i had the above problem too, didnt have security scan plugin installed.

    nice plugin, been looking for something like this.

    just a heads up duck, the link on the plugin page to your website is dead and needs updating:

    http://lionsgoroar.co.uk/wordpress/update-notifier/

  5. Jon Cave
    WordPress Dev
    Posted 3 years ago #

    Is it saying you're running version "abc"? Are you running any plugins or custom functions which might change the version?

    And thanks for the heads up.

  6. carl_pilk
    Member
    Posted 3 years ago #

    yes its saying im running version abc. Running 2.9.2. Not running any custom installation too far from standard.

    Theme: Mandigo

    Plugins:

    Akismet
    All in One SEO Pack
    Get Recent Comments
    Google XML Sitemaps
    Maintenance Mode
    My Category Order
    My Link Order
    My Page Order
    Simple Tags
    TinyMCE Advanced
    Twitter Tools
    Update Notifier
    WordPress.com Stats
    WP-DBManager
    WP-Optimize
    WP-PageNavi

    Hope you can help. Very useful plugin.

    thanks

    Carl

  7. daviddicks
    Member
    Posted 3 years ago #

    Any help on this issue, I've installed Update Notifier and am having the same issue?

    Whats the fix?

  8. Jon Cave
    WordPress Dev
    Posted 3 years ago #

    I am still unable to reproduce this (tried with the same setup as you carl_pilk), and also I am finding it hard to work out how it could happen. Update Notifier uses settings saved by WordPress itself to check if a new version is available, so I would have thought that you would also be seeing the yellow update nag in the administration area.

    It may be helpful to check what is saved in this setting to get some more information on what is going on. All the info (for core updates) used by Update Notifier is taken from the 'update_core' transient. I have a test version update-notifier-menu.php which displays the admin menu with extra info and doesn't send emails. Just place that in the main plugin directory (along with hello.php - that is Hello Dolly) and activate it (after deactivating the normal version of Update Notifier). The actual code for doing this (if you want to add this yourself instead) is: $current = get_transient('update_core'); print_r( $current );

    In the test plugin the (possibly) useful output is under the heading "Contents of update_core transient" at the bottom of the Update Notifier admin menu page.

    After doing that you could also try using the development version - link straight to the zip or go to Other Versions on the Update Notifier page - to see if there's a difference (don't see what though!)

    Sorry I cannot be of more help atm, scratching my head in disbelief mostly :(

  9. daviddicks
    Member
    Posted 3 years ago #

    Did what you recommended, I'm running the latest version of wordpress and dont get the yellow update nag.

    I had have WP-Security-Scanner previously installed but deactivated and removed it sometime ago. Dont know if this is having any effect.

    Here are the details output:

    Contents of update_core transient

    stdClass Object
    (
    [updates] => Array
    (
    [0] => stdClass Object
    (
    [response] => latest
    [url] => http://wordpress.org/download/
    [package] => http://wordpress.org/wordpress-2.9.2.zip
    [current] => 2.9.2
    [locale] => en_US
    )

    )

    [last_checked] => 1275560848
    [version_checked] => 2.9.2
    )

  10. Jon Cave
    WordPress Dev
    Posted 3 years ago #

    Well that looks as I would expect it to, after much searching I cannot see what is going wrong here...

    Were you able to try the development version?

    Will continue to see if I can find out what is happening.

  11. daviddicks
    Member
    Posted 3 years ago #

    i think the development version might have fixed it, ill let you know.

  12. daviddicks
    Member
    Posted 3 years ago #

    im still getting the same problem since running the latest version of update notifier.

    how do i stop it?

    It's time to update the version of WordPress running at...from version abc to 2.9.2.

    getting it across all my sites. any fix and Im happy to donate.

  13. Jon Cave
    WordPress Dev
    Posted 3 years ago #

    I'm afraid I cannot see how this is happening. At the moment my guess would be something to do with your hosting/specific setup. Would you be able to email me: updatenotifier at lionsgoroar.co.uk ?

  14. carl_pilk
    Member
    Posted 3 years ago #

    hi duck,

    im getting the same problem. i updated wp to 3.0 some days ago, yet got this message today:

    It's time to update the version of WordPress running from version 2.9.2 to 3.0.

    weird as im not running WP-Security-Scanner (i did have it installed some time ago, but uninstalled it)

  15. Devstorm
    Member
    Posted 3 years ago #

    Hi,

    I have the same problem:

    It's time to update the version of WordPress running at "URL" from version 2.9.2 to 3.0.1.

    Please really fix this, disabling security with the above suggestion did not help and is not a solution. I never had version 2.9.2 installed, it was a 3.0.1

    As this plugin is very useful if it works :)

    Cheers, Devstorm

  16. Devstorm
    Member
    Posted 3 years ago #

    Please implement reading the real installed WordPress-version from the database, the contents of the $wp_version variable are changed by several security plugins, for good reason!!

  17. Jon Cave
    WordPress Dev
    Posted 3 years ago #

    I have been working on some ideas to help reduce the problem. You can install the development version from this page and here is a direct link to the .zip file. Delete the installed version of Update Notifier and install the development version via Plugins -> Add New -> Upload (you will have to reconfigure your Update Notifier settings). I would be grateful if you could test it out :)

    Currently the dev version removes the back-compat induced issue described below. I am also thinking about what to do about the 'upgrade from abc' emails, (partial) fix to come shortly. Though deactivating the plugin changing the version, or stopping just the part doing the changing works for me in my testing (I have worked out why I couldn't reproduce before, see note at the end). I have also come up with another change to these plugins which should help whilst still allowing you to leave a modified $wp_version in most situations if you so desire.

    Though I have to disagree that mangling $wp_version is useful (xref: some thoughts from a core committer) and in some cases interferes with core WordPress functions (see below about the automatic update checks made by WordPress).

    Thanks for taking the time to report and using my plugin :)
    - Jon

    If you're interested here are the full details on why problems like this are occurring:

    When WordPress does its automatic check for updates it asks wordpress.org if there are versions newer than $wp_version (which in this case is 'abc'), obviously 'abc' doesn't exist and so the response is that an update is available (even if your site already has the latest version of WordPress!). This response is stored by WordPress and when Update Notifier checks this stored value it sees that, allegedly, an update available and sends an unnecessary email notification.

    Also, the problem when Update Notifier tells you that version 2.9.2 should be updated to 3.0.1 occurs because of some backwards compatibility code I had to use (because 3.0 introduced site transients for storing the automatic update check responses), so when Update Notifier looked for the stored information (when $wp_version is not correctly set as 3.0.1) it decided that you still must be running 2.9.2 and so checked the old version of the transient which says 3.0 is available (since it hasn't been changed since updating to 3.0 and 3.0.1 because of the new transient usage).

    Note this does not occur every time since these plugins will often only modify the $wp_version global when not in the admin section. Therefore, if the automatic update check is triggered whilst an admin is logged into the backend then the correct response (no updates available, running the latest version) is stored and then Update Notifier doesn't send an email. If the check is triggered by a normal user visiting the site then the incorrect 'abc' version of events occurs.

  18. Jon Cave
    WordPress Dev
    Posted 3 years ago #

    Currently the dev version removes the back-compat induced issue described below. I am also thinking about what to do about the 'upgrade from abc' emails, (partial) fix to come shortly.

    Just updated the development version to fix this and it works in my testing. If you download the development version (see details above) you should see the version number as 1.4.1-beta in the Plugins menu. I would be grateful for any testing and feedback.

    Thanks.

  19. Jon Cave
    WordPress Dev
    Posted 3 years ago #

    Should be fixed as of 1.4.1

  20. zenofwordpress
    Member
    Posted 3 years ago #

    I just installed the latest version of this plugin for a client who is running the latest version of everything (WP, plugins, etc) and he got this email:
    ***********************************************************
    It's time to update the version of WordPress running at
    http://habitproject.com from version 3.0.4 to 3.0.4.

    The following plugin(s) have new versions available for download:
    example (example.com/example.zip)

    The following theme(s) have new versions available for download:
    example (example.com/example.zip)

    To perform the necessary updates visit your admin panel
    (http://habitproject.com/wp-admin/update-core.php).
    ***********************************************************

    Please, how can this be prevented? Thanks

  21. Jon Cave
    WordPress Dev
    Posted 3 years ago #

    Please, how can this be prevented? Thanks

    That's the test email text. It should have only been sent by clicking the "Send Test Email" button. If you're getting it and both you and the client have not been clicking this button only then is there a problem.

  22. zenofwordpress
    Member
    Posted 3 years ago #

    Thanks Jon. - After my post, I discovered that that email arrives when I clicked on the 'Send Test Email'. I have a call into my client to ask him if he clicked on the button. I suspect he did. Will let you know.

Topic Closed

This topic has been closed to new replies.

About this Topic