When editing a menu with a large number of links (the default Administration menu displays this behavior) from the link list view, checking/unchecking the "Enabled" doesn't actually cause the menu to be edited. After the page reloads, no edit has been made to the enabled/disabled state of links. The logs confirm that no edit was actually made. No errors/warnings/notices appear in the log. Expected behavior is that any link that had "enabled" checked or unchecked would then have that change made after the save.

The issue has been seen across a couple of our projects and is consistently an issue on local development environments. Pantheon hosted remotes seem to be less impacted by this than other hosting (Pantheon does have their own patched version of core. May or may not be related). Drupal sites running core versions 8.2.6 and 8.2.3 show this issue. It does not appear to be a (strictly) memory issue, setting local php memory limit to match working hosted environments (512MB) does not resolve the issue. AWS hosted remotes do show this problem. Menus with small numbers of links (~40 or less) do not show this problem.

To replicate: edit the "Administration" menu (or any menu with a similarly large number of links), disable one or more links using only the UI checkboxes. Save. Possibly needs to be done on a non-Pantheon hosted environment.

Comments

ccasals created an issue. See original summary.

ccasals’s picture

Issue summary: View changes

Version: 8.2.6 » 8.2.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.2.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

pameeela’s picture

Status: Active » Closed (duplicate)
Issue tags: +Bug Smash Initiative

The issue is with max_input_vars, not memory. There is an issue to resolve this broadly at #1565704: Core interfaces can go over max_input_vars so I'm going to close this as a duplicate.