-
Improvement
-
Resolution: Obsolete
-
Neutral
-
None
-
5.2.4
-
None
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.
- caused by
-
MGNLUI-2783 User is blocked in his browser session after starting long running Action
-
- Closed
-
- is related to
-
-
- Closed
-
