Hi Glenn,
> Nik, > > Is there an XSLT extension that is needed? I get a parse error > on one of my > sites with PHP support: There is an xslt extension required -- the xslt engine is sablotron and uses expat for parsing. I've installed the xslt extension on both windows and unix, and neither was difficult. On windows, you just uncomment the "extension=php_xslt.dll" line in php.ini and make sure your dlls are in the right places. On Unix, configure PHP with the following options: --enable-xslt --with-xslt-sablot=<path to sablot> > > Another solution is to have CVS handle it... > > That works for me. > > Yes. There's a 'dqsdweb' module now in the same repository. > Dave set it up so that the server pulls the latest from CVS > every 15 minutes or so. Okay, for this to work we'll need a command line xslt engine. The triggers all take effect on the repository server. We can use the CVSROOT/loginfo file to set up a trigger on commit. http://www.cvshome.org/docs/manual/cvs_18.html#SEC171 This is the file that's normally used to send emails to developers when files have changed. I suspect it's possible to set up a rule for a specific file within a repository. The problem then lies in getting the HTML file back to the clients... If we add faq.html to the repository, then we can write a script that will update faq.xml, rebuild the .html, and check in the .html. Seems like it might be a bit of a run around. Things are pretty crazy at work for me, so I don't have too much time to dedicate to it at the moment. nik ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
