Bug #134

[PATCH] Typo Migrate 34 -> 35 Fix

Added by FuzzyFree - 950 days ago. Updated 479 days ago.

Status :Closed Start :
Priority :High Due date :
Assigned to :FuzzyFree - % Done :

0%
Category :admin
Target version :-
Resolution :

fixed

Description

If you are having trouble migrating from database version 34 to 35, you may want to give this patch a try. It fixes an error where 2 columns were not removed during a previous migrate, and also comments out a line that is not needed and causes an error to be raised.

It does not fix the bug where all comments are disabled on all posts, however, after running migrate you will be able to manually re-enable the comments.

Associated revisions

Revision 289
Added by tobi 1106 days ago

added rss importer. Easy way to get the last couple of posts from your blog on your new typo install (clee) closes #134

History

12/12/2005 03:52 AM - FuzzyFree -

  • Status changed from New to Closed
  • Resolution set to fixed

Please note that this issue is fixed in 797. If you can, just update to 797 instead of applying this patch.

12/12/2005 04:00 AM - pdcawley -

I'm reasonably confident that patch won't work.

The catch is that any existing 

old_ap
or 
old_ac
columns are, in fact, the 'real' 
allow_pings
and 
allow_comments
and they contain the real data. Your best bet in such a situation is to simply comment out the first 4 'schema manipulation' lines and just run the 
Article.find(:all).each {...}
part of the migration from the console and then, having checked that everything went smoothly, use your database client to drop the 
old_ap
and 
old_ac
columns.

Also available in: Atom PDF