Hi, Are migrations currently broken because of the changes to Rails in 2.1? I can migrate a plugin first time, but when I add a new migration to the plugin and try and migrate up, rather than migrating from the current version, Rails tries to run all the migrations from the top. Is this because engines uses Rails' migration engine and thus isn't currently compatible with the new UTC timestamp format? Is there a way around this? Thanks, Tekin
on 2008-06-06 13:41
on 2008-06-06 15:47
I *think* this should work. I'll try writing some tests to verify it - stay tuned to the lighthouse ticket. Cheers, James
on 2008-06-06 17:32
I added a test, but still couldn't replicate this. Can you try? http://engines.lighthouseapp.com/projects/10178/ti... Thanks! James
on 2008-06-09 13:18
Test runs fine for me too. I try do a bit more digging as the same plugins were migrating fine on a 1.2 rails app.
on 2008-08-22 23:07
James is there any movement on this? I recently migrated Substruct to Rails 2.1 and I'm experiencing the same issue. Tried Sven's fork over on github which didn't work either. Seems both of them want to run plugins from my engine from 1 onward. Is there a definite fix by now? -------------------- seth - subimage llc ----- http://sublog.subimage.com ----- Cashboard - Estimates, invoices, and time tracking software - for free! http://www.getcashboard.com ----- Substruct - Open source RoR e-commerce software. http://code.google.com/p/substruct/
on 2008-08-23 07:20
seth b. wrote: > James is there any movement on this? I recently migrated Substruct to > Rails 2.1 and I'm experiencing the same issue. > > Tried Sven's fork over on github which didn't work either. Seems both > of them want to run plugins from my engine from 1 onward. > > Is there a definite fix by now? FYI: I resolved the issue with Samuel's patch available here: http://engines.lighthouseapp.com/attachments/32727...