After the initial load of a layout builder edit page (either per-entity overrides or the per-display defaults), any subsequent visits to the page will trigger a "You have unsaved changes" message, even when no changes have been made.
(this bug was introduced by #3144010: New pseudo-fields cannot be removed, InvalidArgumentException thrown → )
Scenario 1:
Scenario 2:
Actual result: "You have unsaved changes" message appears.
Expected result: The message should not appear, since there are no unsaved changes.
Update LayoutTempstoreRepository so that it can explicitly keep track of whether any given SectionStorage in the repository has unsaved changes.
Review
The "You have unsaved changes" message will only appear when you have unsaved changes
LayoutTempstoreRepositoryInterface has a new public hasUnsavedChanges() function. Note that this interface has a one-to-one correspondence with the LayoutTempstoreRepository class, so we can add functions without breaking any BC rules.
In addition, LayoutTempstoreRepositoryInterface::set() has a new optional boolean argument called $has_unsaved_changes, which is used to track whether there are unsaved changes in the SectionStorage being set.
N/A
N/A
Needs work
11.0 🔥
Last updated
Blocks and Layouts Initiative. See the #2811175 Add layouts to Drupal issue.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
@AndyThornton could you please share your solution ("own version of that subscriber")?
Patch from #20 doesn't work with 10.3.0 because of "Add static caching to LayoutTempstoreRepository"
https://www.drupal.org/project/drupal/issues/3445909 🐛 Add static caching to LayoutTempstoreRepository Fixed