Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-2855

Ansynchonous action (activation) should return better error message

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Neutral
    • Resolution: Obsolete
    • Affects Version/s: 5.2.4
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              efochr Evzen Fochr
              Reporter:
              cringele Christian Ringele
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response: