Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I've been adding menu items in main navigation, which included links to custom content as well as pages generated by views. After adding 5th top level menu item all of my buttons got disabled and only Home is now left visible.
Any time I try to enable, I receive message that all is saved, but menu items are still disabled.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | d8db.zip | 788.31 KB | sashkernel |
| #6 | Menus.JPG | 77.31 KB | sashkernel |
| #5 | sshot-2.png | 3.32 KB | hussainweb |
| #5 | sshot-1.png | 26.25 KB | hussainweb |
Comments
Comment #2
dawehnerThanks for reporting, I'm wondering whether you managed to reproduce the issue and can give a step by step instruction to reproduce it?
Comment #3
sashkernel CreditAttribution: sashkernel commented--Edited-- sorry posted to the wrong thread at the beginning.
What I did is created 3 types of content, created 3 views to list that content. Each view was a top level menu item and individual content pages were child menu items.
I have following contributed modules installed:
- Admin Toolbar
- Calendar
- Field Group
- Views Templates
I tried to disable those modules to eliminate any 3rd party bug but they all became grayed out and I can't really do anything with them.
Comment #4
sashkernel CreditAttribution: sashkernel commentedJust figured out how to disable modules but issue still persists.
Comment #5
hussainwebI am not able to reproduce this. See the screenshots. c1, c2, and c3 are views. They have child links which are content.
Comment #6
sashkernel CreditAttribution: sashkernel commentedHere's what I have
Departments - View (Lists departments)
-- Finance - Content
Division - View
-- Division 1... - Content
This happened when I tried to add a 3rd view that lists 3rd type of content. I removed it from the menu to see if that was it, but nothing changed. I still cannot enable those menu items.
Comment #7
hussainwebAre the views disabled by any chance?
Comment #8
sashkernel CreditAttribution: sashkernel commentedviews are enabled. Even if they were disabled all child items should be able to be enabled.
Comment #9
sashkernel CreditAttribution: sashkernel commentedThis is my dev site, so I think I should be able to open access to it for you guys to see the problem. Just need to verify some security settings.
Comment #10
PQ CreditAttribution: PQ at D. Agency commentedIf you go into the edit page for the link, enable and save it there then does the enabled status stick?
If so then we'd know that it's something to do with the link list UI.
I've had a similar issue on a D7 site which turned out to be caused by PHP's max_input_vars limit being exceeded. Although that was a very large menu, so it's less likely to be this in your case unless your max_input_vars is very low.
Comment #11
sashkernel CreditAttribution: sashkernel commentedNope, when editing content and enabling menu there does not do anything.
One thing I noticed: my parent menu items were created manually; I just created a menu item via one of those views and it worked.
I also tried to move child item from disabled menu to the working one; I got successful Saved message, but change did not occur.
I'm uploading DB dump from my D8 test server so you guys could actually reproduce the copy of what I have.
I set login to following
root/password
There is one module active on top of default installation, which is Admin Toolbar.
Hope this helps
Comment #12
Denis Danielyan CreditAttribution: Denis Danielyan as a volunteer commentedWe experienced the same issue here. But only on the staging server (which of course cannot be debugged).
max_input_vars cannot be the issue as it is set to 1000.
It turned out to be that suhosin was active on the staging Server that caused the problem as it chopped off long variable names.
To verify the issue, I created a small php page that prints the $_POST variable (print_r($_POST); die;). Then logged the POST command in Chrome, (network tab, click on preserve log), right click the post command and choose "copy as cURL". Change the URL in the cURL-statement to use the print-php page and verify that the arguments returned are the same that are submitted.
If they are not, your problem is with the webserver.
Comment #13
dawehnerThank you for filing this issue.
I hope you haven't yet tried to submit the user permissions form. Suhosin indeed causes often issues in Drupal :(
For comments like #2630776-6: Suhosin causes menu items to be disabled we have another issue already: #2464077: Menu link overrides are lost after cache rebuild.
Comment #14
Denis Danielyan CreditAttribution: Denis Danielyan as a volunteer commentedWe actually had a whole bunch of weird errors reported from the client because of this problem.
To give a future reference to others that have the same problem here a quick recap of which settings changed we changed.
suhosin.request.max_array_index_length
suhosin.post.max_array_index_length
This is for the names. When the names the UUID takes up a major part of the 64 characters that are allowed by default so it was increased to at least 128
suhosin.request.max_varname_length
suhosin.post.max_varname_length
Just to be save, we increased the value from the default 64 to 128
@dawehner:
This was unfortunately a case of "it runs on my machine" and the client ran into it. We're much too happy with config-import/export to make our fingers dirty on the non-dev servers ;-).
Comment #15
cilefen CreditAttribution: cilefen commentedComment #20
catchI don't think there's anything that can be done here, additionally suhosin doesn't exist in quite the same way in PHP 8 as far as I know. Closing as outdated.