vb.org Archive - Update to 4.2.2 blew up my board.

Page 3 of 3

Show 40 post(s) from this thread on one page

vb.org Archive (https://vborg.vbsupport.ru/index.php)

- vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)

- - Update to 4.2.2 blew up my board. (https://vborg.vbsupport.ru/showthread.php?t=303172)

weave

10-11-2013 04:33 PM

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

Code:

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:

Code:

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

10-11-2013 04:41 PM

Quote:

Originally Posted by eboggs_jkvl (Post 2452206)

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

10-11-2013 05:00 PM

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

10-11-2013 05:11 PM

Quote:

Originally Posted by AndrewSimm (Post 2452265)

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

10-11-2013 06:16 PM

Quote:

Originally Posted by Peafor (Post 2452226)

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

10-11-2013 06:36 PM

Quote:

Originally Posted by weave (Post 2452268)

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

10-11-2013 11:37 PM

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

10-12-2013 12:03 AM

Awesome!

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

Can you help?

http://store.img-share.eu/r_pngX0uvahE.png

ForceHSS

10-12-2013 12:45 AM

Quote:

Originally Posted by eboggs_jkvl (Post 2452420)

Your welcome

Paul M

10-12-2013 01:35 AM

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

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

Quote:

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.

Paul M

10-12-2013 01:37 AM

Quote:

Originally Posted by meaters (Post 2452090)

I hope Paul M reads this, he's been away all day.

I do have a life outside of forums, aside from the fact I work during the day. :p

AusPhotography

10-12-2013 02:47 AM

for those with issues...
1. The 4.2.2 upgrade is very solid! (i.e. a vanilla vB site wont have problems)
2. All the issues we have had are due to add-ons (in test)
3. I'm waiting for DBtech and a few others to remediate their products
4. You have the option of suppressing the errors, but that has side effects (i.e. you miss errors that really need to be dealt with)

Peafor

10-12-2013 08:54 AM

Quote:

Originally Posted by Paul M (Post 2452480)

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

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

I havent seen anyone mention they tried this option first.

I wanted to try it but all the errors had locked me out of the admin panel, I couldn't get in to turn them off. :(

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

Quote:

Originally Posted by ForceHSS (Post 2452276)

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

Thanks for taking the time to reply. I couldn't get that far, it kept saying the install folder was not there, when it was.

I've given up now and reverted to the last safe version I had, lost two days of posts but our members are great and we will get over it. It was not worth any more stress or loss of sleep.

One thing I can't understand is that I have two forums, identical in every way except content. What I do to one I do the the other. They are on the same server. I upgraded one without a problem, that is why I assumed the 2nd would be just as easy, it wasn't and produced all these errors. :huh:

Hey ho, life is too short for stressing. :)

Thanks for your help though, appreciated.

Good luck with everyone in getting your sites sorted.

eboggs_jkvl

10-12-2013 11:35 AM

Quote:

Originally Posted by Paul M (Post 2452480)

Option 2 is what fixed the "Upload attachment" problem.

Elmer

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

Um... one tiny little question for the coders on here.

Since I edited the class_core.php, what happens when I update to 4.2.3? Will I lose that edit and need to re-edit the file and add the lines again?

Elmer

Digital Jedi

10-12-2013 12:48 PM

Quote:

Originally Posted by eboggs_jkvl (Post 2452561)

I would imagine a new version would account for it. Or if class_core hasn't had any changes between versions, you could just use it.

justicechick

10-12-2013 02:40 PM

Quote:

Originally Posted by Paul M (Post 2452480)

I tried it...didnt work. I've seen some say they went back to 4.2.1, yet Ive also read that once you upgrade you cant revert ????? :confused:

As someone that is new to all of this I would much rather not have to be doing walk arounds and rigging to get things to work that typically should never cross my mind. However, Ive been at it since the upgrade started throwing off the time zone error right on up until now, I fix one things and find another. :)

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

Quote:

Originally Posted by Digital Jedi (Post 2452589)

I would imagine a new version would account for it. Or if class_core hasn't had any changes between versions, you could just use it.

Im wondering the same thing. I was dealing with a qwa.qwa@qa that kept putting themselves into the usergroup admin, regardless how many times we banned them. So I was looking for a solutions to keep them out or else I would have stayed with my 4.2.1... To bad I found out to late that I needed to delete the entire install directory, not just the install/install.php! LOL I traded one problem for what seems like a entire apple cart full of them. Thankfully there are some smart ppl here that always seem to have the answer for anyone who can follow a few directions. :up:

Paul M

10-12-2013 05:23 PM

Quote:

Originally Posted by Peafor (Post 2452536)

I wanted to try it but all the errors had locked me out of the admin panel, I couldn't get in to turn them off. :(

Then you would need to disable hooks via the config file, then login and turn the option on. You could then re-enabled hooks.

Paul M

10-12-2013 05:28 PM

Quote:

Originally Posted by justicechick (Post 2452636)

I tried it...didnt work. I've seen some say they went back to 4.2.1, yet Ive also read that once you upgrade you cant revert ????? :confused:

Please be more than specific than "didnt work". Id like to know under what circumstancs it would not work.

As for reverting, there are no database changes from 4.2.1 to 4.2.2, so you could quite easily re-upload 4.2.1 and it would work.
I would suggest if you did this that you turn debug mode on and reset the version back to 4.2.1 in Options > Untouchables (then turn debug back off).

justicechick

10-12-2013 10:36 PM

Quote:

Originally Posted by Paul M (Post 2452696)

I try the setting in options > Plugins > PHP Compatability. Turning it on alone didnt solve the error codes I was getting. I did the code edit , I had seen

(2. For those who feel comfortable with editing files.

In class_core.php locate lines 5683-5685 (class_core.php is in the 'includes' folder)
Code:

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

Add lines for Deprecated and/or Strict errors as required ;

Code:

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

This will bypass the additional error reporting. )

And its working fine now. Thanks

All times are GMT. The time now is 06:11 AM.

Page 3 of 3

Show 40 post(s) from this thread on one page

X vBulletin 3.8.12 by vBS Debug Information
Page Generation 0.02287 seconds Memory Usage 1,823KB Queries Executed 10 (?)
More Information
Template Usage: (1)ad_footer_end (1)ad_footer_start (1)ad_header_end (1)ad_header_logo (1)ad_navbar_below (2)bbcode_code_printable (16)bbcode_quote_printable (1)footer (1)gobutton (1)header (1)headinclude (6)option (1)pagenav (1)pagenav_curpage (2)pagenav_pagelink (1)post_thanks_navbar_search (1)printthread (19)printthreadbit (1)spacer_close (1)spacer_open Phrase Groups Available: global postbit showthread	Included Files: ./printthread.php ./global.php ./includes/init.php ./includes/class_core.php ./includes/config.php ./includes/functions.php ./includes/class_hook.php ./includes/modsystem_functions.php ./includes/class_bbcode_alt.php ./includes/class_bbcode.php ./includes/functions_bigthree.php Hooks Called: init_startup init_startup_session_setup_start init_startup_session_setup_complete cache_permissions fetch_threadinfo_query fetch_threadinfo fetch_foruminfo style_fetch cache_templates global_start parse_templates global_setup_complete printthread_start pagenav_page pagenav_complete bbcode_fetch_tags bbcode_create bbcode_parse_start bbcode_parse_complete_precache bbcode_parse_complete printthread_post printthread_complete
Messages: