Support

Admin Tools

#11800 db Error on Updating to 2.5.4 with AT Pro

Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a

Latest post by nicholas on Monday, 02 April 2012 15:17 CDT

drjjw
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (Updating Joomla)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: (2.5.3)
PHP version: (5.3)
MySQL version: (5.1)
Host: (LiquidWeb)
Admin Tools version: (2.2.2)

Description of my issue:

Hi Nik,

When Updating using AT Pro to Joomla 2.5.4, received this dB error on 2 sites, after which, the sites still seem to upgrade and function. Just wondering if they can be safely ignored. Attached error as I triggered AT Pro when pasting them!





drjjw
Sorry, attachment didn't work, try this:

http://db.tt/lY8TKpbe

nicholas
Akeeba Staff
Manager
Hi Jordan! Don't freak out, I will now try using my psychic powers. You had used jUpgrade to migrate these formerly Joomla! 1.5 sites to 1.7 or 2.5 in the past. Am I correct?

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

drjjw
Now usually when you use your "psychic powers" line, you are pretty pissed off on Twitter. But I honestly didn't think to include that in the post :) Yes, you are correct!

nicholas
Akeeba Staff
Manager
He he! Today I had an upgrade in my crystal ball. No more static; perfectly clear images and very precise mind reading :)

No, seriously. You are the third person today with the same problem. It has to do with how jUpgrade screws up all IDs, including menu item IDs. The end result is that an otherwise free menu item ID ends up being used, therefore screwing up the update's SQL script.

What you need to do is run the following SQL command against your database, using phpMyAdmin:
INSERT INTO `#__menu` (`menutype`, `title`, `alias`, `note`, `path`, `link`, `type`, `published`, `parent_id`, `level`, `component_id`, `ordering`, `checked_out`, `checked_out_time`, `browserNav`, `access`, `img`, `template_style_id`, `params`, `lft`, `rgt`, `home`, `language`, `client_id`) VALUES
('menu', 'com_joomlaupdate', 'Joomla! Update', '', 'Joomla! Update', 'index.php?option=com_joomlaupdate', 'component', 0, 1, 1, 28, 0, 0, '0000-00-00 00:00:00', 0, 0, 'class:joomlaupdate', 0, '', 41, 42, 0, '*', 1);

replacing #__ with your site's database prefix.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

drjjw
Son of a gun!

nicholas
Akeeba Staff
Manager
He he! On the bright side, you now know that I really am a psychic after all ;)

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!