Site crashed after update to 5.2.14

[scotserve]

Updated to 5.2.14

Cant access site or admin area

 

Catchable fatal error: Argument 1 passed to WHMCS_TokenManager::init() must be an instance of WHMCS_Init, instance of WHMCSCore given, called in /home/scotserv/public_html/includes/functions.php on line 0 and defined in /home/scotserv/public_html/includes/classes/class.TokenManager.php on line 0

 

Have submitted support ticket but asking here in case anyone has a clue

 

I have to admit I am finding these updates and subsequent sorts a tad tedious

[brian!]

if this was just an incremental patch, i'd be tempted to re-upload... possibly the files got corrupted during the original upload.

[WHMCS TedX]

This happens when you accidentally apply the 5.1 update to a 5.2 installation. To fix it, you'll have to do the full upgrade.

[scotserve]

This happens when you accidentally apply the 5.1 update to a 5.2 installation. To fix it, you'll have to do the full upgrade.

 

Bollox, thats what I have done

Note to self must try and stop working 24hr days

[scotserve]

Ted

Many thanks - quick Idera restore back to 5.2.13 and then apply patch - all fixed and feeling quite sheepish about making a schoolboy error

[R-n-R]

(I too opened a support ticket some 7 hours ago but nothing yet)

 

Crud, this same thing happened to me, my first impression was it was a corrupt file.

 

Here is what I did, I upgraded from 5.2.12 --> 5.2.13 without issue. Logged in to my Admin area and it was showing 5.2.14 was available and I was on 5.2.13

 

Now I uploaded the patch from 5.2.13 --> 5.2.14 and after the upload all pages went blank and then I activated the error message and it is identical to scotserve 's error.

 

Because I thought it was file corruption of the 5.2.14 patch file, I deleted it off my PC, and went back to look and sure enough its still in my Recycle Bin on my PC and sure enough its was for 5.1.13 to 5.1.14! URGH! I thought I was careful too!

 

Problem is I downloaded the REAL 5.2.14 patch and uploaded and still same issue. Since I wrote over the other files I wonder if I can revert back to 5.2.13 just by loading the patch for 5.2.12 --> 5.2.13

I will wait a little while and get some advice from you guys as what I should do now.

 

Thanks in advance

 

~ Roy

[R-n-R]

Ted

Many thanks - quick Idera restore back to 5.2.13 and then apply patch - all fixed and feeling quite sheepish about making a schoolboy error

 

scotserve, my friend, I owe you a beer or beverage of your choice. I decided to do as you did and all is working now!

 

For those that might have done the same stunt, I too upgraded the 5.1 when it should of been the 5.2.14

 

But loading my 5.2.13 backup to the server and then once complete I loaded the 5.2.14 (the CORRECT ONE THIS TIME) all was good I am back in business!

[dutchnet]

Tried that did not work

[ski]

I just performed the update whmcs_v5213_incremental_to_v5214_patch (still sitting in my chrome download bar) and got the blank page. I turned on error reporting and received the same error as you guys. I have never had any issues before doing updates, and am a little apprehensive about doing anything else until I have a better understanding of whats going on.

 

I realize all the data is still in the database... worst case scenario, what would I have to do to get the site back? Is it really just as easy as installing the full 5.2.14?

 

Thanks in advance guys.