[MGNLUI-2855] Ansynchonous action (activation) should return better error message Created: 05/May/14 Updated: 22/Jul/14 Resolved: 22/Jul/14 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 5.2.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christian Ringele | Assignee: | Evzen Fochr |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | quickwin, support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| 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 |
|
An activation using the asynchronous action implementation should return the full error of failing, example: The real error in the background is: ERROR info.magnolia.module.exchangetransactional.TransactionalSyndicator 05.05.2014 08:46:10 -- Failed to activate content. info.magnolia.cms.exchange.ExchangeException: Message received from subscriber: Parent content /uzh/unicms08 is not yet activated or you do not have write access to it. Please activate the parent content before activating children and ensure you have appropriate rights at info.magnolia.module.activation.BaseSyndicatorImpl.activate(BaseSyndicatorImpl.java:426) at info.magnolia.module.exchangetransactional.TransactionalSyndicator$2.run(TransactionalSyndicator.java:181) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) And when using the direct activation the error pop up shows a meaningful information, see print screen: DirectActivation-ParentNodeNotExisting.png Conclusion: |
| Comments |
| Comment by Evzen Fochr [ 21/Jul/14 ] |
|
Fixed by |
| Comment by Federico Grilli [ 21/Jul/14 ] |
|
@Evzen Was it ported to master (5.3.x)? Looking at the commit log for |
| Comment by Evzen Fochr [ 22/Jul/14 ] |
|
Error messages in CE and EE 5.3.1 |
| Comment by Evzen Fochr [ 22/Jul/14 ] |
|
@Federico posted screenshots of error messages form 5.3.1 CE and EE, is it ok or if not, can you pls describe what need to be changed. |
| Comment by Federico Grilli [ 22/Jul/14 ] |
|
Can you pls try to reproduce the same error as in the issue description with a parent node not activated and see if the scheduled error message is the same you get with direct activation? |
| Comment by Evzen Fochr [ 22/Jul/14 ] |
|
Error message in 5.3.2 |