theo Posted May 15, 2018 Share Posted May 15, 2018 A specific page (frontend) is not being loaded when $config->debug is true; It is a similar observation as described here before: If I set $config->debug to false, it works. No error message, nothing. The page uses PageTableExtended, but it is not that complex (9 pages in involved in the PT). What could be the reason? What can I do about it? Did you have similar observations? Thank you. PHP 7.07 / PW 3.0.94 Link to comment Share on other sites More sharing options...
flydev Posted May 15, 2018 Share Posted May 15, 2018 16 minutes ago, theo said: No error message, nothing. Hi @theo is there something in the apache / nginx / php* logs ? Link to comment Share on other sites More sharing options...
theo Posted May 15, 2018 Author Share Posted May 15, 2018 @flydev No, I can't see any error in /var/log/apache2/error_log. Only access_log has an entry (normal). Thank you. Link to comment Share on other sites More sharing options...
theo Posted May 15, 2018 Author Share Posted May 15, 2018 EDIT: It seems that uninstalling ChromePhpLogger helps in this case. But still, this is a general issue imho (Memory?). I think it is not directly a problem of ChromePhpLogger. Thank you. Link to comment Share on other sites More sharing options...
dragan Posted May 15, 2018 Share Posted May 15, 2018 Do you have Tracy Debugger installed? Do you see anything suspicious there when loading that page? Link to comment Share on other sites More sharing options...
theo Posted May 15, 2018 Author Share Posted May 15, 2018 @dragan Yes, I've tested this before, then disabled Tracy, AOS and stuff. Then I remembered ChromePhpLogger and disabled this one. The latter helped. Could be some recursion / stack problem? The problem is gone for now, but It is a little scaring, as I have no indication about what went actually wrong. It might happen again? Link to comment Share on other sites More sharing options...
BitPoet Posted May 16, 2018 Share Posted May 16, 2018 On 5/15/2018 at 1:28 PM, theo said: The problem is gone for now, but It is a little scaring, as I have no indication about what went actually wrong. What I have sometimes found helpful in such cases is to bootstrap PW and render the page in question from the command line, i.e. something like php -r 'namepsace ProcessWire; include("index.php"); $p = $pages->get("ID_OR_PATH_OF_YOUR_PAGE"); $p->render();' since PHP CLI is usually a bit more talkative when things go haywire. Might be worth a try. 2 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now