Closing my site

[K4GAP]

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

[ozzy47]

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.

[Max Taxable]

Originally Posted by GaryT

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.

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.

[BirdOPrey5]

The warnings introduced in 4.2.2 will go away again by adding the line

define('SKIP_ALL_ERRORS', true);

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.

[Krusty1231]

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

[Paul M]

Originally Posted by Krusty1231

Although I would suspect that Gary is not trying to hide them - but wants them fixed entirely.

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.

[K4GAP]

Originally Posted by Paul M

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

Originally Posted by ozzy47

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.

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.

[BirdOPrey5]

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.

[Paul M]

Originally Posted by GaryT

May I ask, how is it that this is acceptable by so many?

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.

[Digital Jedi]

Originally Posted by GaryT

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?

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.