[MGNLACTIVATION-69] Non-activated nodes cannot be deleted without switching off subscriber Created: 08/Dec/13 Updated: 15/Mar/21 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Activation |
| Component/s: | None |
| Affects Version/s: | 5.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | deletion, ideas, undo/redo, usability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Since In config app, nodes/properties can no longer be deleted when public instance |
| Comments |
| Comment by Jan Haderka [ 09/Dec/13 ] |
|
Multiple things:
The above being said, this bug report should be converted into a part of undo/redo story/epic as it clearly depends on it. |
| Comment by Mikaël Geljić [ 12/Dec/13 ] |
|
Ok definitely makes sense considering the active subscriber configuration. Now from a developer's perspective, how about having the default subscriber inactive by default / set active through magnoliaAuthor properties, or something along these lines? |
| Comment by Evzen Fochr [ 25/Mar/15 ] |
|
If you create new public (by copy paste f.e.), Author instance don't know about its nodes, so if you try to "publish deletion" something marked as "not activated" you still must check all your public instances if node is there and needs to be deleted. And if one or more public have incorrect configuration, it correctly aboard operation. |