Magnolia 6.2.54 known issues
SPA page rendering is broken
When trying to render an SPA page, you may instead see a template error message similar to this:
Error while rendering [/home_de/about-us] with template [demo-ecommerce:pages/Basic]
for URI [/home_de/about-us?mgnlPreview=false&mgnlChannel=desktop]:
RenderException: No template script defined for the template definition
[ConfiguredSpaRenderableDefinition(jsPaths=null, cssPaths=null, baseUrl=null,
routeTemplate=null, spaRouterClass=class info.magnolia.pages.spa.routing.SiteAwareSpaRouter)]
The issue may be due to a faulty initialization or loading of the license by the Multisite module. We are actively working to resolve it. For more details, see MULTISITE-209.
Workaround
Edit any site configuration. This re-triggers its registration and page rendering starts working again.
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:
-
Before importing, erase publishing properties from import files, for example, using the following command.
sed -i '' '/^[[:space:]]*mgnl:lastActivatedVersion:/d' <YOUR_FILE_TO_IMPORT>.yamlWe also recommend deleting any mgnl:activationStatusproperties to avoid inconsistencies related to the publication state. -
After importing, in the UI, unpublish imported nodes before publishing them.