Closing my site
 

Not that anyone will miss it but, I'm frustrated with 4.2.2. I am finding error messages that I've not seen discussed here in vb's forums. And I'm not going to be and get a headache over those error's. If I do cool down and decide to open my site again, It won't be using 4.2.2. That's for darn sure.

I'm also frustrated having a wonderful style with so many code fault's that I have no support for. The code faults are not as much faults as they are to custom and will not allow most mods. Miner sold me the skin then would not answer support requests then, he closed his site.

And then there's the matter of all the bickering going on in these forums. It is SO obvious to me that there are some new members (not all) that are here for anything but good reasons.

Merry Christmas

That's sad news to hear Gary. If you want, you could post at my site, and I can see about helping you resolve any issues you may be having.

That don't mean that I can wave a magic wand, and make it all better, but I sure can give it a go.

If you know some members like to bicker here, best thing to do is not read anything they post, save yourself the headaches.

On their profile there's a link for blocking them. Don't know how effective that is here since never used, but it's a consideration.

The warnings introduced in 4.2.2 will go away again by adding the line
To your config.php file... just below <?php

Just make sure you have a more recent download of 4.2.2, the build available for the first couple weeks didn't have this option.

I added what BOP said to my PHP file a while back. Works great for me. Although I would suspect that Gary is not trying to hide them - but wants them fixed entirely.

I'm not in the same league as you guys, but I do try to pay attention, and learn from what you guys say and do on this forum.

I like reading your guys posts, and it saddens me when yet another respected member is about to disappear.

There are a few of us here who do read what you guys post, and try to learn from your knowledge without being a pain in the a$$.

They are just warnings. While fixing them is ideal, they dont make any difference to functionality.

What you need to remember is they are equally present in all older versions as well, the only difference is that by default, 4.2.2 displays the warning, older versions did not - you can turn the warnings off again using the config option mentioned above.

May I ask, how is it that this is acceptable by so many? PLEASE! Be totally honest with me, I'm a big boy I can take it. Am I putting to much into this? Or has it become kosher to just accept that this is the way we (licensed vb users) are to deal with such matters from now on?

Someone needs to set me straight on this. Are there any efforts to fix these errors other than to just hide them?

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

I served in the Military from 1971 - 1998. I retired with many honors. I was the 1st Sgt before retiring for 19 months. I HAVE VERY thick skin. Bickering is something that did not happen within earshot of me, or there was hell to pay. I will admit it yanks my chain to see, hear, or read of such a personality disorder. (yes, my wife get's by with it). I'm trying to be a good civilian but it's hard.

With limited resources to me it is more important time is spent to allow the product to work on PHP 5.4 and fix real bugs than to clear up warnings easily hidden that no one previously noticed or cared about. Yes, in an ideal world you could do it all, but the world is rarely ideal.

Because they are just warnings!

They dont mean anything other than to warn you about something. For example, deprecated warnings simply tell you that a function may be removed from php at some point in the future. The function still works exactly as its always done.

In PHP, warnings are basically just informational messages, which have no effect on functionality.

In other words, errors and warnings are two different things. A warning means to look out for something or to be aware of something that may or may not matter. An error means something is immediately wrong. A sign can warn you to expect a traffic light around the corner, but when you get there, it's green.

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.

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.

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 ;).

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

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.

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.

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.

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

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.

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

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