Upgrader not found when upgrading from 1.0 to 1.2.1

Having trouble installing serendipity?
Post Reply
somy
Posts: 3
Joined: Fri Feb 29, 2008 2:50 pm

Upgrader not found when upgrading from 1.0 to 1.2.1

Post by somy »

Hi,

I tried to upgrade from version 1.0 to 1.2.1 and I followed the instruction in FAQ:

1. Backup files and DB
2. Copy and overwrite all files from 1.2.1 to 1.0.
3. Open admin page with admin user name and password, upgrader cannot be found in this page.

The version number in admin pages is 1.2.1, however the index page still displays 1.0. Could someone help? Thanks a lot!

Regards,
Mai Sun
somy
Posts: 3
Joined: Fri Feb 29, 2008 2:50 pm

Post by somy »

I changed the version number in my s9y_config_local.inc.php to 1.0 and I saw the upgrader and went through it, however I received the following error msg when exeuting DB changes:

CREATE INDEX pluginretr_idx ON mai_blog_plugins (placement, sort_order);
/ Duplicate key name 'pluginretr_idx'

create table mai_blog_mediaproperties (
mediaid int(11) not null,
property varchar(128) not null,
property_group varchar(50) not null default '',
property_subgroup varchar(50) not null default '',
value text
) /*!40100 CHARACTER SET utf8 COLLATE utf8_unicode_ci */;
/ Table 'mai_blog_mediaproperties' already exists

CREATE INDEX mediapropid_idx ON mai_blog_mediaproperties (mediaid);
/ Duplicate key name 'mediapropid_idx'

CREATE UNIQUE INDEX media_idx ON mai_blog_mediaproperties (mediaid, property, property_group, property_subgroup);
/ Duplicate key name 'media_idx'

create table mai_blog_options (
name varchar(255) not null,
value text not null,
okey varchar(64) not null default ''
) /*!40100 CHARACTER SET utf8 COLLATE utf8_unicode_ci */;
/ Table 'mai_blog_options' already exists

CREATE INDEX options_idx ON mai_blog_options (okey);
/ Duplicate key name 'options_idx'

ALTER TABLE mai_blog_images ADD COLUMN realname varchar(255) not null default '';
/ Duplicate column name 'realname'

ALTER TABLE mai_blog_references ADD COLUMN type varchar(128) not null default '';
/ Duplicate column name 'type'

CREATE INDEX reftype_idx ON mai_blog_references (type);
/ Duplicate key name 'reftype_idx'

ALTER TABLE mai_blog_category ADD COLUMN sort_order int(11);
/ Duplicate column name 'sort_order'

ALTER TABLE mai_blog_category ADD COLUMN hide_sub int(1);
/ Duplicate column name 'hide_sub'

CREATE INDEX categoryso_idx ON mai_blog_category (sort_order);
/ Duplicate key name 'categoryso_idx'

Then I open my index page and the version number in the bottum is still 1.0, however the s9y_config_local.inc.php is changed to 1.2.1.
garvinhicking
Core Developer
Posts: 30022
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Post by garvinhicking »

Hi!

What's your URL? The version number on the frontend and in the backend both come from the same file. This shouldn't be possible.

The error message you get actually indicates that the upgrade was executed already!

Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
somy
Posts: 3
Joined: Fri Feb 29, 2008 2:50 pm

Post by somy »

Hi, here is my URL:

http://mai.maimuzi.com/

Thx!
garvinhicking
Core Developer
Posts: 30022
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Post by garvinhicking »

Hi!

In the HTML sourcecode of your URL it says "Serendipity 1.2.1". Where do you still see an old version string?

Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
littlerabbit
Regular
Posts: 15
Joined: Thu Nov 09, 2006 6:41 pm
Contact:

Same problem, but resolved

Post by littlerabbit »

I had the same MySQL errors, but at the bottom of that page I have gotten "Successifully upgraded to 1.3.1". When I went back to the site, it asked me to upgrade again... It turns out that my serendipity_config_local.inc.php was not writable. Once I made it writable and completed the upgrade again I was good to go.
Post Reply