Can we store these settings in a table in the DB with a page_id foreign key? Wouldn't that circumvent the page-specific problem? We could agree upon a string format for the settings (i.e. comma separated, pipe "|" separated etc) to be stored in. The schema would look something like this:
id | page_id | extension_id | settings | ------------------------------------------------------ 1 5 1 userName|pass|port|protocol On 1/16/07, Sean Cribbs <[EMAIL PROTECTED]> wrote: > That's the thing, though. Page#config renders the 'config' part and > then parses the YAML from it. > > > What happened to Page#config()? I'd use that because it allows you to > > change the configuration of an extension through the admin interface. > > Of course, it has it's limitations. But I would rather try to find a > > solution to these issues than relying too heavily on > > file-system-level-config files. > > > _______________________________________________ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
