The specified value for the 'multiple' property of a 'field' action is not honored. This is a persistent bug regardless of node type or field type. Assuming the referenced type exists this will not set the field to allow unlimited values as it should:

    <field>
      <type>profile</type>
      <name>favorite_urls</name>
      <label>Favorite URLs</label>
      <option>link</option>
      <widget>link</widget>
      <weight>42</weight>
      <multiple>1</multiple>      <!-- NOT WORKING //-->
      <title>optional</title>
    </field>

Comments

vaish’s picture

vaish commented

Recently added experimental code introduced some bugs which are causing this issue. We will try to fix it as soon as possible. Thanks for reporting the bug.

Anonymous’s picture

Anonymous (not verified) commented

This is also not working in YAML patterns

sarvab’s picture

sarvab commented
Status: Active » Needs review

This issue should be fixed now for both XML and YAML. It was caused by confusion of the #option labels and values for the mutiple select value. The label "1", which is actually key 0, was being used instead of the key "1", which is label "unlimited".

The code now looks for keys first over labels.

In this case, using unlimited would also have worked.

vaish’s picture

vaish commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.