-
- 258 Posts
Catch the errors in your own code so they don’t propogate up to the core code.
-
- 9 Posts
That would be ideal, but errors do happen and I’d like to clean up that error page. How do I do that? Thank you.
-
- 258 Posts
That unfortunately required hacking the core code as that’s currently not a configurable option. Look in manager/include/document.parser.php and search for the error message strings in there
-
- 9 Posts
That is a gigantic file. I searched through it some and found: $php_errormsg. Where would that variable be stored?
Thanks.
-
- 258 Posts
Look at the function messageQuit on line 2319.
But I would still *strongly* recommend you don’t hack this -- it’s much easier to check and catch errors within your own code. This function should only get called for php syntax or sql errors. Your users should never see it if you’ve tested you site properly and have made your own error checking code.
-
- 9 Posts
It only happens every now and then (seems to have when the server’s load is high and I guess that Apache and/or PHP fails). I just wanted to add a note on there - not really changing it around that much.
Thanks!