Thread

Hi,
I just ran the 1.6.3 update on my 1.6.2 installation. update.php says the update was successful, but when I log back in it still says 1.6.2 in the top left corner. If I rerun update.php it also says that I’m still using 1.6.2. Any ideas how to track the error down?

eexperience, was your config.php file writeable when you ran the update?

It might not have been.

You can edit the config.php file manually to have:

$conf['app_version'] = "163";

Does that make sense?

Hi Sue,
I had that suspicion too. But my config.php and config.php.bak were already set at 666.

I can edit the config.php, but how can I be sure that the update was successful?

Thanks,
Timon

Well, there are no database changes with the install.

The file core.system.php was changed to have:

define('APP_BUILD'    ,    '20080319');

That’s one method to make sure at least that file was updated.

In addition to the change Sue is suggesting for the config.php file, you will want to add:

$conf['cookie_prefix'] = "";

And I would then verify that 666 are the correct permissions on your host for PHP to be able to write to the file, by going to your General Configuration and changing the “URL to Documentation Directory” preference, making sure that it “sticks” when you change it.

If you find that value above in your config.php file already, and its version was already correct, then the update went okay, the file was written to properly, but a PHP caching mechanism is probably still holding the old information.  I’ve seen that occur on MAMP environments, for instance.

Hi Sue,
now it gets interesting. I’ve checked the config.php after the update and it already had $conf[‘app_version’] = “163”; in it. The core.system.php has the exact line you told me. So both files have the correct settings.

I’ve cleared all EE caches and my local browser cache and logged out of EE. Still it says version 1.6.2 in the top left corner and in the site stats when you log in.

Yep, that sounds like a PHP cache.  Introduce a syntax error into it manually, and save it remotely:

echo "break " me!";

Access your site, you should get the error (or a blank screen depending on your error reporting settings), then remove the malformed code to put your config.php back to normal.  That should force the server’s caching mechanism to read and cache the new file.

Hi Derek,
your suggested line of code was already in there. Changes to the configuration stick also and are reflected in the config.php.

I’ve restarted my Apache server but no luck. I’m using Ubuntu 6.06 on my server and PHP 5.1.2 with eAccelerator v0.9.5.1.

Hi Derek,
thanks for your help. The last bit solved the problem.

Thanks for your quick support. I appreciate it.

Timon

Yeah, eAccelerator is what MAMP uses - it’s a curious mechanism, and I’m never sure why it doesn’t detect that the file has changed until you manually edit it.  Glad you’re up and running!