Hello Laraurkiola,
Can you please share a link to the page on your website where we can test the form? Without the link it would be difficult to debug.
Yeah, of course. Sorry I didn’t share it: http://laumedia.es/
I’d appreciate a lot if you could help me! Thanks!!!
Hello,
Thank you for sharing the link. I was able to check the error. Can you please let me know the exact version you are using?
P.S. Please note as a PRO user and have an active license, you can also contact us at https://mc4wp.com/contact/.
The version of WordPress is the last one: 4.3.1
And the version of the plugin: 2.7.23
I downloaded it last week from the web, and it seems to be updated.
Thanks for the info for the next time π
Hello,
Thanks for sharing the details. To debug this, I shall need some more information. Can you please email us at “support @ mc4wp.com” with a link to this post. From there we can take it further and try resolving this at the earliest.
Hey Lara,
You’ve got mail! We fixed the issue, so I will be closing this issue now.
On a related note, please note that you can use the following to set a custom “loading text” instead of using the AJAX loader.
<input value="Β‘ME APUNTO!" type="submit" data-loading-text="One second..">
Hope that helps. If not, let me know!
Perfect!!
And do I need to deactivate any option if I add this loading text?
Thanks a lot!!!
Hey Laura,
No other changes required except the line my colleague shared.
Yeah, I did it, but then it doesn’t lead me to the confirmation page :S
Hello Laura,
I just tested the form, and while I did receive a confirmation email, the submit button did not work as expected.
Did the form worked earlier before you added the above code?
Yeah, as it seems, it worked without the data-loading-text…
If data-loading-text is ON, it sends a confirmation email, but doesn’t redirect to the confirmation page.
And if the data-loading-text is OFF, it redirects to the confirmation page, but doesn’t send a confirmation email…
How is that possible?
Hey Laura,
Ugh, good catch. I just took a closer look and for some reason, the older bug I thought we fixed was still there. I have just updated the plugin on your site and made sure it is now fixed forever.
Hope that helps & sorry for the hassle!