Website Known Issues

This page contains known issues, resolved or unresolved.

Welcome banner appearing on content pages

Sympton

A content page, e.g. Notice Sheet page, shows the Welcome banner, the actual content and then home page footer.

Root Cause

This can happen when Joomla doesn't know under which menu to display content and therefore default to the home page as menu choice (which has ItemId 101). This means that Joomla will display all the modules that appear on the home around the content.

This will happend when the menu item is of type Tagged Items and the user navigates from summary page to the specific tagged content. For example, if the Notice Sheets menu displays a list of tagged noticesheets and the user selects a notice sheet to view it, Joomla will display the notice sheet in the context of the home page, not the Notice Sheets menu and therefore display the welcome banner and home page footer.

In my view, this is a clearly a bug but there seems to be some discussion on whether it is expected behaviour, see Joomla issue 6970.

Work Around

To work around the issue, for each menu of type Tagged Items, a corresponding menu under Hidden with type Category Blog needs to be created. Once done, Joomla will generate different links for the actual menu of Tagged Items and the specific item page will be displayed in the context of the Category Blog menu item.

sh400sef can be used to determine how the URLs should structured.

Plesk auto upgrade failing

Sympton

Emails like this one arrive in your inbox:

Attention, 

The update of Plesk has failed.

You can download Plesk Installer logs at the following link: https://s1.ccchislehurst.org:8443/admin/update/log/id/a6f78464-89fa-9f94-1504-df83b4db65e6.
Contact your Hosting Provider for support assistance.

This message was sent automatically by Plesk Installer.

Root Cause

Follow the link to check the log but usually the cause is that the disk space has run out.

Fix

To the fix the issue:

1. Log in via SSH as root.
2. Check which kernel version it is running on: uname -r
3. Run sudo apt-get autoremove and check that the current kernel version is not in the list before confirming to continue.

If this does not work because there is not enough space on the boot partition (run df to check):

1. Create a backup image via the 1 & 1 Cloud console.
2. Go to /boot and run ls.
3. Manually remove files with a lower version than the current kernel version using rm, e.g. code>rm abi-4.4.0-96-generic
4. Once you have some space created, run sudo apt autoremove --purge linux-image-x.x.x-xx-generic for lower versions than current kernel version until there the boot partition usage is about 60%.

For more information, see SOLVED Package Operations Failed.