> > 1. There are a couple of other extensions that appear similar (Sean's > Import/Export and and Istvan Hoka's Super Import Export come to > mind). How is yours different?
The file_system extension does not attempt to back up the entire database representation of your Radiant website, whereas the other two that you mentioned do. The main goal of the file_system extension is to make pages, snippets and layouts easily editable as files on your file system. This allows you to use your usual text editor, rather than having to do everything through the Radiant admin. It is most useful when you are designing (or redesigning/refactoring) a site. > 2. If I use the file_system extension with other extensions (like, > say, SnS) is it aware of these new models? Will it export them too? No, not out of the box. However, the file_system extension has been designed so that other extensions can ride along with the import/export process. For example, Sean Cribbs template_extension[1] adds his custom Template and PartType models, so that these are also saved to the file system. Naturally, this code belongs in the templates extension, rather than in the file_system extension, because you only want to back up Templates and PartTypes if you have that extension installed. I would be happy to work with you, Chris, in making SnS play along with the file_system extension. If you are looking to backup your website to the filesystem, I would say that the (super)import_export solutions are a better fit. These should capture all tables in your database as yaml files. (There is one possible exception, which I will detail below.)* I hope that this helps to clear up any confusion. Cheers, Drew * The import_export extension can back up all database tables whose name translates using the normal Rails conventions. e.g. pages (table) with Page (model), page_parts (table) with PagePart (model). In the Radiant core, there is just one model which breaks this convention: the config table corresponds to a Radiant::Config model. This is given special treatement in the import_export extension, to make sure that it is captured in the yaml file. If any other extensions include models whose name cannot be discerned from the corresponding table name, then they will not be backed up to the yaml file. [1]: http://github.com/seancribbs/radiant-templates-extension/tree/master _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
