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.
Drupal 8 checks for xdebug's max nesting level in system.install. If under 256 it will throw an error:
exception 'Drupal\Core\Installer\Exception\InstallerException' with message 'Xdebug settings: xdebug.max_nesting_level is set to <em [error]
class="placeholder">200</em>.
Set <code>xdebug.max_nesting_level=256
in your PHP configuration as some pages in your Drupal site will not work when this setting is too
low.' in /var/www/drupal8/core/includes/install.core.inc:2279
Attached patch changes the default from 200 --> 256.
Comment | File | Size | Author |
---|---|---|---|
#2 | xdebug.max_nesting_level-2488300-1.patch | 528 bytes | entendu |
#1 | xdebug.max_nesting_level-2488300.patch | 818 bytes | entendu |
Comments
Comment #1
entendu CreditAttribution: entendu commentedComment #2
entendu CreditAttribution: entendu for eBay Enterprise commentedWhoops, re-rolling without my NFS config ;)
Comment #3
dasginganinjaI too ran into this yesterday at DrupalCon LA code sprints.
I just setup a new box with this patch applied and did not encounter the error afterwards. Tested and working!!
Comment #4
joelbloch CreditAttribution: joelbloch commentedHello,
I am very new to everything, I installed VirtualBox, vagrant and vdd yesterday. I am not familiar at all with drupal, with git, with xdebug or anything.
When I try to access the drupal8 site for the first time, it seems I encounter the same error:
xdebug.max_nesting_level is set to 200.
Set xdebug.max_nesting_level=256 in your PHP configuration as some pages in your Drupal site will not work when this setting is too low.
I manually edited the vdd_xdebug.ini.erb to type 256 instead of 200, but it does not do anything.
Could you tell me step by step how to fix my problem? How do I apply your patch, what should I do from the start to the end?
I want to use drupal, I am blocked at the step -2, and it's quite frustrating.
Thanks!
Comment #5
GiorgosK@joelbloch
you need to destroy and recreate your vagrant vm before this setting takes effect
+1 for the patch, should be committed
Comment #6
cparrish817 CreditAttribution: cparrish817 as a volunteer and commentedI can confirm that I was getting that error and that manually updating my vdd_xdebug.ini.erb file to 256 fixed it. While I didn't use the patch directly I'd also like to see it committed.
Comment #7
vellines CreditAttribution: vellines as a volunteer commentedFollowing the VDD Getting Started Doc, I also got this exception when installing D8 via Drush. Applying the patch from comment #2 and rebuilding the VM per comment #5 resolved the issue.
Comment #8
sqndr CreditAttribution: sqndr as a volunteer commentedAlso confirming that after I applied the patch, the error disappeared. Please commit! :)
Comment #9
wheatpenny CreditAttribution: wheatpenny commentedMy goal was to get the latest D8 commit up and running on VDD. The patch from this issue and from https://www.drupal.org/node/2327263 did that for me.
+1 for committing this patch.
Comment #10
siliconmeadow CreditAttribution: siliconmeadow as a volunteer commentedSame goal and same outcome as wheatpenny.
+1 to commit this patch.
Comment #11
siliconmeadow CreditAttribution: siliconmeadow as a volunteer commentedRegarding #2488300-4: xdebug.max_nesting_level too low and #2488300-5: xdebug.max_nesting_level too low above, surely
../vdd$ vagrant provision
would be a quicker and less destructive way of adding the new value?
Comment #12
wheatpenny CreditAttribution: wheatpenny commentedSee https://www.drupal.org/node/2327263#comment-10284857 for the testing that I did for the #2 patch above. I was able to install Drupal 8 combined with the patch from that issue. In my opinion, this patch is RTBC and ready to go.
Comment #14
ericrdb CreditAttribution: ericrdb commentedThanks for working on this.