-
Type:
Story
-
Status: Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: 7.3.0 CE GA1, Master
-
Component/s: Fragment Administration
-
Epic Link:
-
Sprint:S01E04 - Turtles Swamp, S01E05 - Flowers Rebellion
-
Git Pull Request:
This task introduces a way to allow deleting fragments that have been deployed inside a site, virtual instance or system.
The first step to achieve this is that the "read-only" flag only blocks editing, but should not prevent deleting a fragment. Thanks to this, deployed fragments (which are given the "read-only" flag automatically) can be deleted from the corresponding UI.
Note though, that fragments should only be deletable from the UI of the scope which owns the fragments. That is, when accessing the fragments administration of a site, only the fragments of that site can be deleted, but not those inherited from Global.
In the case of virtual instance-scoped fragments, they can be deleted from Global.
Finally, in the case of system-scoped fragments, they can be deleted from Global of the default virtual instance.
- depends on
-
LPS-106411 Deploy folder can not delete zip file on Windows
- Closed
- is related to
-
LPS-107185 LPS-106253 - Product QA | Test Automation Creation
-
- Closed
-
- relates
-
LPS-106665 Fragment Thumbnail not imported with command: npm run import
- Closed
- Testing discovered
-
LPS-106795 Deployment descriptor file doesn't be included in zip file with command: npm run compress
- Closed
-
LPS-106798 [BUG] Deployed fragments should only have certain actions when set read only property
- Closed
-
LPS-106799 [BUG] Can delete deployed fragments of system-scoped only in Global site of the default virtual instance
- Closed