Closing my site

[K4GAP]

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.

[Digital Jedi]

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.

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.

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

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.

[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 .

[DivisionByZero]

Most of those non-fatal warnings are simply housekeeping stuff. Cross your T's and dot your I's. It's nothing more than a what a nagging school teacher would do to get you to conform to standards.

[Paul M]

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.

I really cant tell if you are ignoring what people are telling you, or just acting up. Most php software has suppressed warnings & notices in it, especially if its older software. vBulletin 3 - the one you were "happy" with in 2008 - generates lots of them, it simply doesnt display them. Try taking all the error supression out of WP and see what happens. No standards have been lowered.

[K4GAP]

Originally Posted by Paul M

**I really cant tell if you are ignoring what people are telling you, or just acting up.**

No Sir I'm not ignoring or minimizing anyone's comments in this thread. Doing that would be a sign of a flawed character.

I've tried every fix posted by anyone I have learned to trust while I've been here. The best thing for me to do is take Supermans advice and downgrade to 4.2.1 and, take someone else's advice to take a break from it all.

[billstelling]

both of the issues related to 4.2.2 with the timezone and errors code is due to the changes in php and are related to vb only in that it causes it to trip the errors. Nothing is really wrong with vb, it just has not caught up with the most recent changes to server php..

Adding
this code

date_default_timezone_set ('America/New_York');
define('SKIP_ALL_ERRORS', true);

is just the easiest way to fix it for now. It's more of a version mismatch problem than a core vB problem.

PHP time zone helper

[final kaoss]

I would agree with bills suggestion, 4.2.2 fixed several security issues. Since it's already upgraded I would just apply the quick fix provided & then just carry on as usual.

Hell either way you choose, you get the same result = no error messages displayed.

[justicechick]

Took me about a month gary with 4.2.2 to finally work through the error codes(did what BOP said) and everyday it seemed we were globally turning off hooks/plugins and work our way through them one bay one to find the one causing the headache. I don't think I will ever upgrade again. LOL

--------------- Added [DATE]1387251383[/DATE] at [TIME]1387251383[/TIME] ---------------

Took me about a month gary with 4.2.2 to finally work through the error codes(did what BOP said) and everyday it seemed we were globally turning off hooks/plugins and work our way through them one bay one to find the one causing the headache. I don't think I will ever upgrade again. LOL

[RichieBoy67]

This is the nature of all website script. Mods get out dated, Php gets updated, everything changes.

These warnings are supposed to be a tool for us to use to repair old plug ins, etc. I have used and worked with Joomla, Drupal, and Wordpress for years and have had issues with each at one time or another. Code gets depreciated, etc. It is just part of the business.

Gary, you could probably get rid of those warnings in about 5 minutes. I think you will regret closing your site over some simple warnings. Either way best of luck.

Rich