TOPIC: Update 2.2 -> 3.0.1

Hello,

I made a clean installation of 3.0.2 to clean Joomla 3.1.5 on my test server. It did not work. I uninstalled it and removed #_matukio tables from database. Then installed 3.0.1 and that worked fine and was happy about few new functions/options in backend.

After testing I decided to try installing 3.0.1 to clients web site, on 2.x version. In backend, the tabs have different setup than the tabs in the clean install and the new options are missing from advanced-tab (meaning the email notification setup).

Plus, when I tried to add a new or edit an existing event in backend, the system says:

1146 Table '[database].#_matukio_locations' doesn't exist SQL=SELECT * FROM #_matukio_locations WHERE published = 1 ORDER BY title ASC

And adding Locations makes the system say:

1146 Table '[database].#_matukio_locations' doesn't exist SQL=SELECT * FROM `#_matukio_locations` WHERE id = 0

Any advice?

Hi Miika,

very wired - any error messages during the update? Sounds like the database update didn't work out. Which MySQL and PHP Version are you using?

Best regards

Yves

Hi,

PHP 5.3.27
MySQL 5.5.32-cll

And to be exact, the version I installed the 3.0.1 on was 2.2.1

And no, I do not have live link to the problem as I was forced to recover the site from backup I took before I did anything. I can try again this evening if you come up with some suggestions.

Thanks.

HI Miika,

hmm hard to say - try updating to 2.2.10 first and after that to 3.0.0 and then to 3.0.2 (maybe we also get some error messages this way).

Best regards

Yves

Hello,

I copied the client site to my own test server to investigate the issue. I first installed 2.2.4 (since 2.2.10 doesn't exist in download area ). There I got these warnings:

JLIB_INSTALLER_ERROR_NOTFINDJOOMLAXMLSETUPFILE
JLIB_INSTALLER_ABORT_DETECTMANIFEST

It seems that some strings are missing from somewhere..

Then I installed 3.0.0 without warnings and the features seemed to work ok. Next I installed the 3.0.2 and again without any warnings and still the functions work fine. Perhaps there was something missing in SQL updating in 3.0.1 software package but was included in 3.0.0.

I will now take the client site offline and try this update procedure there too. Wish me luck..