Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MCW lost values by submit-on-change #44

Open
zonky2 opened this issue Apr 15, 2019 · 2 comments
Open

MCW lost values by submit-on-change #44

zonky2 opened this issue Apr 15, 2019 · 2 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@zonky2
Copy link
Contributor

zonky2 commented Apr 15, 2019

If I have entered values in the MCW and have not yet saved them, they will be lost if I have a submitOnChange in another input field

@zonky2 zonky2 added the bug Something isn't working label Apr 15, 2019
@zonky2 zonky2 added this to the 3.4.x milestone Apr 15, 2019
@discordier
Copy link
Member

Uh, that is a big one, as the MCW is rendering via ajax now, isn't it @stefanheimes?

@Total-Reality
Copy link

Total-Reality commented Jan 16, 2021

I can't confirm this. I tested it with Contao 4.9 & MCW 3.4.9

  • Changes in some MCW fields are saved after changing another field with submitOnChange attribute.
  • New added MCW fields are saved after changing another field with submitOnChange attribute.

@zonky2 zonky2 modified the milestones: 3.4.x, 3.5.x Aug 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants