Metamodels BE select value don't store

[StefCan]

Hi,

I have updated MM with the latest release from the nightly builds and since the select don't store the value in BE, i have clear the cache, but nothing happened.

It's a bug ?

Contao Version : 3.5.30

Thank's

[zonky]

more informations:

* Attributes,
* Input mask
...

e.g. with screenshots

[StefCan]

Hi,

It's 2 Attributes "select" "Catégories" and "Sous-catégories"

In attachment screenshots of Attributes and Input mask

ThxCapture d’écran 2017-10-14 à 11.06.17.pngCapture d’écran 2017-10-14 à 11.05.10.pngCapture d’écran 2017-10-14 à 11.05.50.pngCapture d’écran 2017-10-14 à 11.06.56.pngCapture d’écran 2017-10-14 à 11.06.35.pngcapture.jpg

[zonky]

hmmm....???

all screenshots looks like good - it´s the Category (select) the only thing that wasn't saved?

.. and pls check the second point: http://metamodels.readthedocs.io/en/.../mm-start.html

[StefCan]

Hi,

"Catégories" and "Sous-catégories" wasn't saved

I have tested with the submit on change and now the value was saved if I uncheck "submit on change" value wasn't saved.

Capture-d’écran-2017-10-16-à-06.35.19.jpg

[zonky]

"submit on change" does not yet save any data - this only happens when you click the "Save"button.

The submit on change" is used to reload the page e. g. for displaying/changing dependent subpallets.

[StefCan]

Hi

I have the same bug on 2 other websites with last Metamodels Nightly Build :

The other website doesn't store the value of the check box, but if I apply "submit on change" and save the value was stored.

I don't know why, but it's the only way to store the value.

[zonky]

can you change to composer and update MM?

[StefCan]

Yes but not this week. I change to the composer next week and give you some feedback.

Thx

[zonky]

note: http://metamodels.readthedocs.io/fr/...rsion-composer