Jason Johnston wrote:
[me]
Umm. There's already a head element in the template, which is the
sample one from the Cocoon documentation
Are your HTML elements by chance in the http://www.w3.org/1999/xhtml
namespace, or another namespace? The CForms XSLT only matches elements
in the null namesp
peter wrote:
On Wed, 24 May 2006 10:20:36 +0200, Christofer Dutz wrote
If you add a tag called "head" anywhere in your template, then
CForms will add all CForm stuff (CSS, JavaScript, ... everything
that belongs into a html head-tag) it needs inside this tag. All you
have to do in any transfor
On Wed, 24 May 2006 10:20:36 +0200, Christofer Dutz wrote
> If you add a tag called "head" anywhere in your template, then
> CForms will add all CForm stuff (CSS, JavaScript, ... everything
> that belongs into a html head-tag) it needs inside this tag. All you
> have to do in any transformation
Stuttgart, Karlsruhe, Düsseldorf
-Ursprüngliche Nachricht-
Von: Peter Flynn [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 23. Mai 2006 23:13
An: users@cocoon.apache.org
Betreff: Re: AW: Cforms dates and data destinations
Christofer Dutz wrote:
> a: The samples-styling xslt looks for a
Christofer Dutz wrote:
a: The samples-styling xslt looks for a head-tag to insert the javascript.
When starting to use CForms I missed that at first. Either change the xslt
or add a dummy "head" element somewhere. You can move the stuff in another
transformation ;)
Changing the XSLT is easy, bu
Hi Peter
a: The samples-styling xslt looks for a head-tag to insert the javascript.
When starting to use CForms I missed that at first. Either change the xslt
or add a dummy "head" element somewhere. You can move the stuff in another
transformation ;)
b: As far as I understood everything you can
