Activating pages

About activation

In a typical setup, you have one "author" instance and one or more "Public" instances of Magnolia. The purpose of the Magnolia author instance is to manage the content, while not being publicly visible. Your changes are only visible to other editors. The "public" instance(s) represent your actual website. Edit bars and buttons are normally not visible on public instances. This separation allows you to edit content at your own pace, and to make it available (publish it) whenever you want.

Activation is the process of publishing your pages. Under the covers, this simply copy pages between instances of Magnolia. In Magnolia, anything can be activated, not only pages. As such, configuration, users, groups, etc. is also activated.

How to activate a page

Activating a Page Activating a page is usually done through the website workspace. As for creating and editing your pages, you can either use the contextual menu (right-click) or the function bar.

 Activating a tree/branch of pagesWhen adding a couple of new pages, you might want to activate all of them at once: you can also activate a whole tree of pages, by using the contextual menu option "Activate including sub pages".

Check your activated page

You might be surprised to not see your page immediately on your public website. If the workflow module is installed on your Magnolia instance, for example, you might have to wait for someone else (typically a "publisher") to approve your activation.

If you have a simple, no-workflow installation, then the default location for your new page on the public instance would be the same as on your author instance; i.e if you edited http://localhost:8080/magnoliaAuthor/test/mypage.html the corresponding public URI would be http://localhost:8080/magnoliaPublic/test/mypage.html

If not, your system administrator certainly has more details about this.

Troubleshooting

If you get an error indicating that the page could not be activated, the most likely reasons are:
  • The Subscriber is not configured properly
  • Your credentials have not been published or updated on the public instance(s).
Here too, your system administrator should be able to help.