Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation Incomplete with XDebug enabled #904

Closed
snky1987 opened this issue Jan 5, 2015 · 4 comments
Closed

Installation Incomplete with XDebug enabled #904

snky1987 opened this issue Jan 5, 2015 · 4 comments
Labels
bug report Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: needs update

Comments

@snky1987
Copy link

snky1987 commented Jan 5, 2015

With XDebug enabled /setup/index.php/install route in Google Developer Tools throws an error:
"Maximum function nesting level of '100' reached, aborting!"

Which cause Installation error at 93% in my case.
I resolved this issue using xdebug.max_nesting_level = 200 in my php.ini but it may cause problems in the future with some users.

using ini_set() function may resolve the problem but it will not work for a users who aren't allowed to override php.ini in PHP code.

Any ideas how to fix it permanently ?

@orlangur
Copy link
Contributor

orlangur commented Jan 5, 2015

In fact, xdebug.max_nesting_level = 200 is a system requirement when XDebug enabled.

So, some check similar to, for example, MySQL version check could be implemented to enforce this requirement. Override ini value silently does not seem a viable solution to me, better just describe ways to set the value in hint.

@snky1987
Copy link
Author

snky1987 commented Jan 6, 2015

@orlangur I agree. It is something easy to forget for a developer (and certainly hard to find and fix for a newbie user of Magento with just minimum knowledge of PHP). There may be some kind of misc. check to find out this nesting_level issue and also permission level in TEMP directory.

I had this issue few times during installation process tests that Windows 7 for some reason blocked unlink() of install.log in TEMP dir. (permission denied) but it's hard to reproduce this error (I just had it 2 times during 20 installation processes).

So yes. It may be useful to have some kind of Miscellaneous tests as well.

@monkeysee
Copy link
Contributor

Internal ticket: MAGETWO-33027

@muasir muasir added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jan 23, 2015
magento-team pushed a commit that referenced this issue May 15, 2015
magento-team pushed a commit that referenced this issue May 15, 2015


- fixed issue
- implemented unified output format for failed setting check
magento-team pushed a commit that referenced this issue May 15, 2015
magento-team pushed a commit that referenced this issue May 15, 2015
@vpelipenko
Copy link
Contributor

@snky1987, fix is available from 0.74.0-beta9. Please, let us know if it will occur again.

magento-team pushed a commit that referenced this issue Mar 15, 2017
okorshenko pushed a commit that referenced this issue Dec 1, 2017
… return is not authorized #904

 - Merge Pull Request magento-engcom/magento2ce#904 from RomaKis/magento2:9468
 - Merged commits:
   1. adf18dc
okorshenko pushed a commit that referenced this issue Dec 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: needs update
Projects
None yet
Development

No branches or pull requests

6 participants