- Issue created by @Michelle
- Status changed to Closed: duplicate
5 months ago 1:56pm 8 April 2024 - 🇷🇴Romania amateescu
This will be fixed in 🐛 Contraint validation error after merge: The content is being edited in the develop workspace Needs work .
- 🇺🇸United States Michelle Wisconsin, USA
@amateescu,
Thanks for finding that. I did search quite a bit before filing these issues but I guess I just wasn't using the right terms. I was calling it "sub workspace" not "develop workspace". If I hit any more problems, I'll search on that.
- Status changed to Active
5 months ago 4:12pm 11 April 2024 - 🇮🇳India amitvin
As the workspace association is not getting deleted, One is not able to edit the content on the live workspace even if the content is published. Right now getting the message that content can not be edited as the content is edited in the sub workspace.
A temporary workaround is to delete the association manually after merging the sub-workspace with the parent workspace. - 🇩🇪Germany Antonnavi Berlin
Hello all here,
I had the same bug and fixed it in the way of adding additional cleanup on publication to Live workspace.
See details in attached patch file. - Status changed to Needs review
14 days ago 12:06pm 25 August 2024 - Status changed to Needs work
13 days ago 4:28pm 25 August 2024 - 🇺🇸United States smustgrave
Hello, all fixes should be in MRs against 11.x so tests will run.
Also issue summary should be complete and a clear title. Tagging for both.
With most bugs will also need a test case showing the issue
- First commit to issue fork.
- Merge request !9409Issue #3438769 - Cleanup sub-workspaces on deploy to Live workspace → (Open) created by VinmayiSwamy
- Status changed to Needs review
4 days ago 10:37am 4 September 2024 - 🇮🇳India VinmayiSwamy
Hi, I have created an MR incorporating the patch changes from comment #9 and added a test case to validate these changes as outlined in comment #11. The issue summary has been updated accordingly.
I am removing the "Needs issue summary update" and "Needs tests" tags. If anyone believes these tags should still be applied, please feel free to re-add them.
Kindly review the changes and let me know if any further adjustments or updates are needed. Your feedback and suggestions for further improvements are greatly appreciated.
Thanks!
- Status changed to RTBC
2 days ago 4:27pm 5 September 2024 - 🇺🇸United States Scott Weston
Reviewed code of #13 (and #9) and tested on Drupal 11.0.1 clean Standard installation with default and custom content types, taxonomy terms, and menu links. The bug experienced is no longer happening. Updating status to RTBC.