When I install Drupal 8 on my Windows 10 home, WAMP 2.5.0 it tells me xdebug.max_nesting_level is set to 100. Set xdebug.max_nesting_level=256 in your PHP configuration file.

But, I already did that in php.ini ! (see attachment). Not only I did that, but I've refreshed wamp, restarted all wamp services, and manually cleared the browser cache! So what's causing this? In another PC it did work!

Any ideas?

CommentFileSizeAuthor
zzzzzzzzzzzzzzzzzzzzz.PNG14.18 KBBenia

Comments

Benosika created an issue. See original summary.

cilefen’s picture

cilefen commented

Have you checked phpinfo() to be sure the setting took effect?

cilefen’s picture

cilefen commented
Category: Bug report » Support request
Benia’s picture

Benia commented

phpinfo() ? Is this a fuction? I am not yet programming in PHP, can you detail please what should I check in simple words?

cilefen’s picture

cilefen commented

phpinfo() is how you see the PHP settings in effect on your server. WAMP should provide you this report somewhere. It is the way to find out the setting value.

This issue is about how to set a PHP INI setting in WAMP. As such, this is a WAMP issue and I suggest you use WAMP's support resources in order to find out how to set this configuration in the correct place. There is some connection to Drupal in that you usually need a high level on xdebug.max_nesting_level if using xdebug with Drupal, however, actually setting the value is out of scope for this issue queue.

I will add to this that if there is an installation problem that is not already discussed in another issue, you should include any error logs or messages in the issue summary.

Benia’s picture

Benia commented

As I mentioned I've stted it in the correct place --- In another PC it did work, so it is clear to me it's kind of a bug and therefore I don't agree with your analysis. If we want to bring Drupal to non\not-yet programmers (or just to people who want to save some more time), we need it to work perfectly with WAMP or XAMPP or whatever. In this case, it's really actually a bug since what I did here is the exact thing in did in another PC in which it did work!, and I know what I did and saw...

I would gladly attach the PHP error log but it does not mention anything after I see this error in the installation process.

cilefen’s picture

cilefen commented
Issue tags: +Needs issue summary update

Sorry but you have not explained the the problem in the issue summary clearly enough. Read it again. You wrote that WAMP told you the xdebug nesting value is too low. Was that actually Drupal saying that? Is this an error message in the install process? When does it appear? What is the exact message?

In any case, then you asked about setting an INI value in WAMP and I said to refer to WAMP's documentation on setting and checking INI values, which I stand by.

So although this could be a bug in Drupal, we can't know that until you explain the problem a little more and if relevant, you verify the xdebug setting that is running on this system.

sagar ramgade’s picture

sagar ramgade commented

You can access phpinfo() on wamp by going to http://localhost/?phpinfo=1, Also check the location of php configuration file it is loading. You can check it in phpinfo "Loaded Configuration File" setting, usually it is loaded from you apache bin folder. Modify the file which is listed in your phpinfo and restart the apache webserver so that it takes effect.

Benia’s picture

Benia commented

cilefen, I must disagree, I think it does enough clear from what In my Windows7 home & wamp 2.5.0 I can't install Drupal because it says there that that the xdebug nesting level is too low. Maybe it's indeed subjective in this case,

Anyhow, I've checked phpinfo() and it's 100 there (I didn't know I should check that --- Didn't know what is it when I published the question), thus it seems the problem isn't Drupal related and I'm suggesting to delete this thread.

cilefen’s picture

cilefen commented
Status: Active » Closed (works as designed)

@Benosika I am not trying to be difficult, but you wrote:

WAMP 2.5.0 it tells me xdebug.max_nesting_level is set to 100

Benia’s picture

Benia commented

I Wrote:

When I install Drupal 8 on my Windows 10 home, WAMP 2.5.0 it tells me xdebug.max_nesting_level is set to 100. Set xdebug.max_nesting_level=256 in your PHP configuration file.

For me it is indeed clear from here --- When I install Drupal 8. Especially because it's a known Drupal 8 issue. Anyway, I understand that one may claim I should have emphasized that even further.

cilefen’s picture

cilefen commented

I had been asking what originated the error message. It turns out it was Drupal, not WAMP. https://github.com/drupal/drupal/blob/8.0.x/core/modules/system/system.i...

Looking at the issue summary, I think a misplaced comma is to blame for the confusion.

Anyway, thank you for using Drupal 8.

jay.lee.bio’s picture

jay.lee.bio commented

@Benia, I had the same exact issue with the same exact configuration as you and somehow solved it without understanding it 100%. So I wrote a detailed blog post, which I hope will help you. The answer to your question is in step #2A.

P.S. @cilefen, I think it's actually a WAMP issue instead of Drupal. Or both. Or something. :)

Benia’s picture

Benia commented

I fixed the issue in similar ways back then though I went on to do all from my Ubuntu VM as Drush-master works there best.

I guess that now when MS inserted Ubuntu binaries into Win you could run Drush-master smooth enough quite soon on Win 10 as well...

Benia’s picture

Benia commented

I am sure the problem was WAMP originated. The guys at WAMP created 2 different php.ini files; It seems to be a known issue when people go and edit the file that can be easily traced under c:/wamp instead of the other deep file that should be entered from a shortcut inside the GUI (and if I'm not wrong is situated much deeper in the WAMP folder system).

Anyway, in all, or at least most times I edited the relevant php.ini file via the shortcut from the program, the Drupal install worked just fine.