Today I updated the forminator plugin and now on all my forms the next button does not work. I already tried:
Nothing worked so far… Could anyone help with that?
Thanks in advance!
Markus
I have created an example form to show the bug easily.
The field is required even when it’s hidden to move to the next page. I can use the radio button to hide the second field, but it is still required.
Hidden field shouldn’t remain as required fields, and shouldn’t block moving to the next page. It only should block when the field is shown. It was like described in older versions of the plugin.
Without pagination it is no problem, direct submit works fine.
I’d be very happy if you can solve this fast, as we rely on the plugin in production environnment, thank you for your work
]]>I chose the Hueman theme a few days ago. Everything is fine except for the navigation menus (previous and next).
I installed the CSS in Simple CSS but afterwards I don’t really see what I should do!
Thanks in advance,
Best regards,
Claude
]]>is it possible to create a validation or dependencies for the next button?
I’d like the user to write an access code (ie. a number between 10 and 20) in a field to step to the next page.
If the number is not correct, then an error message should appear instead of the next page.
I can create dependencies for other fields but not for the next button.
Thank You!
]]>My question is, how do I fix this? I need the “next” link to actually link to the next live page, not the one I messed up with/dead link to it.
]]>I created a custom post type specifically for “thank you” pages. For some reasons it shows next/back buttons below the content.
This means it would mess up google analytics since people could reach thank you pages without filling in the form.
I double checked all the settings and they are identical to other custom post types I created and they don’t show the next/back links.
Any idea how to get rid of them?
Thanks a lot in advance!
Chris
Screenshot: https://i.imgur.com/tfCTLLc.png
]]>$(function(){
setTimeout(function(){
$('.ays_buttons_div').fadeIn();
// $('.ays_next').fadeIn();
}, 30000); // milliseconds
})
—————–
But it works only on the first page. Because you are using Ajax, next time it is overwritten by your code.
Could you please help me how to achieve this?
I would like to prevent the user clicking on next button fast, a minimal time spent on the actual question is needed.
Any help would be appreciated.
Thanks,
Peter