Mandatory fields in checkout/address step ignored

[MarcBlasig]

Apologies if that question has been raised before or if my configuration is faulty, but I have set up "address2" as a mandatory field (and set the validation rule to ".+"). If I proceed to checkout a basket, in the "address" step my payment address is selected by a radio button. If I click on it, the full form fields are shown, with "address2" being empty and mandatory. Clicking on "Next" is then prohibited due to missing mandatory fields (as I would expect). However, if I don't click on the address, or even if I click it and afterwards collapse it again, I am allowed to proceed by clicking on "Next". How is that possible and how can I enforce the behaviour to not go any further unless all the mandatory fields are filled (it not just happens with address2).

plugin.tx_aimeos.settings.client.html.checkout.standard.address.billing.mandatory.0 = order.address.address2
plugin.tx_aimeos.settings.client.html.checkout.standard.address.delivery.mandatory.0 = order.address.address2
plugin.tx_aimeos.settings.client.html.common.address.payment.mandatory.3 = address2

Is what I have - maybe something is missing? But it seems to work as long as the fields are visible (which they are not all of the time).

Any help would be greatly appreciated!

[aimeos]

Which Aimeos version do you use?

[MarcBlasig]

Thank you for replying

I am on the TYPO3 extension 25.10.3 and on TYPO3 12.4.42.

PS: Sorry for not adding those information in the first place. The reminder text is red, but pretty tiny so I overlooked it.
PPS: Regular registration for your forum seems broken, because of the Captcha. I can click on shoes all I want, it still claims I didn't do it right

[aimeos]

How to set the form fields mandatory, optional or hidden is documented here:
https://aimeos.org/docs/latest/frontend ... orm-fields

If you do it like you did in TypoScript, it overwrites only the first configuration setting (firstname). Better use:

Code: Select all

plugin.tx_aimeos.settings.client.html.common.address.payment.mandatory {
    0 = firstname
    1 = lastname
    2 = address1
    3 = address2
    4 = postal
    5 = city
    6 = languageid
    7 = email
}

[MarcBlasig]

Ok, I was just posting the "relevant" (meaning "address2") portion of the setup, I am already on

Code: Select all

                        
plugin.tx_aimeos.settings.client.html.common.address.payment.mandatory {
  0 = firstname
  1 = lastname
  2 = address1
  3 = address2
  4 = postal
  5 = city
  6 = email
7 = countryid
}

Also, that is working as intended everytime you actually "see" all the form fields, for example on the "my profile" page, and also in the checkout process when you actually display the full address data by clicking on the preselected radio button option.

The problem is that you can skip providing all the mandatory fields by just clicking "Next".
As a clarification, I want to implement the shop on a website with lots of existing frontend users as a new feature. So there is no registration process that demands "address2" to be set before entering the shop (which would be easiest as you can not save addresses without it as it is - the typoscript setup seems correct). I could of course write some middleware that checks if all the mandatory fields are set for the frontend user in shop context and prevent them from actually using the shop unless the fields are set, but to me, this seems like a bug that should be tackled officially as well.