Guest Posted June 27, 2007 Share Posted June 27, 2007 I have a couple scripts from a contribution that are generating blank pages instead of content. I have tried getting support on the issue in their own thread to no avail. I want to know how i can debug this problem so that i can see any errors and fix them. Is there a debug mode or function within osc that i can use? If not, then how can I process the scripts incrementally or line at a time? This is such a common problem, I can normally figure out where the error lies when doing my own work, but when theres includes and requires all over the place and tons of code... then it becomes quite a pain to figure out. If no debug mode, then how can i stop it from generating blank pages? :) Link to comment Share on other sites More sharing options...
Guest Posted June 27, 2007 Share Posted June 27, 2007 I have a couple scripts from a contribution that are generating blank pages instead of content. I have tried getting support on the issue in their own thread to no avail. I want to know how i can debug this problem so that i can see any errors and fix them. Is there a debug mode or function within osc that i can use? If not, then how can I process the scripts incrementally or line at a time? This is such a common problem, I can normally figure out where the error lies when doing my own work, but when theres includes and requires all over the place and tons of code... then it becomes quite a pain to figure out. If no debug mode, then how can i stop it from generating blank pages? :) Usually the white screen of death means that there is a missing ';' or /> or something like that somewhere in the code. It could be that the contribution is fighting with you osCom somehow. I'm sure that you probably already know that, but if there are a ton of includes and requires, it's going to be hard tracking down just where the error is. What you might want to do is comment out the majority of the includes and requires, and then one at a time uncomment them and see if the page comes up at all. That way you can at least track down where the error is most likely to be. Link to comment Share on other sites More sharing options...
gazzzzzza Posted June 27, 2007 Share Posted June 27, 2007 Hi You might want to try turning error reporting on for PHP on the server (if its your server) Or you may be able to do it via a htaccess file on your website only. create a file called .htaccess if there isnt one in the root of your site already put the following in it php_value error_reporting 6135 php_value display_errors on (i think thats right although im a bit rusty!) provided your server is setup to allow htaccess overrides of php values, then you should see the actual errors on screen. I must stress that you should turn error displays off once the site is ready, as it is a security risk to leave them there for anyone to see! always here to offer some useless advice.... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.