FAQ
How can I save my package before all required fields are filled?
Saving a new package requires all form fields to be completed.
However, the Package Manager release candidate doesn’t include selection or validation for the Root path.
Therefore, you can enter a temporary placeholder (for example, /a) to save, then return later to complete the correct path.
This way, if you need to copy a path from another app (for example, the Pages app), you can either open that app in a new browser tab or use a placeholder to save your draft. When copying a path from the Pages app, check whether an extra space is added to the front of the path after pasting it.
Why doesn’t Package Manager reopen my previously open package when I switch between apps?
The Package Manager app is a bit different from other apps in Magnolia. It uses Magnolia’s new design system and frontend technology, and is displayed in an iframe within the classic Magnolia interface. Because of this, Package Manager doesn’t preserve the last working state across app switches. If you leave a package editor view in Package Manager, for example, to open the Pages app, and then reopen Package Manager, it returns to the browser view. Consider opening other apps in a new tab/window to keep your editing context.
Should I install packages directly on public instances?
While it is technically possible to use Package Manager to install packages directly on public instances, it’s not recommended. Installing content on a public instance can create content differences between your author and public instances. A safer approach is to install your package on the author instance and then publish the freshly installed content to public instances.
If you need to install content on a public instance, consider the following:
-
Any content installed on a public instance is publicly available immediately.
-
If you do need to install your package on public instances, it’s good practice to install the same package on your author instance as well.