Mandatory information about my setup:
Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? No
Joomla! version: (unknown)
PHP version: (unknown)
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Admin Tools version: (unknown)
Description of my issue:
I get update notifications about Joomla 2.5.8 to 3.0.2. I just tried that update and got an error. I couldn't access the website front end. I went to the backend to use Akeeba Backup to restore my site to the 2.5.8 version backed up just before the upgrade attempt. The restore only worked partially, and I'm left with very unsatisfactory 3.0.2 admin web pages.
On checking the Joomla forum about upgrading from 2.5.x to 3.0.x and what is says is:
"Joomla 3.0 Update Guide
If you need an update guide for moving from 2.5.x to 3.0.x then here it is:
DON'T!"
from: [http://forum.joomla.org/viewtopic.php?f=710&t=757723]
I checked my Akeebabackup admin tools setting and it is for stable releases only. The Joomla forum advice is wait until Joomla 3.5 (unless I'm a developer, etc., needing an early release)...but 3.0.2 is also flagged as a RC. So we are in a half-way house. Akeebabackup admin tools is prompting me to upgrade (and correctly for RC upgrades) BUT Joomla is really advising that as a regular site with no need to try anything in 3.0.x I should wait until 3.5.
Is there some way that Akeebabackup notifications can be amended to handle a new situation like this? Maybe by adding a new category of Joomla releases as Joomla is now talking about release with short term support (STS) and long term support (LTS) - so, ideally, I would have a new Akeebabackup admin tools that gives me that choice between STS and LTS releases for notifications.
