?
avatar Fedik
Fedik
24 Mar 2016

I got whole menu broken after upgrade to 3.5, when tried create new menu item
... in some reason.

Steps to reproduce the issue

Go to menu manager and create new menu (any type), without parent.

Before
screen 2016-03-24 17 43 51 500x418
After
screen 2016-03-24 17 44 27 500x418

Also it breaks the level for ALL menu items on the site.

System information (as much as possible)

php: Linux 3.13.0-55-generic #
94-Ubuntu SMP Thu Jun 18 00:28:41 UTC 2015 i686
dbversion: 5.5.47-0ubuntu0.14.04.1
dbcollation: utf8_general_ci
dbconnectioncollation: utf8mb4_general_ci
phpversion: 5.5.9-1ubuntu4.14
server: Apache/2.4.7 (Ubuntu)
sapi_name: apache2handler
version: Joomla! 3.5.1-dev Development [ Unicorn ] 21-March-2016 22:00 GMT
platform: Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
useragent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

systeminfo-2016-03-24T15-55-51+00-00.txt

avatar Fedik Fedik - open - 24 Mar 2016
avatar Fedik
Fedik - comment - 24 Mar 2016

hm, in database #__menu:
Joomla 3.4.x: Menu_Item_Root level = 0
Joomla 3.5.x: Menu_Item_Root level = 2 - changes after create a new menu item

Quick fix is to change Menu_Item_Root level to 0 in #__menu, manually. And reorder menu items.
But after making a new menu item the levels is broken again.

avatar brianteeman
brianteeman - comment - 24 Mar 2016

Is this a very old site? I seem to recall this as an issue in the past and it was caused by an error in one of the migration components


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9572.

avatar andrepereiradasilva
andrepereiradasilva - comment - 24 Mar 2016

@Fedik i can't reproduce this.

avatar Fedik
Fedik - comment - 24 Mar 2016

hm, yes, they are old (since joomla 3.3.x, I guess) ... was 2 sites on different servers, and one local dev setup (before upgrade they was 3.4.8) .. actually there is more, but I had to stop the upgrade because of this

@brianteeman do you remember which issue it was?

avatar brianteeman brianteeman - change - 24 Mar 2016
Labels Added: ?
avatar photodude
photodude - comment - 24 Mar 2016

Off the top of my head, I think the menu "Rebuild" button was added to address something like this.

avatar bertmert
bertmert - comment - 25 Mar 2016

An identical issue was reported in a german forum. There ALL levels (also backend menus) were increased by 9 (10 instead 1 and so on) and lft/rgt had extremely huge values. A friend of mine helped after some unsuccessfull tests:

  • Save menu items again: unsuccessful.
  • Create additional menu item with parent in highest menu level (root): unsuccessful
  • Click Rebuild button: All items in database table had a "root/" in field link afterwards. But nothing else changed.

  • Correcting table:

  • All level decreased by 9 (9 to 0, 10 to 1 and so on).

  • All link: Remove "root/"
  • Set lft of ROOT to 0.
  • Click Rebuild button afterwards. TE reported success but after a PM to him is not willing to test with a new menu item. He sent us a database export: lft/rgt and all other fields looked fine.
avatar brianteeman
brianteeman - comment - 25 Mar 2016

This doc should be relevant
https://docs.joomla.org/Fixing_the_assets_table


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9572.

avatar chrisdavenport
chrisdavenport - comment - 25 Mar 2016

@Fedik Are you using the PDO driver by any chance?

I can reproduce this exact behaviour using PDO. For a possible explanation see #9601

avatar Fedik
Fedik - comment - 26 Mar 2016

@chrisdavenport yes, I use PDO,
I try to test that PR soon

avatar Fedik
Fedik - comment - 26 Mar 2016

yep, MySQLi works fine, PDO fail,
I wonder what was changed there since 3.4.8, as there all worked fine

btw #9601 fix the issue

avatar Fedik
Fedik - comment - 26 Mar 2016

see #9601 for fix

avatar Fedik Fedik - change - 26 Mar 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-03-26 11:06:02
Closed_By Fedik
avatar Fedik Fedik - close - 26 Mar 2016

Add a Comment

Login with GitHub to post a comment