[albatross-users] Auto list bug/issue...

[Andrew McNamara]

>I've come across a strang which is in 1.11+, maybe prior versions as
>well but I didin't check them.
>
>Normally, if you try to have several form fields defined with the same
>name, you either need to use the "list" argument on the tags, or make
>the list in the page object/module.  This is very nice, because
>albatross doesn't pull an perl like bs of thinking for you, and letting
>some bug creep into production because it never caused a problem when
>testing.
>
>However, if you name several fields the same name, but they are
>different types, you can get a field that will sometimes be a list,
>sometime a string.  To show this, here is a simple template that will
>show the problem:

Thanks for the report, Michael. I know it's been outstanding for a while!

The problem is due to inputs that can appear multiple times, but return
a single value (such as radio buttons and submit buttons). This simple
example exhibits the problem also (it should raise an exception on load,
but doesn't):

    <al-form>
     <al-input type="text" name="name">
     <al-input type="radio" name="name">
    </al-form>

I've checked a change in (r8871) that addresses this issue, and I hope
to be able to put out a new release later in the week.

-- 
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/