Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.7b3 update Notice: Undefined property: stdClass::$client_id in libraries\vendor\joomla\utilities\src\ArrayHelper.php on line 521 and 522 #14271

Closed
jsubri opened this issue Feb 27, 2017 · 4 comments

Comments

@jsubri
Copy link
Contributor

jsubri commented Feb 27, 2017

Steps to reproduce the issue

I took a 3.6.5 site and tried to update to 3.7b3 over the test channel, the update didn't completed, similar than #13624

Expected result

Successful update.

Actual result

During update process:
Notice: Undefined property: stdClass::$client_id in D:\www\htdocs\upgrade-to-j37b3\libraries\vendor\joomla\utilities\src\ArrayHelper.php on line 521
Notice: Undefined property: stdClass::$client_id in D:\www\htdocs\upgrade-to-j37b3\libraries\vendor\joomla\utilities\src\ArrayHelper.php on line 522

Navigating in com_menus showed briefly the below screen shot.
j37b3-upgrade

System information (as much as possible)

Windows7, php5.4, mysql (using mysli), multi-langage (3) with "Menu Type: mainmenu" assigned to all languages and the 3 corresponding "Menu Type: mainmenu-en" + "Menu Type: mainmenu-nl" + "Menu Type: mainmenu-fr"

Additional comments

found a missing column in #__menu_types
alter table #__menu_types add COLUMN client_id int(11) NOT NULL DEFAULT '0'; helped to progress a bit. Might be missing in administrator/components/com_admin/sql/updates/mysql/

@zero-24
Copy link
Contributor

zero-24 commented Feb 28, 2017

@jsubri please double check that you come from 3.6.5 and not any other beta version of 3.7.0.

As the line you mention is there see: https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_admin/sql/updates/mysql/3.7.0-2016-11-19.sql#L1

@jsubri
Copy link
Contributor Author

jsubri commented Mar 1, 2017

Starting point was a 3.6.5. I found out the site was initially created with 3.6.3-dev, 3.6.3 was applied then migrated to 3.6.4, 3.6.5. Fix button used each time. I fixed the issue by creating the column manually, I don't understand the reason the upgrade failed. Just noted the optional word "COLUMN" is not in the sql file,
Going to close this. Thank you

@jsubri jsubri closed this as completed Mar 1, 2017
@wojsmol
Copy link
Contributor

wojsmol commented Mar 2, 2017

@jsubri COLUMN is not optional in the Joomla! SQL parser (see https://github.com/joomla/joomla-cms/blob/staging/libraries/cms/schema/changeitem/mysql.php#L79)

@wojsmol
Copy link
Contributor

wojsmol commented Mar 2, 2017

@jsubri @zero-24 Plese test #14312

wilsonge pushed a commit that referenced this issue Mar 2, 2017
…aries\vendor\joomla\utilities\src\ArrayHelper.php on line 521 and 522 (#14312)

* Simple fix for #14271

* fix typo
jjaracz pushed a commit to jjaracz/joomla-cms that referenced this issue Mar 9, 2017
…aries\vendor\joomla\utilities\src\ArrayHelper.php on line 521 and 522 (joomla#14312)

* Simple fix for joomla#14271

* fix typo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants