Make WordPress Core

Opened 6 years ago

Last modified 6 weeks ago

#40966 assigned defect (bug)

Double clicking the Update plugins-button gives... interesting experience!

Reported by: bitnissen's profile bitnissen Owned by: giuliapierbon's profile giuliapierbon
Milestone: 6.3 Priority: normal
Severity: normal Version: 4.6
Component: Upgrade/Install Keywords: shiny-updates good-first-bug has-patch needs-testing
Focuses: Cc:


Hi there,

I just updated to 4.8 on a bunch of sites and in one site I accidentally clicked the "Update"-button multiple times. What then happened, was a rather weird experience: After the update of the plugins successfully completed, it did another run where all updates apparently failed.

I tried this on multiple 4.8-installs, all has the same behaviour, so I guess it's fairly easy to reproduce. I've also recorded a video:

Steps to reproduce:

  • Upgrade to 4.8.
  • Go to "Plugins" » "Updates available" (you need at least a plugin that has updates ready for it)
  • Select all update-ready plugins.
  • Click the "Update"-button. Then click it again.
  • Observe the table of plugins :-)

Kind regards,

Attachments (7)

40966.diff (1.2 KB) - added by MarcGuay 6 years ago.
40966.2.diff (900 bytes) - added by MarcGuay 6 years ago.
Remove extra line
40966.3.diff (1.9 KB) - added by xkon 6 years ago.
On Update only and re enable on all notices just in case.
40966.4.diff (812 bytes) - added by xkon 6 years ago.
Noop update
40966.5.diff (3.6 KB) - added by swissspidy 6 years ago.
40966.6.patch (2.9 KB) - added by bookdude13 3 years ago.
Refreshed patch
40966.7.diff (3.5 KB) - added by simonemanfre 6 weeks ago.
Add class 'is-enqueued' to prevent elements being added twice to the update queue

Download all attachments as: .zip

Change History (29)

#1 @swissspidy
6 years ago

  • Keywords shiny-updates needs-patch good-first-bug added
  • Milestone changed from Awaiting Review to Future Release
  • Owner set to swissspidy
  • Status changed from new to assigned
  • Version changed from 4.8 to 4.6

Hey there,

Welcome to WordPress Trac and thanks for your report!

I'm pretty sure this isn't new in WordPress 4.8. This functionality was introduced in 4.6 with Shiny Updates. We've previously fixed this bug in the feature plugin (see, but I guess not every instance of it.

#2 @MarcGuay
6 years ago

Because the Apply button is a submit input and not an anchor like in the other case, the solution will be a bit different. It seems that it will need the disabled property added somewhere in the click event in wp-admin/js/updates.js starting at line 1999, and then removed once the queue is finished working, but it's not obvious to me at the moment, it's my first time looking at this code.

6 years ago

6 years ago

Remove extra line

6 years ago

On Update only and re enable on all notices just in case.

#3 @xkon
6 years ago

  • Keywords has-patch added; needs-patch removed

For some weird reason ( just in case it was working for you ) @MarcGuay s code was not disabling the button at all on my installation.

Either way I placed the code a little differently on ( 40966.3.diff ). It will disable the Apply button only in case of 'update-selected' and re-enable it either way whenever there's a notice. I think it's safer this way and at least it works for my installation.

Best regards,

This ticket was mentioned in Slack in #core by xkon. View the logs.

6 years ago

#5 @afercia
6 years ago

Please don't set disabled on focused elements because this will trigger a focus loss when using a keyboard. ideally, to avoid double clicks, the button should just no-op. /cc @swissspidy

6 years ago

Noop update

#6 @xkon
6 years ago

Changed the diff into 40966.4.diff to fix the issues that @afercia mentioned.

Hopefully this will pass. I already did my tests but more tests are always welcome.

Best regards,

6 years ago

#7 @swissspidy
6 years ago

Few notes:

  • Network admin for themes is probably affected too
  • The first patches don't work because of a11y rasons
  • 40966.4.diff is too broad. $('.updating-message') could be anything

What we really need is a way to disallow a specific theme/plugin that has already been updated.

