![]() |
Starting from a clean slate.
I've deleted anything vb related from my host server and started with a fresh new database.
Now I'm sitting here this morning in a lot better frame of mind than I had a few days ago. Apparently nobody could understand the 4.2.2 dilemma I was having and why the (newly accepted standard) irked me so bad. It's ok, maybe it's a personality trait I inherited from the military. I never expected anything less than perfection. ----------------------------------------------------------------------------------- With that out of the way. I'm looking about vb.org and vb.com for any advantages or disadvantages to either 4.2.0 or 4.2.1 Does anyone have suggestions on which I should use? And the advantages or disadvantages of using either? Thanks' |
There is no reason you should not be using 4.2.2. There was no "newly accepted standard" and 4.2.2 is coded better than any prior version- you simply never knew the warnings existed in 4.2.1, 4.2.0, or any prior version.
4.2.2 with this line added to config.php has less bugs/errors/warnings than any prior 4.x version. Code:
define('SKIP_ALL_ERRORS', true); |
There did seem to be a communication issue with what we were trying to convey the other day. I would have to agree that 4.2.2. is the better option. If you go with 4.2.1 or 0, you're basically going with the lesser standard. Less secure versions that didn't display the warnings properly. You'd definitely be settling for less than perfect with .1 or .0.
|
That's the spirit Gary.
I had a similar scenario with my RC quad build. The programming of the flight controller was giving me fits. I just put in the closet for a week. When I cooled off I got it back out and fixed the problem. Now I enjoy putting her through her paces. Some times it's good to walk away for a minute then come back to the problem. |
Quote:
If you want to be using vB4, then you should be using 4.2.2, simple as that. |
Heck I don't know what all the fuss is about I'm still running 4.1.9 just fine, it's patched and have not had an issue to date.
You should run 4.2.1 OR 4.2.2, if you do not understand how to make the errors not display then go with 4.2.1 however if you can add a snippet of code and/or tick the compatibility option in admincp to make them go poof then run 4.2.2 ;). The newest version is typically (99% of the time) the safest and best to use, are there exceptions to this rule? Well sure why do you think I used 99% i.e. 1% of the time the exception is if an exploit if found in a vB4 yet vB3 is not affected by it, that would be one of the few exceptions. Quote:
/Salute! |
Quote:
Merry Christmas' |
Quote:
Merry Christmas to you too Gary and everyone else as well! |
All times are GMT. The time now is 09:59 AM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|