The URL you provided requires Admin access to your site to view. I think this is the form you’re asking about based on the post id.
The Google Form confirmation page can hidden using CSS. The easiest way to do this is to temporarily turn off the confirmation page redirect. This allows you to easily find the HTML elements and classes which you can then hide using “display: none;”. Once you’ve got the content hidden, turn the redirect back on and see if the final result is acceptable.
Marking resolved due to lack of follow up.
Hi Mike, sorry for the delay. Yes, that is the correct form.
What I did is this: I created a post where I call the shortcode for the Google Form plugin, then I created a Page with the confirmation and placed a link to that page inside the “Confirm URL” field. I looked into the standard confirmation page’s code to see a DIV that I could hide with CSS but the only one I could find is .ss-resp-card that only hides the text of the confirmation page, not the whole page. Any solution around this? There is absolutely no way to remove this delay completely?
Thank you!!
There is no way to remove the delay completely because the plugin doesn’t know the difference between the confirmation page Google generates and the “next” or “previous” page of a multi-page Google Form until the WordPress page has already started rendering.
The AJAX confirmation page has the least amount of delay but it doesn’t always work due to the various ways WordPress themes are constructed.
This sort of question comes up pretty regularly so I’ve written up a step by step process to show how I setup a custom confirmation page.
Thanks for a great plugin and excellent support. Thanks to this information, my redirect works to my custom confirmation page. I just have a couple minor questions
- Any advice on finding themes that don’t break the AJAX? I am using theme “WP 2016” and the AJAX style does not work FYI
- Maybe the custom confirmation set-up would be less error prone if somehow choosing “style=none” were labeled more clearly as something that disables the whole custom confirmation process?
