Wordpress shows that I have 1 plugin update when all plugins are already updated

So, I searched the forums, and although I found several people with a problem similar to mine, I still have not found a way to get this fix. What happens is that WordPress shows that I have 1 plugin update when all my plugins are updated. Below is a link to a screenshot of imgur so you can see what I'm talking about:

http://imgur.com/HlspXv7

Now I tried several things, including reinstalling WP and removing transients using Artiss Transient Cleaner , but nothing works. Any ideas on what might cause this scam / ghost plugin to request an update if it isn't? Thank you and I appreciate your help.

+14
wordpress wordpress-plugin notifications
source share
11 answers

I see this from time to time with premium plugins and themes that require an activation key. The WP user interface will not provide updates for the plugin or theme, but the count of the pending update will be displayed in the user interface.

To track the source, I use the following function:

/** * Debug Pending Updates * * Crude debugging method that will spit out all pending plugin * and theme updates for admin level users when ?debug_updates is * added to a /wp-admin/ URL. */ function debug_pending_updates() { // Rough safety nets if ( ! is_user_logged_in() || ! current_user_can( 'manage_options' ) ) return; if ( ! isset( $_GET['debug_updates'] ) ) return; $output = ""; // Check plugins $plugin_updates = get_site_transient( 'update_plugins' ); if ( $plugin_updates && ! empty( $plugin_updates->response ) ) { foreach ( $plugin_updates->response as $plugin => $details ) { $output .= "<p><strong>Plugin</strong> <u>$plugin</u> is reporting an available update.</p>"; } } // Check themes wp_update_themes(); $theme_updates = get_site_transient( 'update_themes' ); if ( $theme_updates && ! empty( $theme_updates->response ) ) { foreach ( $theme_updates->response as $theme => $details ) { $output .= "<p><strong>Theme</strong> <u>$theme</u> is reporting an available update.</p>"; } } if ( empty( $output ) ) $output = "No pending updates found in the database."; wp_die( $output ); } add_action( 'init', 'debug_pending_updates' ); 

Add this to your functions.php theme, then go to the page with ?debug_updates added to the url. For example: yourdomain.com/wp-admin/?debug_updates. This should show you any topic or plugin that is causing the problem.

+15
source share

I had this problem, and it was that a new translation was available (which is not obvious from the Updates page, you should go to Update Translations below);

enter image description here

after updating the translations ... the warning disappeared;

enter image description here

+8
source share

A slightly modified version of Kevin's answer that does not require adding parameters to the URL. It simply connects to the update core right after the plugins, themes, and translations and displays a list of updates.

 /** * Debug Pending Updates * * Displays hidden plugin and theme updates on update-core screen. */ function debug_pending_updates() { // Rough safety nets if ( ! is_user_logged_in() || ! current_user_can( 'update_plugins' ) || ! current_user_can( 'update_themes' ) ) return; $output = ""; // Check plugins $plugin_updates = get_site_transient( 'update_plugins' ); if ( $plugin_updates && ! empty( $plugin_updates->response ) ) { foreach ( $plugin_updates->response as $plugin => $details ) { $output .= "<p><strong>Plugin</strong> <u>$plugin</u> is reporting an available update.</p>"; } } // Check themes wp_update_themes(); $theme_updates = get_site_transient( 'update_themes' ); if ( $theme_updates && ! empty( $theme_updates->response ) ) { foreach ( $theme_updates->response as $theme => $details ) { $output .= "<p><strong>Theme</strong> <u>$theme</u> is reporting an available update.</p>"; } } if ( empty( $output ) ) $output = "No pending updates found in the database."; echo "<h2>Pending updates</h2>" . $output; } add_action( 'core_upgrade_preamble', 'debug_pending_updates' ); 
+2
source share

I had the same problem when installing Wordpress 5.0.1. In my case, it was connected with a formidable premium. The formidable support team also sent a message because something has changed there, here is their message:

 Hi , As some of you may know, we updated the licensing software on our site a few months ago. This meant we had to move all of the licensing information to a new format. Unfortunately, this caused some of the custom site limits to be reduced for add-ons that werent bundled with a grandfathered license. We had a few people understandably ask us about this. Our solution was that they could manually upgrade to a bundle, which would solve the problem. However, over the last month we were made aware that some people were upset with the reduction in limits, but hadnt contacted us about it. As a result, we set to work and moved everyone with a Business or Enterprise license over to a bundle that would automatically correct the issue. I want to take this opportunity to apologize for the trouble we may have caused, and that we didnt realize sooner that so many people had been negatively affected. I would also like to reassure you that we never intend to remove a grandfathered benefit from your account. I hope you were not among the group that lost faith in us over this issue. While we will always aim to resolve issues as soon as they occur, we would ask that if you ever run into another problem, that you contact us about it first. That way, we can rectify the problem and reduce the trouble it causes you. 

So this can be very common if the plugin changes the way the developer API is accessed.

Best regards, Norbert

+2
source share

I ran into this problem and found that the culprit was W3 Total Cache. Deactivating and reactivating the plugin fixed the problem. Hat tip This forum is for tips.

+1
source share

The previous expired Yoast Premium plugin was the culprit, so I turned it off and on again, and this solved the update problem.

+1
source share

If you have FTP access, look in the plugins folder and make sure you have an X number that matches the ones that appear in Wordpress. Perhaps you have one that is broken, so it still detects it, but it does not format it correctly so that it does not appear in Wordpress.

If you do not have access to FTP, you can still see the files by going to "Plugins"> "Editor" and looking at the drop-down list in the upper right corner.

0
source share

It was definitely a Yoast Premium plugin in my case. After I deactivated and reactivated, the false number of the plugin disappeared.

0
source share

I had an older version of the Yoast Premium SEO plugin that I deactivated and then reactivated again, and this solved the problem.

0
source share

in most cases this happens with premium plugins. so turn off the plugins one by one until the notifications disappear and work again. then the problem will be solved.

0
source share

I deactivated and then reactivated the Yoast SEO Premium plugin. This solved the problem.

0
source share

All Articles