You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Derek Hohls <DH...@csir.co.za> on 2004/06/30 15:28:34 UTC

Mismatch between form model and template

Hi all

I got stuck for quite a while on a really simple 
problem... not sure how to avoid this for future.

In my form model I have:

    <fd:field id="testName" required="true">
        <fd:label>Any name</fd:label>
        <fd:datatype base="string"/>
    </fd:field>     

But this field was NOT displayed in the form 
template (I forgot to add in an ft: widget).
Net result was that it looked like the flowscript
had "hung" at that point, and would not display
anything when the submit button was pressed.

There was nothing in any of the logs to indicate
*why* this was happening - is it possible to have
the default behaviour of the forms processor to
report a warning to one of the logs when a required 
field is not completed??

Thanks
Derek


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: Mismatch between form model and template

Posted by Joerg Heinicke <jo...@gmx.de>.
On 30.06.2004 15:28, Derek Hohls wrote:

> Hi all
> 
> I got stuck for quite a while on a really simple 
> problem... not sure how to avoid this for future.
> 
> In my form model I have:
> 
>     <fd:field id="testName" required="true">
>         <fd:label>Any name</fd:label>
>         <fd:datatype base="string"/>
>     </fd:field>     
> 
> But this field was NOT displayed in the form 
> template (I forgot to add in an ft: widget).
> Net result was that it looked like the flowscript
> had "hung" at that point, and would not display
> anything when the submit button was pressed.
> 
> There was nothing in any of the logs to indicate
> *why* this was happening - is it possible to have
> the default behaviour of the forms processor to
> report a warning to one of the logs when a required 
> field is not completed??

We are aware of this issue: 
http://issues.apache.org/bugzilla/show_bug.cgi?id=25302.

Joerg

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org