Opened 13 years ago
Closed 13 years ago
#134 closed defect (fixed)
Save private components should work even when component is used
| Reported by: | patdui | Owned by: | twagoo |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | ComponentRegistry | Version: | |
| Keywords: | Cc: | twagoo |
Description
Create profile and reference to a private component.
If you now edit the private component and save, it doesn't work. GUI gives: "Failed to register: - Unable to register at this moment. Internal server error." which should be more descriptive. The real reason it doesn't work is because the component is still used by other profiles. (see server logs:
clarin.cmdi.componentregistry.DeleteFailedException?: Still used by the following profiles:
)
It protects the user that your change indirectly changes those profiles. It is probably better if it is possible to just make the change to PRIVATE components possible. Gui should probably notify which profiles are affected and ask for confirmation and then proceed.
Change History (3)
comment:1 Changed 13 years ago by
| Owner: | changed from patdui to twagoo |
|---|---|
| Status: | new → accepted |
comment:2 Changed 13 years ago by
| Status: | accepted → assigned |
|---|
comment:3 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixed in [1462:1475/ComponentRegistry/trunk] (1.9-SNAPSHOT)
When updating a component in the private workspace, the UI client calls registry/components/usage/{id} to retrieve a list of items that use the component. If it is not empty, a confirmation dialog is shown that includes a list of items that will be affected.