?
avatar sshcli
sshcli
14 Apr 2017

Steps to reproduce the issue

Upgrade from 3.6.5 to 3.7.0-rc3

Expected result

Actual result

error1

warning1

System information (as much as possible)

Joomla! 3.7.0-rc3
PHP 7.1.3
MySQL 5.6.35

Additional comments

avatar sshcli sshcli - open - 14 Apr 2017
avatar joomla-cms-bot joomla-cms-bot - change - 14 Apr 2017
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 14 Apr 2017
avatar zero-24
zero-24 - comment - 14 Apr 2017

@sshcli please double check that you updated from 3.6.5. The error looks like you updated from beta or other dev version.

avatar mbabker
mbabker - comment - 14 Apr 2017

Rename the alias column in the #__fields table to name and you're good. Closing as a known issue since maintenance team has elected to not support non-stable updates.

avatar mbabker mbabker - change - 14 Apr 2017
Status New Closed
Closed_Date 0000-00-00 00:00:00 2017-04-14 17:44:58
Closed_By mbabker
avatar mbabker mbabker - close - 14 Apr 2017
avatar zero-24
zero-24 - comment - 14 Apr 2017

This is why i have asked to double check if he direct updated from 3.6.5 if yes than this is a valid issue.

avatar sshcli
sshcli - comment - 15 Apr 2017

@zero-24 said: sshcli please double check that you updated from 3.6.5. The error looks like you updated from beta or other dev version.

I have tested with both:
Update from 3.6.5 and got the warning
Update from 3.7.0-rc1 and got the error

@mbabker said: Rename the alias column in the #__fields table to name and you're good.

The "Alias" column doesn't exist in my installation. (Updated from 3.6.5 to 3.7.0-rc3)
I only have the column "name"
name

Maybe we are facing another bug, very similar but different

avatar zero-24
zero-24 - comment - 15 Apr 2017

I can not confirm this kind of errors on my installation. I have just tryed 3.6.5 -> 3.7rc3-dev

avatar sshcli
sshcli - comment - 19 Apr 2017

@mbabker said: Rename the alias column in the #__fields table to name and you're good.

Yes, it works, Thanks

@zero-24 said: I can not confirm this kind of errors on my installation. I have just tryed 3.6.5 -> 3.7rc3-dev

I think you could reproduce the issue by making a clean installation of 3.6.5 and then unzip 3.7.0-rc4 in the root directory of your server.

Add a Comment

Login with GitHub to post a comment