Card migrations not initialized at wagn create time

Support Ticket

Card migrations not initialized at wagn create time+status
answered
Card migrations not initialized at wagn create time+tags
 

Card migrations not initialized at wagn create time+issues

With v1.11.5, immediately after setting up database.yml, "rake wagn:create" works fine but a subsequent "rake wagn:migrate" crashes.

 

It looks to me as though this is because wagn:create doesn't have anything similar to assume_migrated_upto_version for the card migrations. wagn:migrate tries to run RenamingForMenu, which assumes that there is a card called *content for it to rename to *structure, but the seed data has already been updated to create *structure in the first place.

 

Not that big a deal, since there's a workaround (just put the timestamps for the card migrations into schema_migrations_cards), but it's an irritant and probably a significant issue for non-rails-guys who don't want to understand the plumbing of activerecord.

 

Wow, great ticket. Clear, thoughtful, and you've already conceptually solved the problem. I'll make sure this gets fixed in 1.11.6

--Ethan McCutchen.....2013-06-20 02:34:42 +0000

Yeah, but I didn't actually fix it and send a pull request! So it could have been better.

--Brett Neumeier.....2013-06-21 04:45:06 +0000

You don't need to apologize for anything. I'd nominate you for an award just for digging into the problem. As yet that is a rarity in the Wagn community, and we need many more like you.

 

Thanks.

--Gerry Gleason.....2013-06-21 11:17:54 +0000

Addressed in this commit, currently being reviewed in this pull request

--Ethan McCutchen.....2013-06-21 18:30:26 +0000