After following instructions for the version upgrade, including running update.php and getting “Congratulations, you have successfully upgraded to 1.6.3” I log back into the control panel and it still shows 1.6.2 Build 20080206.

A previous ticket for this client indicated Derek thought there had been improper upgrades along the way. Is there any way to unearth the version history, so that I can follow the individual upgrade steps? Doing a full upgrade from one point release to another doesn’t overwrite everything necessary?

I had that happen on an install last week. I updated 4 sites, three went great, and one of them did something like what you’re experiencing and got it working with some help from this thread.

http://expressionengine.com/forums/viewthread/77245/

Hummmm. That thread sounded hopeful, but upon inspection, config.php still shows

For the record, I’m not part of our tech support team, they’re much smarter about this stuff than I am, just hoping to get you closer to a solution while I’m around today.

So you tried this; including the logging in and out part in step 3?

1). Download config.php, verify that it says $conf[’app_version’] = “163”;

2). Change app version back to “162” like so: $conf[’app_version’] = “162”;

3). Upload the edited config.php file, log in to control panel, log back out.

4). Change app version to the correct version “163” and upload changed config.php

5). Log in to control panel, control panel now shows correct version.

The reason I ask is that I had overlooked that part the first time; I hadn’t logged out and back in.

Also you’ve covered the basics like clearing your cache and stuff by now right?

Site › Admin › Utilities › Clear Cached Data

And you’ve doubled checked your file permissions, especially on the config and system cache right?

I once had an FTP program tell me I had updated those file permissions, but when I logged out with the FTP, and back into the account again, they hadn’t been. So these days I’ll log out and back in with my FTP to double check that stuff to when I’m having issues.

I’m headed out for a couple of hours and will try and check back here from a computer where I’m going if possible.

No, I failed at step 1.

it does not say =’163’ instead it says =’162’

<edit>
Oh, and thanks for any thoughts on this and for minding the store…

Hm. . .  your file permissions are good though? You’re system/config.php file was at 666 when you ran the upgrade script?

Also, what version were you upgrading from 1.6.2?

I’m asking this because I’m wondering if its just that the file wasn’t writable during the upgrade. You know, like maybe all your files are good, but the config file just couldn’t be updated on the server.

yep, config.php was set at 666.

i’m not sure what the upgrade path over time has been; this is a gig i’ve taken over at this juncture…

do you suppose trying to run update.php again will do any harm?

I can’t think of anything it would harm.

Might be time for me to step aside and bring in one of the tech staff here though. They see a lot more of this stuff than I do.

Hm- 1.6.2->1.6.3 doesn’t do much.  Running the update again shouldn’t hurt anything in this particular case.  Looks like all it does is add the cookie_prefix to the config file- if I’m reading things correctly.  If that doesn’t do it, I’d just manually change the version number to 163.  That should be fine for this update- but I’d prefer to get a successful run on the update script- more for the future than for this particular instance.  If it doesn’t write to the config on a more significant update, it could be more pesky.

I did the config.php tweak and it’s now showing the correct point release, but still using an out-of-date CP theme.

I’m concerned that a previous update was ferkakte, and I still need to upgrade the Forum module.

Not sure how far to rollback. Apparently, the initial install was downloaded in June 2005 (is that still EE, or PM at that point?) and some intervening upgrades, but no paper trail.  :(

June 2005 is still EE, of course. The CP date theme stems from the core files, actually, so you might want to try reuploading those. No need to rerun update.php, just replace the files with the most recent version.

Wow. 6/05 seems like ancient history from here. Go figure.

So the update script does not overwrite the /core folder?

Define ancient EE 1.0 came out in April 2004. In the summer of 2005 we held at 1.3. The update script never touches anything besides the database, by the way. That’s why you need to upload the new files all by yourself every time.

<lightbulb>

ummmmmm.

finally got a window to take the site down and update.

copied over the /core and /cp folder contents, but now my control panel will not load at all.

honest, i thought i was beginning to understand this stuff.

uggg.

<edit> went through reinstall and have the site back online, but only get a blank page when trying to access the control panel.

<edit, edit> was an error with the cp index.php

this thread was helpful if you read through and reverse everywhere he says “the control panel is working, but nothing else” ;o)

Am I to understand you’re fine now? You should probably replace all files at a go, not just core and cp. The modules folder, in particular, is particularly important.

Yes and no. The update has now gone through, but to Derek’s point in the earlier thread, do I now need to step backward and deal with all the point releases that may have been missed?

No. Running update.php sucessfully means you have upgraded to the latest version.