Will Chronoforms be doing a better job at managing external database information?
With over 30+ forms and another such chronoconnectivity it would be nice to have a central "external database" repository. Having it in every single form multiple times makes it very difficult to point the installation to different external databases (think devp, staging, prod regions) having to manually edit each DBREAD/DBWrite on every form.
The best I've done so far is hack MySQLI.PHP driver to look for a specific hostname and then update all the connection fields when doing a connection. At least all I need to do is use a specific literal for my hostname everwhere but now I have to manage that whenever I do Joomla updates.
Is there a different approach so I only have one place for my external DB info?
With over 30+ forms and another such chronoconnectivity it would be nice to have a central "external database" repository. Having it in every single form multiple times makes it very difficult to point the installation to different external databases (think devp, staging, prod regions) having to manually edit each DBREAD/DBWrite on every form.
The best I've done so far is hack MySQLI.PHP driver to look for a specific hostname and then update all the connection fields when doing a connection. At least all I need to do is use a specific literal for my hostname everwhere but now I have to manage that whenever I do Joomla updates.
Is there a different approach so I only have one place for my external DB info?