No, i was not using the rails command, but i have found out what was causing this behavior for me; I don't know how, but suddenly the radiant rake tasks were copied to the /lib dir of the project. Since these already existed in vendor/radiant/lib, they were executed twice, which caused the migrating back to version 0. I found out because when i ran "rake -T" to show available tasks, all radiant tasks had their description double a la:
rake radiant:update # Update both configs, scripts and public/javascripts from Radiant / Update both configs, scripts and public/javascripts from Radiant So, if anyone else has this, deleting all rake tasks in the project/lib folder should fix it.. Met vriendelijke groeten, Benny Degezelle Gorilla webdesign www.gorilla-webdesign.be > Date: Sat, 09 Jun 2007 12:18:36 -0500 > From: Sean Cribbs <[EMAIL PROTECTED]> > Subject: Re: [Radiant] db:bootstrap issue continued > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Unless you intend to hack Radiant into your Rails app (refer to the work > Matt and Loren have been doing lately), don't use the 'rails' command at > all. Just the 'radiant' command will do. It's very possible that it's > not correctly running the migrations because the boot/environment files > are not being overwritten. > > Sean _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
