Schema upgrade doesn't happen with 4.261

By Bruce J.A. Nourish on Jun 30, 2009 at 1:38 PM 4 Vote 0 Votes

Hi,

I've installed MovableType 4.261, and I'm trying to upgrade from 4.26 using the instructions on the following page: http://www.movabletype.org/documentation/upgrade/

The problem I'm having is that when I try to log in, I am told I need to upgrade. Once I go through the upgrade process, I can log in. But then if I close the browser and come back, I have to go through the upgrade process again. Inspecting dumps of the database indicates that the schema and contents are unchanged.

I've also tried using a 4.25 database dump, but the same problem occurs.

Can anyone shed any light on this?

Thanks,
Bruce

Reported on Movable Type 4.2

4 Replies

| Add a Reply

Mike T | July 2, 2009 10:27 AM | Reply

What product version and schema version do you see in MT.pm under lib?
Bruce J.A. Nourish | July 7, 2009 2:42 PM | Reply

Hi Mike,

( $VERSION, $SCHEMA_VERSION ) = ( '4.261', '4.0071' );
( $PRODUCT_NAME, $PRODUCT_CODE, $PRODUCT_VERSION, $VERSION_ID ) = (
'Movable Type', 'MT',
'4.261', '4.261'
);

Bruce
Mike T | July 10, 2009 5:32 AM | Reply

Check mt_config and see if it says MTVersion 4.261

If it does, then you can set that to 4.26 and see if that tricks it into running the update. (Back up your database first)
Bruce J.A. Nourish | July 16, 2009 12:42 PM | Reply

Hi Mike,

If I change the mt_config in the database to have 4.26 instead of 4.261, I get basically the same behavior, except the entries in the log say "Movable Type has been upgraded to version 4.26."

Bruce