Magnolia 6.0 reached end of life on June 26, 2019. This branch is no longer supported, see End-of-life policy.
...
When accessing the webapp without the trailing slash after the context http://localhost:8080/magnoliaAuthor after login the user is presented with a 404 page rather than admincentral. This behavior is configurable via the mapperContextRootRedirectEnabled
and mapperDirectoryRedirectEnabled
attributes of the Context which may be used to restore the previous behavior. See Tomcat 9.0.0.M2 in https://tomcat.apache.org/tomcat-9.0-doc/changelog.html.
...
Your Magnolia instance starts up very slowly, noticeably more than before. You may encounter this after upgrading your macOS to Sierra 10.12 or later.
Workaround:
Open a terminal and figure out the hostname of your Mac. To get the hostname, use the command hostname
.
Code Block | ||
---|---|---|
| ||
hostname
joesLittleMacBookPro.local |
The command returns the hostname of your Mac. In the given example, the hostname is joesLittleMacBookPro.local
.
/etc/hosts
with an editor of your choice. You will edit the file in the next step.root
. Your user must belong to the group admin; otherwise, you cannot save the changes to the file. You will be asked for your password either when opening the file or when trying to save it.Add these two lines to /etc/hosts
:
Code Block | ||||
---|---|---|---|---|
| ||||
127.0.0.1 <hostname>
::1 <hostname> |
In place of <hostname>
, use your real hostname.
Most probably, your hosts file already contains entries starting with 127.0.0.1
and with ::1
. Just add the real host name at the end of one line that starts with ::1
and at the end of another line that starts with 127.0.0.1
. Make sure to add a space character before the hostname.
With the given hostname, the two lines would look like this:
Code Block | ||||
---|---|---|---|---|
| ||||
127.0.0.1 localhost joesLittleMacBookPro.local
::1 localhost joesLittleMacBookPro.local |
Further information:
...
For issues related to publishing/activation keys and the handshaking process, see either the Publishing or errors page or the Activation errors page, depending on the module you use.