-
Type:
Task
-
Status: Closed
-
Priority:
Normal
-
Resolution: Fixed
-
Affects Version/s: 4.0.0
-
Fix Version/s: 4.0.0
-
Labels:
-
Similar issues:
-
Story Points:0.5
-
Epic Link:
-
Sprint:Tiger Sprint 128, Tiger Sprint 129
When a container has just been locked by another user, changes to component's properties cannot be saved and a component cannot be deleted (the backend will return an error). In these cases, the UI should:
- close the dialog
- show an error message in a toast
- re-render the container of the component so the user sees it has been locked (depends on
CHANNELMGR-565for the visuals).
An example reproduction path is:
- editor edits a page
- admin edits the same page
- editor adds a banner to a container (and thereby locks the container)
- admin edits another component in the same container
- admin changes a parameter and clicks 'Save'
Expected: admin sees the dialog close, a toast appear with an error message and the container re-render. Clicking the component again will then open it in read-only state.
- is blocked by
-
HSTTWO-3650 Improved ContainerItemComponentResource to return proper error codes when the container has been locked
-
- Closed
-
-
HSTTWO-3645 ContainerComponentResource: #updateContainer() and #deleteContainer() APIs should return proper error codes and use recommended HTTP methods PUT & DELETE
-
- Closed
-
- relates to
-
CHANNELMGR-619 When a user clicks on a component that was deleted by another, proper error feedback should be shown up
-
- Closed
-