Unexpected error message: "Assign 'On Submit' action in Triggers section to submit the form."

I’ve added a Popup Form to one of my pages.
This form has an associated trigger for On Submit.

Despite this, and despite the form submission actually working, I get the following error message:

image

What do I need to do to correct this?

Hi @travis_s,

This message says that you should assign an action to the ‘On Submit’ event of the Popup Form. This means you go to the settings of the Popup component, scroll down to the Triggers section and assign an action to the ‘On Submit’ trigger.

This action will then run every time the submit button is pressed, and {{data}} will contain all the values of the inputs.

You say the submission is working for you, how exactly are you doing it? Just straight up working with {{ui.popupForm.values}} and a custom button or something like that?

1 Like

Hi @Max, thanks for the reply!

Yes, we do already have an action set up for the On Submit trigger. I didn’t word this well in the first post.

1 Like

I just noticed myself that it still shows with the trigger set. If it is not intended that the warning shows when the trigger is set, then this might be an issue with UI Bakery not correctly checking the triggers.

But, this only concerns the editor view anyway, so a user will never see that notification. I don’t think there’s any straightforward solution that doesn’t require some hack.

@Kate could you confirm with the developers if it’s intended that the warning shows even if the trigger is set? Thank you.

Hi guys,
This feature was released yesterday, but it looks like there might be some issues with it. We’ll try to reproduce it on our side, and I’ll get back to you.
Thanks!

Hi @travis_s

This might be silly, but I’ve reproduced it now, and actually, clicking the X on the alert did the trick. Could you please see whether it works for you?

Hi @Kate , if I press the X on the alert, the alert disappears, but it comes back the next time I submit the form again.

Hi @travis_s
I’ve already informed the team about it

Hi @travis_s

The hotfix is already available in the cloud version. If you are self-hosting, the fix will be available in the rc version tomorrow. You can follow the updates on our changelog.