Closed (works as designed)
Project:
Drupal core
Version:
7.63
Component:
base system
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Jan 2019 at 10:49 UTC
Updated:
27 Mar 2019 at 21:16 UTC
Jump to comment: Most recent
Comments
Comment #2
WiseMike commentedComment #3
mrgoodfellow commentedDo you have any modules enabled that effect menu management?
I was unable to duplicate this issue.
When reviewing the hidden value on the table menu_links I am showing either a value of: 0, 1, or -1
I do not see any null values under 'hidden' on this table.
When adding a new menu item I am showing a value of 0 for 'hidden' on the new menu item.
Try disabling any enabled modules and see if the issue persists.
Comment #4
xjmAlso, what version were you updating from? And can you provide a full backtrace?
I can't really think of a way the 7.62 or 7.63 releases themselves could have introduced a problem like this, so the most likely causes are an incomplete site update (try running
update.phpagain and then check the status report to confirm the version is correctly set to 7.63), or a contributed or custom module.Comment #5
WiseMike commentedOnce I got corrupted table {menu_router}
I restored it from a backup. Could it be related to this error?
Comment #6
mrgoodfellow commented@WiseMike Its possible that the table could be corrupted. If you restored from a backup and it was missing columns it could cause this.
I would suggest doing the following:
You could backup the correct table schema from the clean install and then use that to restore the correct schema, then re-insert your production data.
You could also manually correct any inconsistencies using SQL commands to alter the table.
https://www.w3schools.com/sql/sql_alter.asp
This is my schema for these tables in a clean install:
I hope this helps!
Comment #7
andyg5000If it's not related to a corrupt database, my guess is that it's a contrib module that's trying load and save a menu link without proper checking. For example, I just filed #3043925: Deleted menu items can cause fatal error where taxonomy_menu was doing just that.
I'm going to close this one out, but please reopen if you don't think that's the issue!