The bulk action handler bails early if an item doesn't have the update class (like, when a plugin doesn't have an update). In theory this be used to fix this bug here. However, wp.updates.updatePlugin doesn't remove that update class after a successful update.

40966.5.diff fixes that by removing update with updating during the process.

#8 @xkon
6 years ago

I just tried your patch @swissspidy and I'm still able to hit the Apply button resulting in plugins update failed.

I thought the idea was to not being able to re-send the update command by 'disabling' the Apply button so we don't get update errors. That's why by reading if the 'updating-message' exists somewhere in the page which is a class added only when something is currently being updated the button is just doing nothing. The 'updating-message' is also binded and checked only if you have the 'update' selected from your list and I haven't seen any other lists containing the 'update-selected' option but I might be wrong here.

Anyway I'm new to this so I might be missing something. Though the .4 patch was cancelling the Apply action and no more update failures where showing. The .5 you uploaded is still giving Errors.

This is by hitting the Apply button 5 times in a row.

I'll take another swing at it as well as I never though of the Theme process as well.

Best regards,

Last edited 6 years ago by xkon (previous) (diff)

#9 @xkon
6 years ago

@swissspidy , now that i see this again with fresh eyes - do you want me to apply your patch and rework my js on top of your new css classes ? Just in case that makes it good to get it onboard as well?

#10 @swissspidy
6 years ago

@xkon Sure, feel free to build upon 40966.5.diff.

3 years ago

Refreshed patch

#11 @bookdude13
3 years ago

  • Keywords needs-testing added

Hey all! I'm new here, and I hope I'm not stepping on anyone's toes. Patch refreshed. This works for me with a plugin updating. Not sure how to test the theme side. Note that I did not do the css selector change at the end of 40966.5. I wasn't sure if that was still necessary since the last post here was a couple years ago.

This ticket was mentioned in Slack in #core by oglekler. View the logs.

3 years ago

#13 @swissspidy
22 months ago

  • Owner swissspidy deleted

This ticket was mentioned in Slack in #core by sergey. View the logs.

7 weeks ago

#15 @SergeyBiryukov
7 weeks ago

  • Milestone changed from Future Release to 6.3

This came up in a recent new contributors meeting. Moving to 6.3 for review.

#17 @giuliapierbon
7 weeks ago

I have tryed to apply 49066.6.patch to the current dev without success.
I have this error:
error: patch failed: src/js/_enqueues/wp/updates.js:380
error: src/js/_enqueues/wp/updates.js: patch does not apply

#18 @ryokuhi
7 weeks ago

  • Keywords needs-refresh added; needs-testing removed

Hello @giuliapierbon, and welcome on Trac.
You get the message above because the patch doesn't apply anymore.

#19 @giuliapierbon
7 weeks ago

Okay, I've just realized!Sorry
Can I have the ownership?

#20 @ryokuhi
7 weeks ago

  • Owner set to giuliapierbon

@giuliapierbon No problem! Contributing to WordPress can be difficult (especially in the beginning), but the most important part is to give it a try!
If you want to take care of the ticket (which doesn't strictly mean that you have to write the patch for it), I'm giving you ownership.

6 weeks ago

Add class 'is-enqueued' to prevent elements being added twice to the update queue

#21 @simonemanfre
6 weeks ago

@giuliapierbon I have attached new code to prevent items being added to the update queue again when the user click the update button several times.

To do this I added a new class "is-enqueued" the first time the update is launched for each element, if the user click again on the update button I check if that class is already present and do not add it back to the queue.

The class is then removed in the event of a successful or failed update of each plugin.

I have tested locally for both successful and failed updates and it seems to work correctly.

I don't know if using an HTML class is the best way to solve this bug, maybe it can also be done using local storage, but i see that WordPress use many other class to do similar thing, like "active", "update" or "is-uninstallable".

Last edited 6 weeks ago by simonemanfre (previous) (diff)

#22 @ryokuhi
6 weeks ago

  • Keywords needs-testing added; needs-refresh removed
Note: See TracTickets for help on using tickets.