DHTML problem with Lyons

[erebo85]

Hi all,
i'm trying to link DHTML forms and table to make something like this the problem appear when i push the botton in the form, the number of row in the table increase by 1 but the cells of the table are all empty!
i'm going crazy to solve this problem, and i saw that also the DHTML forms and table here doesn't work anymore!
my code is:

{{dhtml.form{inputs:[{label:"numero",field:"num"},{label:"Titolo",field:"titolo"},{label:"Indirizzo web",field:"indirizzo"}],button:"Anteprima", publish: @clip}}}

{{dhtml.table{columns: [{field:'num',label:'Numero CD'},{field:'titolo',label:'Descrizione'},{field:'indirizzo',label:'Indirizzo WEB'}], subscribe: @clip}}}

i have a similar problem if i use page.uri instead of @clip, the difference is that i see in the uri the fields with their value but at the end of the uri i see again the fields with no value ( naturally i've clicked once on the button ) ...something like this: ?num=5555&titolo=5555&indirizzo=5555&num=&titolo=& indirizzo=
instead of ?num=5555&titolo=5555&indirizzo=5555

{{dhtml.form{inputs:[{label:"numero",field:"num"},{label:"Titolo",field:"titolo"},{label:"Indirizzo web",field:"indirizzo"}],button:"Anteprima", publish: page.uri}}}
{{__request.args.num}} -|- {{__request.args.titolo}} -|- {{__request.args.indirizzo}}

can anyone help me?

[erebo85]

no one can help me?
please I have big trouble with a lot of pages in my wikis, this problems begins after the upgrade tothe new release...
can i try to downgrade the wiki? ...and how i can downgrade?

[crb]

no one can help me?

Super-SteveB can, and this bug report is certain to get his attention!

[sean]

Hi there,

I would like to second this plea for help. I am using page.uri in my dhtml.form calls and seeing the repeated argument that the OP refers to. This is a major regression for us.

Cheers,

Sean

[sean]

In an ugly hack - this problem can be fixed for me by removing the 'hidden inputs' from the dhtml.form extension.

Specifically this bit:
<td>

<eval:foreach var="input" in="args.inputs" test="input.hidden">
<input eval:name="input.field" eval:value="input.value" type="hidden" />
</eval:foreach>&#xA0;</td>


Even if I set 'hidden' to 'false' this still gets generated (even though the default should be false).

This is not really a maintainable solution. Can the dhtml.xml script be fixed soon?

Thx,

P.S To be sure, to be sure this same note is posted here in the forum and in the bug :-)

[sean]

According to the docs, <eval:foreach> has a 'where' clause but not 'test' clause??????
I haven't tried testing this - because ultimately I would like it fixed in the mindtouch script - just trying to provide some clues to speed up the fixing ;-)

[SteveB]

Sorry for the delay and thanks for filing the bug. I'll take a look at it today.

[SteveB]

Ok, figured out the problem. There was a regression in 9.02 that no longer recognized the "test" attribute on <eval:foreach>. 9.02.2 will have a fix for that. I'm going to change dhtml.xml to use a more clunky version with a nested <eval:if> which does essentially the same thing. The dhtml.xml script at http://scripts.mindtouch.com/dhtml.xml should be updated within the hour. Just restart it from your control panel and you'll be good.

[SteveB]

The script is updated.

[sean]

Hi Steve.

Appreciate the fix :-)

Overall I like all the extra features in 9.02. Seems like there have been a few small regressions (__count in nested foreach loops is another one we found) - but it is great to see you guys committed to getting on top of these quickly - love your work

Sean