[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: PNG File CE - 5.3.2 .png     PNG File DirectActivation-ParentNodeNotExisting.png    
Issue Links:
causality
caused by MGNLUI-2783 User is blocked in his browser sessio... Closed
relation
is related to MGNLUI-2840 (Potentially) long running actions sh... Closed
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:
When failing because the parent node was not activated yet the error the end user receives is:
"Can't execute command website-activate"

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:
The asynchronous action triggering should receive the same error as the direct triggering.



 Comments   
Comment by Evzen Fochr [ 21/Jul/14 ]

Fixed by MGNLUI-2840

Comment by Federico Grilli [ 21/Jul/14 ]

@Evzen Was it ported to master (5.3.x)? Looking at the commit log for MGNLUI-2840 isn't that clear. could you please verify?

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

Generated at Mon Feb 12 09:00:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.