The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#13
|
||||
|
||||
![]() Quote:
![]() 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 ![]() Quote:
![]() |
3 благодарности(ей) от: | ||
puertoblack2003, RichieBoy67, tbworld |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|