> > I think that sounds like a plan. So then would that multi-dimensional > array allow for storing multiple sites and configuration options? > > Is that sound? Is this designing too far ahead? Possibly? > > hm...i am thinking in: - make changes to permit direct access to a config variable (not serialize array), and store variable sites. - make a new table for user variables aiki_user_meta (like wordpress). This table can be user to add customizedl fields to user, too. - instead load config.php, load config-site1.php or....In run-time we don't need manage two sites at same time. But these config files only must have essential variables: connection and url_site.
roger -- You received this bug notification because you are a member of Aiki Framework Admins, which is subscribed to aikiframework. https://bugs.launchpad.net/bugs/795393 Title: the config coptions in config.php not ready for multiple sites Status in Aiki Framework: Confirmed Bug description: The config options in configs/config.php are not ready for multiple sites. Need to figure out some structure for multi-sites. For backwards compatibility could do: $config[SITENAME][OPTION]; ex: $config['example.org']['db_name'] = 'example_org'; Any other thoughts? But have to think this through, since no current option could have an OPTION name To manage notifications about this bug go to: https://bugs.launchpad.net/aikiframework/+bug/795393/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
