PHP Version: 7.2.26
Wordpress Version: 5.3.2
Plugin Version: 14.10
Current Theme: pes2019
Application Used: Own Application
Active Plugins:
Advanced Custom Fields PRO
Ajax Load More
Classic Editor
Contact Form 7
Enable Media Replace
Force Regenerate Thumbnails
Limit Login Attempts Reloaded
Simple Custom Post Order
Hide SEO Bloat
WordPress Importer
Yoast SEO
WordPress Database Backup
WP GoToWebinar
Hi @wizcomhosting,
When I remove that backslash I was able to submit the form successfully. I got the message: “Success You are registered for Dispelling the myths about financial wellbeing, at 11:00am GMT on 17/3/2020. See you there!”
It looks like that backslash is being added due to a code error..although I am quite surprised this is the first time this issue is being reported…I feel like this should have popped up a long time ago. I will release an update in the next few minutes to resolve this. Thanks,
Thank you very much.
I’m still getting the error;
var calendarDataDecodedAndParsed = JSON.parse(atob(calendarData)); InvalidCharacterError: String contains an invalid character
in Console
And no thank you message (either in Chrome or Firefox)
I can see you registration ‘Dsfsdf’ but not the ones I’m making this morning
Should have said, the Submit is displaying properly now, thanks.
The calendar was displaying fine when I submitted the form this morning. I am not 100% sure why it’s not working for you, what I recommend is doing an isolation test, so try with a different basic theme like Twenty Sixteen, then try deactivating all other plugins except WP GoToWebinar and see how this works. Ensure during testing that no caching is happening on your site.
OK, will do. I removed the calendar (it was only for testing) so we’re only talking about the form
Must be later there no?
This is the console log from Chrome
Uncaught DOMException: Failed to execute ‘atob’ on ‘Window’: The string to be decoded is not correctly encoded.
at HTMLDocument.<anonymous> (https://www.wearepes.co.uk/wordpress/wp-content/plugins/wp-gotowebinar/inc/script.js?ver=14.12:8:55)
Just to be clear, there is no calendar shortcode on the page (nor any div called #calendar – which could cause a problem perhaps?)
I have it working now.
I tried it in vanilla Twenty Seventeen – as you might expect it worked fine
I turned off all my plugins in my site – still didn’t work, so some kind of clash with the (bespoke) theme
I went into the plugin file inc/scripts.js and deleted the first function that populates the #calendar div (I’m not using the calendar) and it works.
Thanks for your help. We probably won’t buy the premium version but I will insist that the client donates – it’s only fair.
Hi @wizcomhosting,
Glad to hear it’s sorted. Yeah I am based in Sydney so there’s a time difference.
Donations are much appreciated 🙂
Thank you,
