[TheLastSuperman]

Originally Posted by GaryT

I'm not going to reply in the manner I want to. To be short I now know I have the option of excepting the error messages (which by the way I think is a very poor standard to set) or I can revert to WP like I used up until 2008 when I purchased (and was happy with) vb before it lowered it's standards.

Admin, moderator, or whoever, please remove my account.

Oye... Gary trust me, you're just reading into this too much . Let me try to explain...

Wordpress has code within it to hide certain errors as well, if it does not hinder functionality then why "freak out" the end-user with a warning message? So you see the reason why in ANY software (like Paul mentioned above this was present in past versions you simply never saw them because they were not told to show in the previous versions) you see errors and warnings is due to the fact not every single server hosting websites is setup identical in fact most run different versions of php/mysql/other software and that is why they decide to often times hide warnings but show errors i.e. warnings are something you should check into, errors something you fix. Long story short it's best to include code to help ease many into things such as knowing a warning/error can occur due to difference in versions and including code to not display them (in-turn freaking out you or your members) but honestly yes, it is the job of the server admin/site owner to know what they are running which is server and software-wise and having it all "jive" properly.

So no worries honestly unless it's an actual error, then like Paul said it's best to actually fix it instead of let's say applying a "band-aid".

Edit: Gary... if it eases your mind why not simply go back to 4.2.1? I know you ran a full backup before upgrading... if so instead of closing the site simply restore it to 4.2.1 but like I tried to explain above unless it's an error message and only a warning then don't fret so much, simply include code to hide the warnings and go on about your business .

Originally Posted by Digital Jedi

Well, consider that you can't fix something that isn't actually broken. Like I said, a warning and an error are different. Some of these warnings are saying "hey, we might someday stop using this function in a future version of PHP sometime down the road. But it fundamentally still works." With that said, PHP errors are notoriously uninformative and even misleading at times. This is a issue with PHP, not vBulletin.



They usually don't do that. But like I said, take some time off. We'll still be here if you decided to come back.

We do not delete accounts, we will rename and obfuscate them best we can though .