[MAGNOLIA-3197] Better error message when the parent of an activated node is not activated yet Created: 09/May/10 Updated: 23/Jan/13 Resolved: 10/May/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.3.1 |
| Fix Version/s: | 4.3.2 |
| Type: | Improvement | Priority: | Trivial |
| Reporter: | Fabrizio Giustina | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| 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 |
|
If you try to activate a node with a missing parent the error message returned to the activator simply contains the missing node name, e.g. "parent"
Something more explicit could help, e.g.: Parent folder "parent" not yet activated, please activate it before children.
|
| Comments |
| Comment by Fabrizio Giustina [ 09/May/10 ] |
|
done |
| Comment by Jan Haderka [ 10/May/10 ] |
|
While good idea in general, the proper place to apply this thing and minimize the impact is elsewhere. |