Hi everyone,
I still search for a solution to show the actual fatal error instead of the default 500 internal sever error page. Same thing when I use <mvexit>. It gets me the default 500 error instead of exiting the program.
I'm on Ubuntu 11.10 (GNU/Linux 3.0.0-32-server x86_64) but it happen with every Ubuntu server I have (even the latest versions). I'm pretty sure it's a setting somewhere in Apache2 but I just cannot find it.
I can debug with the miva debug file, but for small errors (like a sql query) it's faster to see it on screen. And also, cannot use mvexit anymore :(
Thank you in advance if you have any idea :)
Emma
I still search for a solution to show the actual fatal error instead of the default 500 internal sever error page. Same thing when I use <mvexit>. It gets me the default 500 error instead of exiting the program.
I'm on Ubuntu 11.10 (GNU/Linux 3.0.0-32-server x86_64) but it happen with every Ubuntu server I have (even the latest versions). I'm pretty sure it's a setting somewhere in Apache2 but I just cannot find it.
I can debug with the miva debug file, but for small errors (like a sql query) it's faster to see it on screen. And also, cannot use mvexit anymore :(
Thank you in advance if you have any idea :)
Emma
Comment