Search the Community
Showing results for tags 'xdebug'.
Found 5 results
-
Trouble Debugging ProcessWire using XDebug + PHPStorm
FrancisChung posted a topic in General Support
Hi there, I'm a newbie and I'm trying to learn more about Processwire so I've setup XDebug + PHPStorm to get some real time debugging happening. I've noticed that no matter where i put a breakpoint in any of my php modules, it seems to return the following error. Error: __debuginfo() must return an array (line 55 of /Users/FrancisChung/site/Test/templates/head.inc) This error message was shown because you are logged in as a Superuser. Error has been logged. I was wondering if fellow Processwire users have a similar setup, and was successful in getting debugging going. I've also read this forum post: https://processwire.com/talk/topic/1611-yes-debugging-templates-and-core-code-works/ I'm also aware there's an issue with XDebug and Processwire: https://github.com/ryancramerdesign/ProcessWire/issues/1316 -
This afternoon i was setting up a new laptop with Win7 64bits. Having used it in the past with no problems i decided to use Wampserver 2.5 to setup my webdev environment. Having set up an existing project and a vanilla PW install i noticed that some front-end pages took quite long to respond/render. After logging in i also noticed this in the back-end. Especially opening a template edit page performed bad, with a noticeable 2 to 3 seconds delay in the response. This was not at all the case with the live site running the same code base. After some hair-pulling i discovered that it was xdebug slowing things down. In Wampserver it comes bundled with the following settings in php.ini (to which i added the max_nesting_level because the default 100 will cause problems in PW) : ; XDEBUG Extension zend_extension = "c:/wamp/bin/php/php5.5.12/zend_ext/php_xdebug-2.2.5-5.5-vc11-x86_64.dll" ;xdebug xdebug.remote_enable = off xdebug.profiler_enable = off xdebug.profiler_enable_trigger = off xdebug.profiler_output_name = cachegrind.out.%t.%p xdebug.profiler_output_dir = "c:/wamp/tmp" xdebug.show_local_vars=0 xdebug.max_nesting_level = 200 After commenting out all of the above, basically disabling xdebug altogether, my PW installs where back to normal, snappy performance. Because i don't use xdebug for debugging or profiling i'm fine with totally disabling it. This might be a tip for people experiencing bad performance in relation to xdebug. What i do find surprising is that with the above settings no actual debugging/profiling is enabled. The only thing xdebug needs to do is collect info for it's stack trace. Would this really cause such slowdowns?
-
Hi, Out of the blue, I am getting this error: Fatal error: Maximum function nesting level of '100' reached, aborting! in C:\data\My Dropbox\www\showled.com\wire\core\Pages.php on line 628 It happens when I try to 'edit' pages under a certain node It used to work and I am pretty sure I didn't change anything Any ideas Sylvio -
on a Windows machine, localhost... Version 2.4 worked pretty fine, I removed it totally and installed version 2.5 and it did not work - see the errors below! the first error went away after putting this into the config.php $config->protectCSRF = false; $config->sessionChallenge = false; $config->sessionFingerprint = false; and then I installed again 2.4 and this version worked again perfectly... don´t know what to do... When I try to drag and drop a picture into the picture field this error comes: ------"this request was aborted because it appears to be forged." and when I want save a page this error comes: Error: Maximum function nesting level of '100' reached, aborting! (line 113 of C:\EasyPHP\data\localweb\projects\ebay2\wire\core\WireData.php) This error message was shown because you are logged in as a Superuser. Error has been logged. -
Hi, Since a few days I get a 'Maximum nesting level reached (100)' at each page I click to edit in de backend. After a refresh F5 it loads. It talks about line 114 of Data.php and sometimes 291. I looked up 114 and that part is in the getter. It happens not always, but often, and on all kinda templates... Funny thing is that after I F5ed the page, I can edit it directly again after it. A bit strange I think. Any clues where I can start searching for the problem? I cannot imagine it is a bug in PW because then others had major problems so it must have to do with a module I installed or whatsoever. I didn't build one myself and they're all from the repository, no manual additions.
