nurkka Posted 4 hours ago Share Posted 4 hours ago Here is a quick report regarding one of the newest versions. I tested 4.26.42. In this version, the PHP console doesn't work anymore: The output window only shows "0:". Tested on two different hosting providers with three different PW installations. Downgrading to Tracy Debugger 4.26.26 fixes the problem. Link to comment Share on other sites More sharing options...
adrian Posted 4 hours ago Share Posted 4 hours ago Hi @nurkka- sorry you're having issues. Can you please try if a modules refresh fixes things? Link to comment Share on other sites More sharing options...
nurkka Posted 1 hour ago Author Share Posted 1 hour ago Thanks @adrian , refreshing the modules did not change anything, but I could narrow the issue down a little bit, because it just occurs on websites of the same "type" I was making. I.e. they are using the same set of modules and a lot of the same template code. I think I will now search in my template code first ... Link to comment Share on other sites More sharing options...
adrian Posted 1 hour ago Share Posted 1 hour ago Interesting - does the console panel work when you using it from the PW admin, rather than the frontend of the site? If you can't figure out the issue, perhaps a trial and error approach of going through the Tracy versions to see where the issue starts occurring might be the quickest in the end. Choose a version in the middle between the current, ie 4.26.34 and if that works, split the difference between it and .42 but if it doesn't, go for .30 - you get the idea and hopefully it won't take long to figure out which one breaks things. Link to comment Share on other sites More sharing options...
nurkka Posted 48 minutes ago Author Share Posted 48 minutes ago I tested all TracyDebugger versions back to 4.26.26 and the issue starts with version 4.26.27. It is the following line in /panels/ConsolePanel.php: # /panels/ConsolePanel.php line 406 xmlhttp.open("POST", "/", true); When I change the line to it's previous version, it works for me: xmlhttp.open("POST", "./", true); Could that be some hosting specific issue? Could it be triggered by .htaccess rules? Okay, I deleted my ready.php and it works too, so it's likely a correlation with some crazy redirect stuff I am using. I'll test that ... Edit: Yes, my redirect code in ready.php caused the error. Thanks for your help @adrian – and thanks again for the great TracyDebugger module. I couldn't imagine to ever work without it again! 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