Ticket #5277 (new defect)

Opened 8 months ago

Last modified 1 week ago

Posts are de-categorized when upgrading to 2.3.x

Reported by: dtc Assigned to: anonymous
Priority: high Milestone: 2.3.4
Component: General Version: 2.3.1
Severity: critical Keywords:
Cc:

Description

When upgrading WP 2.2.3 to either v2.3 or v2.3.1, most of the posts get de-categorized : posts that used to be in categories such as "Blog", "Misc", "Web/Tech" appear to be "Uncategorized" after the upgrade.

I've run the upgrade from 2.2.3 with all plugins disabled and even tried a forced DB upgrade. The first time wp-admin/upgrade.php is run, the result page doesn't load completely. Refreshing the page outputs those errors :

http://img87.imageshack.us/img87/3859/wpqo7.png

There's something wrong with the upgrade script. All the categories have unique names. Here are the catgories in 2.2.3 :

http://img457.imageshack.us/img457/2964/cat223pt9.png

Here are the categories once upgraded to 2.3.1 :

http://img457.imageshack.us/img457/3766/cat231op9.png

The same happens with 2.3

Running :
- Apache/2.2.4
- PHP 5.2.4
- MySQL 5.0.45-community-nt

Logged a support ticket here as well : http://wordpress.org/support/topic/140903?replies=1

Change History

11/04/07 16:12:55 changed by darkfate

So I guess this is happening when a post is in multiple categories?

11/05/07 13:57:03 changed by dtc

No, it happens also when the post is in a single category. The errors appear on a server powered by WAMP. Increasing memory usage does not solve the errors (server set to use 64+ MB for script usage).

11/05/07 18:53:58 changed by darkfate

Well I guess it might have something to do with tagging.

12/03/07 18:08:54 changed by snakefoot

I experience the same error when upgrading from WP 2.0 to WP 2.3, though I thought it was because I had multiple categories with the same slug (though with different parents).

All categories are converted (with renamed slugs), but most of the posts become uncategorized.

01/04/08 23:36:38 changed by lloydbudd

  • milestone changed from 2.3.2 to 2.3.3.

06/25/08 03:44:32 changed by DD32

Judging by the linked support forum post, This might've been caused by a half-upgraded install being upgraded again perhaps?

Does this still need looking into, Or can it be closed off, I'm thinking that if anyone upgrades from 2.0 to a current release, they'll probably pass through the same code, But given the number of upgrades that took place, There should have been more reports if there was an issue?

06/25/08 10:45:14 changed by dtc

It happens when using a Windows machine with WAMP (latest version) or with - Apache/2.2.4, PHP 5.2.4, MySQL 5.0.45-community-nt installed manually.

It looks like a timeout or memory issue (even if the default memory values are upped in each of the services' configuration). The box has 2 GB of RAM so I'm at a loss there.

When I did the upgrade on my live site, all went well. Only the local upgrade fails.