woody repeater with output only

[Bert Van Kets <be...@vankets.com>]

I'm using Cocoon 2.1.4
I have a repeater in a woody form with static output. Just 1 element in the
list may be changed (a member status).
I display most of the data with <wi:styling type="output"/> but there's one
major dicadvantage here. When I use the delete-row action, non of the output
fields are displayed after the delete has done it's thing. The reason is
that the output does not create any form fields, it merely displays the data
in the page. The solution is to add the data in a hidden field using
<wi:styling type="hidden"/>.

Why isn't this like this by default?

Bert



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

Re: woody repeater with output only

[Joerg Heinicke <jo...@gmx.de>]

On 11.03.2004 17:36, Bert Van Kets wrote:
> I'm using Cocoon 2.1.4
> I have a repeater in a woody form with static output. Just 1 element in the
> list may be changed (a member status).
> I display most of the data with <wi:styling type="output"/> but there's one
> major dicadvantage here. When I use the delete-row action, non of the output
> fields are displayed after the delete has done it's thing. The reason is
> that the output does not create any form fields, it merely displays the data
> in the page. The solution is to add the data in a hidden field using
> <wi:styling type="hidden"/>.
> 
> Why isn't this like this by default?

The problem is the following: when using styling output no form fields 
are added to the HTML, but they are expected when the request comes 
back, because you have defined them as fields in the form definition. If 
you don't want to let set them via the request use wd:output instead of 
wd:field in the definition. We are aware that wd:output exists only for 
wd:field: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27598.

When using style type="hidden" the inputs are in the HTML and so the 
values come back from the client. But - and that's probably not expected 
- they can be changed by the user, the value on the server is changed 
then and you have changed values though you did not want to allow this. 
wd:output prevents this.

Joerg

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