Issue Bug Closed

#99243Wrong behaviour when using property and value together

Josua Vogel 12/02/22, 07:56 updated 10/15/24, 09:30

Description

According to the docs, name and value should be ignored, if property is set. I`m using the view helper like this:

<f:form.textfield
                    id="{id}"
                    name="customName"
                    property="{property}"
                    value="customValue"
                    placeholder="{placeholder}"
                    class="input__field form-control{f:if(condition: '{class}', then: ' {class}')}"
                    errorClass="{errorClass}"
                    additionalAttributes="{additionalAttributes}"
                    data="{data}"
                    aria="{describedby: 'error-label-{id}'}"
                />

This is the result:

<input required="required" aria-describedby="error-label-email" class="input__field form-control" id="email" type="text" name="tx_myextension[customerData][email]" value="customValue">

The name attribute is ignored, but not the value attribute.
I´m not sure, what is wrong. Maybe the code, maybe the docs.

Inside the view helper, I found this part:

* The value is determined as follows:
     * * If property mapping errors occurred and the form is re-displayed, the *last submitted* value is returned
     * * Else the bound property is returned (only in objectAccessor-mode)
     * * As fallback the "value" argument of this ViewHelper is used
if ($this->respectSubmittedDataValue) {
            $value = $this->getValueFromSubmittedFormData($value);
        } elseif ($this->hasArgument('value')) {
            $value = $this->arguments['value'];
        } elseif ($this->isObjectAccessorMode()) {
            $value = $this->getPropertyValue();
        }

I can fix this, if someone tells me, which would be the correct behaviour.

Reviews 2