Closed (fixed)
Project:
Admin Toolbar
Version:
3.x-dev
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Dec 2023 at 07:45 UTC
Updated:
2 Jun 2025 at 17:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
sidharth_soman commentedI don't really think there's a need to include the '#max' property since there is already a warning about performance issues given a large number of sub-menus.
For now, here's a patch with max=500 and min=1.
Comment #3
prashant.cComment #5
sandeep_k commentedVerified and tested patch f3408119.patch on Drupal version- 9.5.11-dev. The patch was applied successfully and looks good to me.
Testing Steps:
Testing Results:
f3408119.patch was applied successfully & validations are added now for min (1)and max (500) values.
Moving this ticket to RTBC.
Comment #6
sandeep_k commentedComment #8
adriancidComment #10
justcaldwellJust noting that this change broke prior functionality with little/no notice. In the past a value of zero resulted in creating links for all entities with no need to designate a max number.
In our case, the previous value of '0' was forced to '1' so all but the first of each bundle link disappeared unexpectedly. At a minimum, seems like there should have been an update that set 'invalid' values to the module default of 20.