Hi, On Tue, Jul 1, 2014 at 5:28 PM, Dhananjay Nakrani < dhananjaynakrani@gmail.com> wrote:

Hi,

On Tue, Jul 1, 2014 at 1:34 PM, Michal Čihař <michal@cihar.com> wrote:

...

Hi

Dne Sun, 29 Jun 2014 07:49:26 -0400 Marc Delisle <marc@infomarc.info> napsal(a):

...

Since the new error reporting at the PHP level, errors that were "hidden" using the at sign (for example, @fopen) are now displayed, with the possibility of sending a report.

This is IMHO bug in the error collecting code, Dhananjay can you please look at it?

Sure. I will try to solve it this week only.

...

...

Do we now have to handle the situation differently (with try/catch) to avoid this error reporting? In the case I mention, there is no need to show the error report, as the situation is already handled by checking what fopen() returns.

I think using @ should be good enough (though catching the exceptions is probably cleaner approach).

-- Michal Čihař | http://cihar.com | http://phpmyadmin.net

I've solved that issue by adding an extra check in custom error handler. Please review Pull#1278. Thanks, Dhananjay Nakrani.