Opened 19 years ago
Closed 18 years ago
#5277 closed defect (bug) (worksforme)
Posts are de-categorized when upgrading to 2.3.x
| Reported by: | dtc | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | General | Version: | 2.3.1 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
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 (9)
#2
@
19 years ago
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).
#4
@
19 years ago
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.
#6
@
18 years ago
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?
#7
@
18 years ago
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.
#9
@
18 years ago
- Milestone 2.9
- Priority high → normal
- Resolution → worksforme
- Severity critical → normal
- Status new → closed
Closing this as worksforme.
I did a test upgrade from 2.2.3 -> 2.7 and all categories were maintained correctly (posts with no, 1 and multiple cats assigned.)
I'm guessing given the lack of activity that this was a local quirk.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
So I guess this is happening when a post is in multiple categories?