#12722 closed defect (bug) (reported-upstream)
Concurrent editing of widgets
| Reported by: | josephscott | Owned by: | azaozz |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Widgets | Version: | |
| Severity: | normal | Keywords: | has-patch bulk-reopened |
| Cc: | Focuses: |
Description
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)
Change History (14)
#7
@
14 years ago
- Keywords has-patch added; needs-patch removed
- Milestone Future Release → 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
Feedbacks?
#8
@
13 years ago
- Keywords 3.7-early added; 3.2-early removed
- Milestone 3.6 → 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.
#11
@
12 years ago
I'm starting to look at this in relation to concurrent editing in the Customizer: #31436
#12
@
11 years ago
- Keywords 3.7-early removed
For the issue of conflicting auto-incremented widget IDs across user sessions, I've opened #32183.
#15
@
8 years ago
- Keywords bulk-reopened added
- Resolution → reported-upstream
- Status new → 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'.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
You had me at "the same time." Agreed.