Make WordPress Core

Opened 14 years ago

Closed 8 years ago

#10884 closed defect (bug) (fixed)

Available plugin update count disappears after updating plugin

Reported by: sirzooro's profile sirzooro Owned by: dd32's profile dd32
Milestone: 3.8 Priority: normal
Severity: normal Version: 2.8.4
Component: Upgrade/Install Keywords: has-patch dev-feedback
Focuses: Cc:


When there are any available plugin updates, WP displays number of them next to "Plugins" item in menu. However when you have more than one update available and update one plugin, it disappears.

Steps to reproduce:

  • make sure you have more than one plugin with update available (WP should count of them in menu);
  • go to the Plugin page and click on Autoupdate link for plugin;
  • when update page will load completely, click on provided link to return to plugin list.

Expected result: WP displays new number of available updates next to Plugins menu.
Actual result: nothing is displayed.

Note: I tested this for inactive plugins only.

Attachments (1)

10884.diff (1.6 KB) - added by dd32 13 years ago.

Download all attachments as: .zip

Change History (6)

#1 @dd32
14 years ago

  • Component changed from General to Upgrade/Install
  • Owner set to dd32
  • Status changed from new to accepted

This sounds like an issue that has been run into before, Related to the fact that on some hosts, an update-check cannot be executed within the timeframe allowed on the new page load..

The reason why it happens that the update check is re-performed, is due to that the transients cannot be modified, without increasing the time the transient can live. If theres 60seconds left on the update ttransient, and ts modified, it'll keep that (potentially stale) transient for another 12 hours.. I dont believe theres currently a way to determine how much time is left for a given transient.

I'm going to take a closer look at this time permitting.

#2 @azaozz
14 years ago

  • Milestone changed from 2.9 to Future Release

No patch.

13 years ago

#3 @dd32
13 years ago

  • Keywords has-patch dev-feedback added; needs-patch removed

Attached patch takes care of this.

The question is, Is the extra API request worth it.

The downside of this is that the end of the update page may be delayed up to 3 seconds from displaying depending on the server's willingness to flush the data out to the client or not. It'll also cause a double API request if they visit the update-core page straight away (As I think it makes a request regardless)

#4 @chriscct7
9 years ago

@dd32 can you still reliably reproduce this on 4.0?

#5 @wonderboymusic
8 years ago

  • Milestone changed from Future Release to 3.8
  • Resolution set to fixed
  • Status changed from accepted to closed

This is more stable now - can't find the exact fix, but [18468] for menus, 4.2 for shiny updates - 3.7/3.8 for auto updates

Note: See TracTickets for help on using tickets.