No error reporting to screen on v.2.6.xx

[GJC Web Design]

Hi,

Not sure if others can prove this but this is what I've found.

2 installs - 1 is v2.0.26d - the other v2.6.4

same server  - cPanel/cloud Linux - have access to php settings - all reporting to on incl. logging and on screen reporting

the v2.6.4 never reports (in this case deliberate) php syntax errors to screen but they are logged
the v2.0.26d shows errors to screen and logged (this is how I like it when debugging and developing)

Have proven this by errors on non VM pages print to screen on both installs -
tested error in e.g. module

on v2.0.26d the module error prints to screen on VM pages

but again on v2.6.4 only a white screen on a module error - printed to screen on non VM page

Is this behaviour by design?  It isn't user friendly for debugging issues..

I tried v2.6.4 with VM debugging on - Joomla reporting set to max - error on VM template

notices and warnings in this case print out until the fatal php error is reached and php stops

No fatal error printed out though  - unless people know to look at their logs and where to find them this makes debugging harder than it should.

Cheers

[Milbo]

Yes, it is the first time that we use a leggings for our users.

just enable vmdebug and you see the error reporting. We will add another option in the vm config.

[GJC Web Design]

I tried v2.6.4 with VM debugging on - Joomla reporting set to max - error on VM template

notices and warnings in this case print out until the fatal php error is reached and php stops

No fatal error printed out though

even with VM debug on the actual error that stops the script doesn't print.. the others (e.g. if I have error reporting max)  - so notices and warnings - print but then white screens at the fatal with no print out.
Yes - the fatal is in the log  - but doesn't appear on screen no matter what setting..