Help needed after migration

[webbuilder]

I have updated joomla from 1.5.26 to 2.5 and then to 3.1.1

I managed to pass all problems and everything seems to be ok at the beggining. The problem is when i tried to install an extension. I get the error error building menu After digging up to find the problem i noticed that from Extension manager --> Database i have the following error

Database schema version (2.5.2-2013-02-03) does not match CMS version (3.1.1).
Table '__content' does not have column 'title_alias' with type 'VARCHAR(255)'. (From file 1.7.3-2011-10-15.sql.)
Table '__content' does not have column 'title_alias' with type 'VARCHAR(255)'. (From file 1.7.4-2011-11-23.sql.)

I tried the FIX button but i got the following
1054 Unknown column 'title_alias' in __content' SQL=ALTER TABLE `__content` CHANGE `title_alias` `title_alias` VARCHAR( 255 ) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT '';

Please advise what to do .

Thanks

[sovainfo]

You should remove the 1.7*sql files mentioned.

[webbuilder]

Where are those files located ?

The answer to my question is administrator/components/com_admin/sql/updates/mysql

and it worked !!!

Thanks

[stonepiano]

Thanks, This helped me fix this problem and another one.

[sovainfo]

It is a workaround and unfortunately you have to repeat it with every update. The real problem must be in the sort. Another workaround could be making sure the names of the sql files are all of the same length. And again this needs to be done with every update. If they could only standardize on the name: version-date-seq.


EDIT
Unfortunately I can't test this because I dont have this sort problem. Could one of you test it?

Also does someone know why those old files remain in the distribution?

[DaveOzric]

Thanks!

[kalalee]

You should remove the 1.7*sql files mentioned.

Once I removed the 1.7*sql files via FTP my Joomla 3.x install is now reporting, 'Database table structure is up to date.' THANKS!

[shiftCase]

I have the same error, but those two files weren't present. I deleted the field title_alias from #_content, and still have the same error. So far, still no-go for me.

UPDATE - RESOLVED.

I also needed to flush the site's server cache (not just the Joomla or browser caches) to complete the change.

[leolam]

Also does someone know why those old files remain in the distribution?

You do not have to repeat it with every upgrade.
Only the 2.5 and 3.x are in the distro. I checked with PLT on this in the JBS and I quote Michale Babker

if you’re updating from 1.7 to 2.5, you need every 2.5 update SQL file… as you can’t go from 1.6 to 2.5 cleanly via the backend, the 1.7 files would be necessary to reference for manual database updates

That the J17 are still in is a result from the non-delete in the upgrade from J17 to J25 followed by the mini-migration to J3.x. Down the road something in the database was botched causing the errors after hitting the fix. Removing the J17 files manually if they are present is safe and they won't return

Leo

[sovainfo]

Thank you for addressing this in the JBS.

I disagree with the current way the distribution sets are created. Each of them is designed to be used for a certain purpose. Distro's designed to update J2.5.x shouldn't contain J1.x.sql updates.

Also when my installation says its database is on J2.5.21, Joomla updates shouldn't put any sql update from before J2.5.21 on my system.

When your migration procedure tells you to install J2.5.21 and then update to J3.3.6 you needed to remove the j1.7.*.sql from J2.5.21. When replacing J2.5.21 with J2.5.27 you need to remove them from that distribution again. When replacing J2.5.21 with .22,.23,.24,.25,.26,.27 you'll have changed it for each update.

[Webdongle]

Looking at the sql files in /administrator/components/com_admin/sql/updates/mysql/ they appear to haf if not exist for tables and update. So they should only update the database when a Table doesn't exist or a Table exists and needs to be altered.

/Joomla_2.5.1-Stable-Full_Package/administrator/components/com_admin/script.php Under

Code: Select all

/**
	 * method to update Joomla!
	 *
	 * @param	JInstallerFile	$installer	The class calling this method
	 *
	 * @return void
	 */

Line 313 "public function deleteUnexistingFiles()" and in the list of files

Code: Select all

			'/installation/sql/mysql/joomla_update_170to171.sql',
			'/installation/sql/mysql/joomla_update_172to173.sql',
			'/installation/sql/mysql/joomla_update_17ga.sql',

