Page History

This page describes some errors that may occur during the activation of content from the author to public instance(s).

...

During the activation process Magnolia makes a copy of the current content on the public instance and stores it in the mgnlSystem workspace. The system rolls back any changes using the backup copy if transactional activation fails for some reason. If the activation succeeds, the system overwrites the current content with the activated content and removes the backup copy.

Below tips and tools could help you either detect the issue or clean up unnecessary content before publishing:

• Debugging activation
• Checking at startup
• Cleaning tool
• Visual inspection

Debugging activation

The steps of an activation on Public can be viewed by turning the XAReceiveFilter to DEBUG using the Log Tools app. Here we see an example of the steps during page activation.
Activation of page /travel/about/company

...

To try and resolve the issue, clean the mgnlSystem workspace yourself on the public instance. There is a cleaning tool in the Activation Tools app. This is the same procedure that is run during startup but triggered manually using this app.

...

After running be sure to check the log. If you see repository exceptions then you need to take other actions. For example, restarting the server to release any locks that may still be present. Restarting will automatically call the cleanup procedure described above. If locks was the issue then you should see the system successfully remove the backup copies during the restart. However, if you still see repository exceptions in your log during startup then you most likely have a repository corruption issue. In that case probably the best course of action would be to recreate the workspace from scratch.

Visual inspection

The JCR Browser app will allow you to visually inspect the workspace as well.

...