Magnolia 6.3.4 known issues

Imported content can’t be published without metadata updates

This issue affects publishing when the imported files contain publishing properties, both for bootstrapped files or those imported via the UI when metadata and published versions are out of sync. In particular, when some nodes have the property mgnl:lastActivatedVersion and the corresponding version doesn’t exist, you can’t publish them without modifying them first. In addition, if a published node is modified in a way that doesn’t update Magnolia modification metadata, publishing also won’t succeed.

For more details, see:

Workaround

There are two workarounds to this issue:

  1. Before importing, erase publishing properties from import files, for example, using the following command.

    sed -i ‘' '/^[[:space:]]*mgnl:lastActivatedVersion:/d' <YOUR_FILE_TO_IMPORT>.yaml
    We also recommend deleting any mgnl:activationStatus properties to avoid inconsistencies related to the publication state.

  2. After importing, in the UI, unpublish imported nodes before publishing them.

Feedback

DX Core

×

Location

This widget lets you know where you are on the docs site.

You are currently perusing through the DX Core docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules