Seems like this would miss any table without a class. A
has_and_belongs_to_many association, for instance, would not get
exported if I am reading that patch right.
Maybe thats not even an issue :)
-Alex
http://beautifulpixel.com
On Jun 24, 2008, at 3:57 PM, Andrew Neil wrote:
Hi,
I was trying out the import_export extension, and I noticed that it
wasn't backing up records from my subscribers table. (The
subscribers table was added by a migration in the subscriber_lists
extension[1]). Looking at the source, I could see an easy way of
fixing this, changing:
self.models = [Radiant::Config, User, Page, PagePart, Snippet,
Layout]
to:
self.models = [Radiant::Config, User, Page, PagePart, Snippet,
Layout, Subscriber]
I figured it would be better if the exporter actually looked at the
database to find out what tables are there. I've forked the
extension, and added this functionality. Here it is:
http://github.com/nelstrom/radiant-import-export-extension/tree/
master
It seems to work OK for export. It will need a little more work
though for the importer, but that is for another day.
Cheers,
Drew
[1]: http://github.com/nelstrom/radiant-subscriber-lists-extension/tree/master
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
