Thanks for the reply, Geoffrey. What about the options filled out in the back-end for a module? That has to be stored somewhere and it wouldn't be the .xml file. Then again, if you add another field in the .xml file which accepted a parameter on the back-end it's saving it, I assume to some table in the MySQL. Interesting that's managed in a transparent manner.
David Roth On Fri, Sep 14, 2012 at 7:43 PM, Geoffrey Schaller <gjschal...@psi-13.com>wrote: > This may be a different / special case, but... > > With Kunena Templates, when you edit the xml file for the template (which > acts like a component within Kunena), the change is reflected immediately. > To me, this would indicate it's pulling it directly from the XML file, and > not a database entry. > > If Kunena templates operate in the same fashion as modules, that's a good > indication. > > -Geoffrey > > _______________________________________________ > New York PHP SIG: Joomla! Mailing List > http://lists.nyphp.org/mailman/listinfo/joomla > > NYPHPCon 2006 Presentations Online > http://www.nyphpcon.com > > Show Your Participation in New York PHP > http://www.nyphp.org/show_participation.php >
_______________________________________________ New York PHP SIG: Joomla! Mailing List http://lists.nyphp.org/mailman/listinfo/joomla NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php
