At that point, it should only get nil if the YAML file was not correctly loaded ( data['records'] is the meat of the template ).
Sean Jonathan Métillon wrote: > From: Sean Cribbs <[EMAIL PROTECTED]> > >> To: [email protected] >> Date: Thu, 31 May 2007 11:05:34 -0500 >> Subject: Re: [Radiant] My own custimized db:bootstrap >> >> Check out the bleeding-edge import_export extension. In creating it, I >> leveraged a lot of existing code in the db:bootstrap task, so it >> essentially creates a template similar to the predefined ones. >> *However*, it also loads users from the template, unlike the >> pre-packaged ones. The extension essentially works but may have >> undiscovered bugs. Caveat emptor. >> >> Sean >> > > I exported very easily to YAML using /admin/export > > And I created a new Radiant app with empty template, then: > > rake db:import TEMPLATE=export.yml > > The migration starts and fails at: > > == AddOptimisticLocking: migrated (0.4705s) ============= > > rake aborted! > You have a nil object when you didn't expect it! > You might have expected an instance of Array. > The error occurred while evaluating nil.delete > > You can review the full rake task log with trace here: > http://paste.ubuntu-nl.org/23550/ > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
