New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template Builder: Container Layout Editing Issue #26413
Comments
It looks like we are updating the Screen.Recording.2023-10-10.at.4.56.36.PM-1.mov |
Found this scenario that happens consistently, the content comes back after delete the container and create a new one. we are not cleaning references in the BE Screenshare.-.2024-01-05.5_28_14.PM.mp4 |
The current behavior is that when we remove a Container that has Contentlets inside it the relationship between the Contentlet, page and container is mark as orphan instead of be removed , then if the Container is add back inside the page on the future these Contentlets are going to be back on the page too. In a meeting where participated: @fmontes and @wezell , we decided that the fix is going to be:
|
The default value of the flag will be the new behavior. |
NOTE TO QAIn order to check that the fix is working, watch the video attached by @hmoreras which perfectly describes the scenario that must NOT happen anymore. From now on, previously added content must not show up after a Container has been removed. The name of the flag is:
If you want to bring the old behavior back, just set it to |
…ng orphaned Contentlets (#27391) Co-authored-by: Freddy Montes <751424+fmontes@users.noreply.github.com>
Passed Internal QA
Videofix-issue-26413-template-builder-container-layout-editing-issue.mov |
Approved: Tested on master_917a29e, Docker, macOS 13.0, FF v121.0.1 |
Problem Statement
When editing the layout of a page, content is being moved around when the same containers are used in all the boxes.
Steps to Reproduce
Kapture.2023-10-10.at.12.24.49.mp4
Acceptance Criteria
External Links
N/A
Assumptions & Initiation Needs
N/A
Quality Assurance Notes & Workarounds
The text was updated successfully, but these errors were encountered: