Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-6817

Make LockException error messages more human-readable

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Neutral
    • None
    • None
    • None
    • None

    Description

      Currently, the `LockException` is bubbled all the way up and rendered into a not-so-insightful error message in the UI (see Screenshot from 2016-10-12 14-24-32.png), especially for non-technical users.

      Instead, that exception should either be caught and wrapped or prevented in order to at least throw a more well-formulated one. Something like "Node to be restored was locked by another operation - try again later" would make much more sense to end users.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              creichenbach Cedric Reichenbach
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Task DoD