Comments for Schema upgrade doesn't happen with 4.261

Schema upgrade doesn't happen with 4.261

2009-06-30T20:38:11Z

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

Comment from Mike T on 2009-07-02

2009-07-02T17:27:31Z

What product version and schema version do you see in MT.pm under lib?

Comment from Bruce J.A. Nourish on 2009-07-07

2009-07-07T21:42:22Z

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

Comment from Mike T on 2009-07-10

2009-07-10T12:32:22Z

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)

Comment from Bruce J.A. Nourish on 2009-07-16

2009-07-16T19:42:05Z

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