Update to 4.2.2 blew up my board.

[weave]

If you did the mods to class_core.php - lines 5683-5685 like this:

case E_NOTICE:
case E_STRICT:
case E_DEPRECATED:
// Just ignore these completely
// break;

Some people have had success with adding in "case E_WARNING:"

So your code would be:

case E_NOTICE:
case E_STRICT:
case E_DEPRECATED:
case E_WARNING:
// Just ignore these completely
// break;

I did not have to add "case E_WARNING:" to my forum and I am fully up and functional 4.2.2 with no known issues reported. This upgrade for sure SUCKS and I feel for all of you who have not been able to get past it.

For additional info I am on:

vBulletin 4.2.2
MySQL 5.5.30
PHP Version 5.3.27

For those wondering what these things are "doing"....

E_NOTICE -- "Run-time notices. Indicate that the script encountered something that could indicate an error, but could also happen in the normal course of running a script."

E_STRICT -- "Enable to have PHP suggest changes to your code which will ensure the best interoperability and forward compatibility of your code. "

E_DEPRECATED -- "User-generated warning message. This is like an E_DEPRECATED, except it is generated in PHP code by using the PHP function trigger_error()."

E_WARNING -- "Run-time warnings (non-fatal errors). Execution of the script is not halted."

[Digital Jedi]

Originally Posted by eboggs_jkvl

Well, sir, my grain of salt was a site down with no clue why. I've done every update faithfully upon it's release and have not had any issues other than 1 previous problem of "uploading attachments" which proved to be some setting that the ISP needed to make. I accepted that issue as it took a few hours and they located the problem easily through error messages. HOWEVER, the site was functioning perfectly and the one problem they were chasing could "wait" and a later fix was acceptable.

This time, my site was giving a full screen of scrolling warnings and then the forum displayed. The error messages were not coming ICW the upload problem and the ISP was spinning their wheels trying to figure out the issue. Without answers or clues, I saw no reason to stay on 4.2.2 and weather the storm hoping for a cure. Yes, being limited on my coder knowledge, I un-updated back to 4.2.1 as that one worked and currently IS working.

I lost a program called VB Garage Pro and the forum I run is Jaxvette.com. Missing the car information from a car site is not an option. Was it vBulletin's fault? Probably not as it was an added program so I'll try and deal with that issue with the other vendor. That was my "modification" conflict and was trouble shot quickly so that really wasn't the issue as that didn't hamper my board's function. I'm still working with that vendor.

So, in conclusion, the forum once again lost the ability to upload attachments. Why? I still haven't gotten an answer for that. It may be on here by now but I haven't scoured the site today to dig out the answer. My patience was a full day of "try this" to see if it fixes it. Well we got the warnings cleared but the upload and garage were still messed up and no prospects of them ever getting corrected.

I'm not mad about this, I'm disappointed. I now have to read the forum and google the world on every update to see what issues are presented. Then, and only then, I can do the update with all of the OMGs on file so I can keep my site up.

True, I'm not a coder, but I am an end user. Without end users, companies fail in a Capitalistic society.

Elmer Boggs


Edit

Nope, no clue yet as to why the upload attachments is failing on 4.2.2. Bear in mind that I'm not the one person in the whole world with this issue. The last time I think it was a "Post bit" issue but nothing so far on the current issue.

My coding knowledge is limited, as well. I have no education in the field. Almost everything I know is directly related to my time spent using this software, and on this board specifically. As such, I would never tell anyone not to upgrade, just because I couldn't get something to work. And certainly, not because the solution wasn't sorted out in a day. Boards are work. Boards are complex. Sometimes your lack of knowledge on something means you won't sort a problem out today, this month, this year. It's the nature of the beast. My post said to take complaints with a grain of salt, because a person's decision to upgrade should be based on the all available information. I don't think people, especially people who are in the midst of a problem, should be telling anyone with vehemence not to upgrade. That's why comment said what it said, and what I was specifically addressing.

[AndrewSimm]

If you have errors after the upgrade start disabling plugins one by one until the errors go away. Also upgrade to php 5.4.20 if possible.

[weave]

Originally Posted by AndrewSimm

If you have errors after the upgrade start disabling plugins one by one until the errors go away. Also upgrade to php 5.4.20 if possible.

My test board is PHP Version 5.4.19 and has all the same issues I saw in the hosted 5.3 server. I will kick it up to .20 and see if that just "fixes" it all

[ForceHSS]

Originally Posted by Peafor

I think I might have to try this.

I also did the upgrade and got errors, thankfully I took back ups of database and forum folder. However, silly me, I reverted to the 4.2.0 patch 3 forum folder but did not replace the database to the saved version.

Now I have a 4.2.2 database with 4.2.0 patch 3 forum.

My only option is to try ForceHSS suggestion above or revert to the last saved 'old' version of my database/forum, which was yesterday morning, but I will lose members and posts that have happened in the mean time.

Can I just ask ForceHSS - when you say 'pick the left side option' what does this mean?

I appreciate this thread, don't feel so alone now.

Install the version you had before the updating of 4.2.2 when you run the upgrade.php you will see a option before you click the upgrade if you dont understand I can post a screenshot

[meaters]

Originally Posted by weave

My test board is PHP Version 5.4.19 and has all the same issues I saw in the hosted 5.3 server. I will kick it up to .20 and see if that just "fixes" it all

Awesome, that will help a lot as I am also on PHP 5.4.20

Good luck man please post how it goes.

[eboggs_jkvl]

Ok, after much tension and nerves stress, the board is up and running with all functionality.

I really appreciate the help on this and hopefully won't have the smoking software the next update that comes down.

The "fix" was to

edit class_core.php

and add lines 5683-5686
case E_NOTICE:
case E_STRICT:
case E_DEPRECATED:
case E_WARNING:

Thanks again to all for helping this 70 year old geezer through this.

Elmer

[meaters]

Awesome!

I've fixed some of the errors too but one remains in album.php

Can you help?

[ForceHSS]

Originally Posted by eboggs_jkvl

Ok, after much tension and nerves stress, the board is up and running with all functionality.

I really appreciate the help on this and hopefully won't have the smoking software the next update that comes down.

The "fix" was to

edit class_core.php

and add lines 5683-5686
case E_NOTICE:
case E_STRICT:
case E_DEPRECATED:
case E_WARNING:


Thanks again to all for helping this 70 year old geezer through this.

Elmer

Your welcome

[Paul M]

Im curious why people resort to editing files before trying the options already provided.

http://www.vbulletin.com/forum/forum...66#post4000466

1. Use the option provided in 4.2.2 to suppress these messages if you have products or hooks in use that still generate errors.

Goto : Settings > Options > Plugin/Hook System and then set the "PHP Compatability" setting to 'Yes'.

This will change the error reporting options within vBulletin on the first hook that is run.

If you have vBulletin Suite (i.e. Blogs / CMS) this setting will pretty much disable all the new Strict & Deprecated messages anywhere.
If you have vBulletin Forum only, and have the Panjo enabled, this setting will also pretty much disable all the new Strict & Deprecated messages anywhere.

I havent seen anyone mention they tried this option first.