Update to 4.2.2 blew up my board.

[Paul M]

Originally Posted by meaters

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.

[AusPhotography]

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]

Originally Posted by Paul M

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

Originally Posted by ForceHSS

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]

Originally Posted by Paul M

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.

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]

Originally Posted by eboggs_jkvl

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

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]

Originally Posted by Paul M

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

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

Originally Posted by Digital Jedi

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]

Originally Posted by Peafor

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]

Originally Posted by justicechick

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

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]

Originally Posted by Paul M

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

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