Thread

I installed the 20090515 build last night, on top of 1.6.4, but instead of seeing ‘1.6.7’ I see 1.6.5 as shown below, but with the correct build number.

ExpressionEngine 1.6.5 - © Copyright 2003 - 2009 - EllisLab, Inc.
Script executed in 2.0337 seconds   5 SQL queries used
Build:  20090515

[Mod Edit: Moved to the Technical Support forum]

When upgrading from 1.6.4, did you run update.php?

Not at first, but I did after I noticed the anomaly described above.  But there was no change.

I didn’t write down the sequence but here’s how I recall installing:

1) Overlaid files as per the build upgrade notes
2) Noted that the version number hadn’t changed (was 1.6.4) - I didn’t look at the build number, unfortunately
3) Did the ‘version’ upgrade, including running update
4) Noted that the version bumped to 1.6.4 and now noted that the build was 20090515

This may not be precise, unfortunately.

I’m assuming that since I’m on the most recent build number everything is OK, and indeed the site seems fine.  I was just curious about the version number anomaly.

Steve, you may be on a server that utilizes an external PHP caching mechanism, that stores files that have not been modified externally.  Try editing your config.php file (anything will do, introduce a syntax error perhaps), accessing EE, then change your config.php file back.  I’m going to guess that when you open it up that it says ‘167’, it’s just registering in the environment has having been changed.

Thanks, Derek, but that didn’t seem to work.  I also restarted the server.

When you edited the file, did it still say ‘164’ for the version?  If so, then you need to make sure that file is writable (typically permissions of 666) before running the update.

Config.php says 165.  Its backup says 164.

But I got everything in sync and here’s how:

I ran update.php again.  It prompted me to go from 165 to 166 which was successful.  It then provided a link to update from 166 to 167 but nothing happened when I clicked on the link.  This reminded me that when I went from 164 to 165 I had something similar happen - a non-responsive link for going from 165 to 166. 

So I cleared caches again, installed a new update.php (probably not needed) and ran it again and now it successfully prompted and converted from 166 to 167.

I’m not sure how much of this was brought on by my not running update at first, because I thought I was just installing a ‘build’ vs version [it’s been a while ;-> ].

Anyway, all seems copacetic now and thanks for the help!!

Steve

Glad to hear it. That said, update.php doesn’t do much besides incrementing the version number for the last few versions, so this shouldn’t be too much of an issue 😊 Please don’t hesitate to post again as needed.