# Extensions migrations and import\_export

**URL:** <https://www.ruby-forum.com/t/extensions-migrations-and-import-export/111078>\
**Category:** Radiant CMS\
**Created:** [August 2, 2007, 12:22pm UTC](https://www.ruby-forum.com/t/extensions-migrations-and-import-export/111078 "2007-08-02T12:22:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Giovanni\_I](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/4491bb/32.png) [@Giovanni\_I](https://www.ruby-forum.com/u/Giovanni_I)\
**Post date:** [August 2, 2007, 12:22pm UTC](https://www.ruby-forum.com/t/extensions-migrations-and-import-export/111078/1 "2007-08-02T12:22:39Z")

</div>

Hi,

I’ve been working (together with Andrea F.) on a project for a  
client that we chose to implement with Radiant.

The project makes heavy use of extensions and some extensions depend  
on other extensions - I also choose to deploy with Capistrano 2.

I wanted something like db:bootstrap to quickly bring up the current  
version of the site, so looked into import\_export. Exporting worked  
really well, while importing had some problems: updated\_by fields did  
not work and Radiant::Configs weren’t imported correctly.

I fixed it by handling the import Radiant::Configs in a different way  
and by implementing a db:remigrate:extensions task. Implementing  
db:remigrate:extensions meant I had to find a way to be sure of the  
order the extensions migrations were run, so I added a priority field  
to extension\_meta, and migrations are run according to priority. Any  
extension can choose its own priority setting the meta field.

Should I create tickets with these additions? They’re correlated so I  
don’t know if I should release them or not.

Bye,  
Giovanni

---

<div class="post-metadata">

**Author:** ![Giovanni\_I](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/4491bb/32.png) [@Giovanni\_I](https://www.ruby-forum.com/u/Giovanni_I)\
**Post date:** [August 2, 2007, 3:22pm UTC](https://www.ruby-forum.com/t/extensions-migrations-and-import-export/111078/2 "2007-08-02T15:22:07Z")

</div>

Giovanni,

import\_export was just one of those weekend proof-of-concept things; I’m  
surprised to see anyone using it seriously. Any patches you can  
contribute would be awesome. At some point we will need a robust  
import/export system for Radiant anyway, and it would be easiest just to  
fold it into trunk when it’s solid.

Sean

---

<div class="post-metadata">

**Author:** ![Giovanni\_I](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/4491bb/32.png) [@Giovanni\_I](https://www.ruby-forum.com/u/Giovanni_I)\
**Post date:** [August 3, 2007, 9:15am UTC](https://www.ruby-forum.com/t/extensions-migrations-and-import-export/111078/3 "2007-08-03T09:15:16Z")

</div>

Sean your weekend proof-of-concepts works are a good foundation for me  
🙂  
I’ve kept fixing bugs but right now it depends on my patches to  
radiant to enable db:remigrate:extensions, I’m thinking about a way to  
make it work without those patches.

2007/8/2, Sean C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):