Thread

Thanks Robin, I gave it a go- after I get to an error that can’t be bypassed by hitting the “back” link (which takes me to the license screen) I checked out the config file- version #214, which matches the version from the start of the wizard… I tried your error instructions, I also tried modifying the version # in the config (blank, 215) no luck… I’m not pressed to figure this out before the holiday and in fact won’t have access to the files and db until next week so not much point to diving in much further today. This is a site that I had tried to update previously- maybe I’ll try my hand at one that hasn’t been touched at all, see if it’s possibly something that got caught in the DB during the previous update attempts (though I’m relatively certain I dropped all the tables in between attempts…)

Thanks-

EDIT
I ran an update on another website on this server- it went flawlessly. Worth noting it was an update from 2.2.1 -> 2.3.1, the others were from 2.1.3 -> 2.3.1, and they seem to get stuck between 2.1.4 and 2.1.5

Let’s see- 2.1.5 does do a lot- mostly adding tables for the new file handling.  But it’s not particularly unusual stuff and it’s not a heavy hit going through updating each table row or anything.

I can push through another update, see if I can spot why it fails?  And fix it regardless?  Really thought the cache issue would be it, but I’m pretty sure you’d have spotted it if that were the case.

Hi Robin, thanks- that’d be great- I’ve sent you creds via email…

Sorry for the delay, Adam.  I just finished pushing it through- it didn’t seem to run into the cache problem at all.  Only issue was with some tables existing (and in a more complete form) than the update would have expected.  All file related tables, and I would have thought they were created during the failed update to 2.1.5, except I hit one in the 2.0 update (trying to create a caption field in exp_files when one already existed).  None were related to running a particular update twice (you can sometimes tell), so it’s just puzzling.

Anyway- you’re now on 2.3.1.  The backend worked fine in a quick surf and the frontend now looks good.  I was getting an error with it looking for the ft.cki_mblist.php file, which I couldn’t find to save my life (though I suspect vz_members may be the same thing???) so I grabbed a fresh copy since it’s free, put it up, and the frontend was also good in a quick surf around.

I’m sorry these updates are being so weird for you.  It was definitely a different issue than the server cache one.  But give the site a good look through.  If you do spot anything off, I’ll go back in and take a look.  DB integretity should be fine, though.  Oh- and be sure to update any third party add-ons that may be out of date.

Let me know what you find- Robin

Thanks Robin, all appears to be well. I found a couple issues with CKI Member List but it had to do with my member group settings within the field type. This particular installation started in 1.x, and suffered several failed attempts to upgrade from 2.1.x to 2.3.1 so I’m not surprised it was this troublesome- I appreciate the help. I have a few more to work through on this server, so far though I’m not having the same troubles since turning off the cache function. Wanna mark this closed? It’s wandering…

Thanks!

Glad the only issues are looking minor!  And thanks for confirmation others seem to be going ok w/the cache off.  It’s sounding like the main issue should be resolved (x-fingers) so I’ll wrap this one up.  But if you do have any others that prove to be tricky, just let us know.