Make WordPress Core

Opened 14 years ago

Closed 5 years ago

Last modified 5 years ago

#12722 closed defect (bug) (reported-upstream)

Concurrent editing of widgets

Reported by: josephscott's profile josephscott Owned by: azaozz's profile azaozz
Milestone: Priority: normal
Severity: normal Version:
Component: Widgets Keywords: has-patch bulk-reopened
Focuses: Cc:


When two admin users edit widgets at the same time which ever one saves last wins. I think we'd need something like the post edit lock to be able warn users when someone else is already editing widgets.

Attachments (1)

12722.diff (6.5 KB) - added by wonderboymusic 12 years ago.

Download all attachments as: .zip

Change History (14)

#1 @buch0090
14 years ago

  • Cc davebuchanan@… added

#2 @jane
14 years ago

You had me at "the same time." Agreed.

#3 @scribu
14 years ago

  • Milestone changed from Unassigned to 3.1


#4 @nacin
14 years ago

  • Keywords needs-patch added
  • Milestone changed from Awaiting Triage to 3.1

#5 @ryan
14 years ago

  • Milestone changed from 3.1 to Future Release

#6 @nacin
14 years ago

  • Keywords 3.2-early added

#7 @wonderboymusic
12 years ago

  • Keywords has-patch added; needs-patch removed
  • Milestone changed from Future Release to 3.6

the gift of 3.2-early keeps on giving, and I think this is a great fit for the editing / locking / autosave vibes of this release.

I attached a first run at this. I had to write some JS to make the lock messages stay in tune with the sortable / draggable widget block things, but this overall widget-locking concept wasn't wildly complicated to implement


#8 @nacin
11 years ago

  • Keywords 3.7-early added; 3.2-early removed
  • Milestone changed from 3.6 to Future Release

This is cool. Obviously too late for 3.6 now, but would be great for 3.7. Needs to be re-coded to leverage the heartbeat and probably an abstraction of some of the new locking code.

#9 @wonderboymusic
11 years ago

  • Milestone changed from Future Release to 3.7

these are all marked 3.7-early

#10 @wonderboymusic
11 years ago

  • Milestone changed from 3.7 to Future Release

No one has touched this since my initial patch

#11 @westonruter
9 years ago

I'm starting to look at this in relation to concurrent editing in the Customizer: #31436

#12 @westonruter
9 years ago

  • Keywords 3.7-early removed

For the issue of conflicting auto-incremented widget IDs across user sessions, I've opened #32183.

#15 @talldanwp
5 years ago

  • Keywords bulk-reopened added
  • Resolution set to reported-upstream
  • Status changed from new to closed

There's a proposal to replace the widget screen as part of phase 2 of Gutenberg—GB13204. I've mentioned this issue there.

Also noting that #31436 will cover handling this for the customizer.

As such, I'll close this issue as 'reported upstream'.

Note: See TracTickets for help on using tickets.