Another 4.2.2 upgrade test

[CarlitoBrigante]

Paul, there is no reason to be so dismissive. I have a problem on many servers with display_errors set to off and errors still being shown by vBulletin 4.2.2 through its new error handler. Why this is happening, I did not have time to look into, as I have so many forums to upgrade I do not have time to submit a bug report. I am not paid to look into vBulletin's core code, but I might take some time to do so.

For the others: those warnings, as I said in my previous post, should not be ignored. The reality is that many plugins you could have downloaded also from vBulletin.org will cause those warnings in many vBulletin installations - just, up to this moment, you might have not noticed them. This is because many plugins are using old code or are coded following old PHP standards.

When you set display_errors to off, you should always have log_errors set to on and check routinely for errors popping up there, including warnings, and fix plugins when possible.

On production websites, you should basically NEVER show this kind of error information to the public, as it might expose vulnerabilities or other information about your server you do not want to disclose (like path structure).

Sorry for the fast post, I did not have time to re-read it for spelling errors as I have still 4 forums piled up for an upgrade today.