#29527 closed defect (bug) (fixed)
Number of available updates showing as NaN after completing updates
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 4.1 | Priority: | normal |
Severity: | normal | Version: | 4.0 |
Component: | Plugins | Keywords: | reporter-feedback has-patch |
Focuses: | administration | Cc: |
Attachments (4)
Change History (16)
#1
@
11 years ago
- Component changed from Menus to Posts, Post Types
- Keywords reporter-feedback added
#2
@
11 years ago
- Keywords close added
- Resolution set to invalid
- Status changed from new to closed
I wasn't actually related to the premium plugin but actually to my custom theme.
Can't blame core for that :)
#3
@
11 years ago
In my office we always blame "Chris" when things go awry (we don't have a "Chris").
#5
@
11 years ago
Hi circuuz, could you share what your theme was doing, so we have a better idea on how this broke for you?
#7
@
11 years ago
- Keywords reporter-feedback added
- Resolution invalid deleted
- Status changed from closed to reopened
I just accidentally reproduced this on trunk. I wasn't using the default theme, so it is possible that it theme related in this case as well, but I doubt it. It doesn't happen every time — just once so far.
I'd like to second nacin's query: circuuz, could you share more info on what was causing this?
#8
@
11 years ago
29527.diff checks if the count is NaN
before updating it.
I'm not sure why this happens, but I have a hunch that it is caused by the update count being empty when the page is loaded. That could happen if the updates transients were to get flushed, and the update APIs didn't respond with any updates. In my case, I think that might be happening because I was testing a custom API for retrieving updates for a plugin. I enabled it to get the update, but I disabled it again before running the update.
So, it's possible the only way that a user could cause this is if they are hacking around with stuff. On the other hand it's a rather trivial patch. I'll leave the decision on whether it's needed up to y'all. :-)
#11
@
11 years ago
- Owner set to SergeyBiryukov
- Resolution set to fixed
- Status changed from reopened to closed
In 29960:
#12
@
11 years ago
I see this is closed, but I also saw people asking how this occurred and if this was related to another plugin. I came across this on a production multisite running 4.0. I had 4 updates pending: 3 for themes and 1 for a plugin. I updated the plugin and then used the update now links shown under each of the following themes: TwentyTwelve, TwentyThirteen, and TwentyFourteen. After updated TwentyFourteen, I saw the NaN next to Updates. Screenshots are above.
I wasn't able to re-create this on a fresh 4.0 installation. In your screenshot, the plugin you are updating appears to be a premium plugin, not one hosted in the WP.org repository - I suspect this may be related. Can you try to re-create using a plugin from WP.org and/or a different premium plugin?