I've never subscribed to the notion of masking errors. It's a very bad and downright sloppy approach to software problems. Anyone on my payroll doing that would be fired immediately

Some errors have nothing to do with vBulletin, and some errors are just out of your control. I'm not saying that you should skip all errors with every website you create or build, but with vBulletin sometimes its a good idea in some cases.

I did it with my vBulletin, and it has been working perfectly fine for the past 2 years.

This is why you should use:
This turns off the extra error reporting in php 5.3 & 5.4 (for strict & deprecated warnings), but will allow other important errors to show.

This is what fixed it. It fixed all the errors I was having, I wasn't looking for a different way anyone because it was fixed.

That didn't fix any errors at all. All you did was hide the error messages. It's like piling snow on top of a garbage heap and saying "Hey, I just cleaned up the garbage!"

To be fair, we're not talking errors here. We're talking deprecated warnings, translating to: It is perfectly okay to use this functionality as you do at present time, but be warned: things may change in one of the future versions of php.

The line in the config is no longer needed in 4.2.3 so looks like vb has fixed it in this version

The policy on warning suppression (which was changed for 4.2.2) has been reverted for 4.2.3. In effect, that line you had to add in 4.2.2 is now already included.

If the warnings can't be fixed, hide them. It makes the board look better.

When you don't have the skills or you're just too damn lazy then cover up the problems and don't address them. The customer will never know the difference!!! What a company!!