Does this not mean that the files are deleted during the finalisation of the update ?

[leolam]

I disagree with the current way the distribution sets are created. Each of them is designed to be used for a certain purpose. Distro's designed to update J2.5.x shouldn't contain J1.x.sql updates.

Also when my installation says its database is on J2.5.21, Joomla updates shouldn't put any sql update from before J2.5.21 on my system.

When your migration procedure tells you to install J2.5.21 and then update to J3.3.6 you needed to remove the j1.7.*.sql from J2.5.21. When replacing J2.5.21 with J2.5.27 you need to remove them from that distribution again. When replacing J2.5.21 with .22,.23,.24,.25,.26,.27 you'll have changed it for each update.

I personally happen to agree with you disagreeing (does that makes sense?) but I am very well convinced based on the exchange we had that with only one more release to come for J25 before EOL this issue won't be addressed which again I do understand as well

Leo

[sovainfo]

Yes, it makes sense.

Not too worried about J2.5, what worries me is that the problem is not taken serious. It shouldn't be that difficult to standardize the naming convention to avoid sorting problems, the same applies to removing unneeded scripts. Before copying them into administrator/components/com_admin/sql/updates.

Unfortunately the script.php only removes files afterwards. The files deleted there shouldn't exist in the distribution, they were installed by previous updates/installation.
The files mentioned in folder installation are going to be deleted anyway when installation is finished. So, it doesn't make sense to me why they are in there!
It doesn't delete the files that shouldn't have been copied over from the distribution either.

But what worries me the most is the complete radio silence on J3.4 and J4. In addition to finding new channels to communicate on and leaving the normal channels behind. But that is a bit offtopic, sorry.

[leolam]

Yes, it makes sense.

So I suggest you make a post in the CMS-list of the JBS here: https://groups.google.com/forum/#!forum ... [quote]But what worries me the most is the complete radio silence on J3.4 and J4. [/quote]It is in contrary extremely busy. We had a very successful Bug Squashing session over the last weekend globally where dozens and dozens of people around the globe worked in Teams to get rid of the issues as posted in the issue-tracker http://issues.joomla.org

As you can see from Michael's post here a lot is happening with hundreds of people involved https://groups.google.com/forum/#!topic ... f6iPHK7POk

Might look quite but with the Joomla World Conference next as well you can see that everybody is extremely busy in all teams to make Joomla better in all aspects

Leo

[Webdongle]

...

But what worries me the most is the complete radio silence on J3.4 and J4.

...
As you can see from Michael's post here a lot is happening with hundreds of people involved https://groups.google.com/forum/#!topic ... f6iPHK7POk...

And if you look at https://groups.google.com/forum/#!forum/joomla-dev-cms you will see the approach to other bugs that are being dealt with.

Another way to try and successfully upgrade when you receive "Database schema version (2.5.2-2013-02-03) does not match CMS version (3.1.1)" ... is to install 2.5.2 into a separate directory and edit the configuration.php to connect with the original database. That way you can update the original database because the files match. Then your site should update smoothly. You can download various versions from http://joomlacode.org/gf/project/joomla/frs/ you need to create an account and log in to see the releases in the menu on the left/

[leolam]

you will see the approach to other bugs that are being dealt with.

Monthy Python https://www.[youtube].com/watch?v=-ECUtkv2qV8

Leo

[Joe0411975]

I have also solve my (same) problem by deleting all 1.7 sql files from administrator/components/com_admin/sql/updates/mysql

then I must go back , and back, and back until I could find Database Fix, and after that Fix all worked like a charm... I lost few days to fix this...

It was very strange , all third party worked normal (akeeba admin tools worked) but core joomla components dont (all compnents show contoler.php error, ...)

Read all instructions about upgrade first and then all of these posts....

Summary:

I tried to upgrade joomla 2.5.28 to 3.4.1 (I had virtuemart and a lot third party extensions)

I disabled all plugins, modules,... (remember.php also)

Then I start joomla update, options, set to short term, upgrade it to 3.4.1 and finished with server hickup (errror 500), after which all core componets gave strange contoler.php error and third party as akeeba backup dont...

Upper fix is work for me...

Tnx to all and regards