Just wanted to say thanks :-)

Just wanted to say thanks.

Really liking all the new features since Pro 4 and the new shorter release cycle is awesome…

4 Likes

Agreed, although it means sites I’m currently building I’m going back to add the new features

anyone say pop up booking form (using the new modal elements)

not to mention using grids in header/footer, and all the wonders of CPT/ACF & Loopers

1 Like

Indeed, absolutely great work. The smaller monthly releases in between bigger releases are very welcomed and exciting.

Thanks for all the hard work!

1 Like

Agreed as well. It’s great to get awesome new functionality on a more regular cadence :raised_hands:

1 Like

Thanks everyone! We appreciate the kind words. It’s really great to hear how much you’re liking the Pro 4+ roadmap. Onward to responsive styling!

5 Likes

Hey @scotbaston - i’ve been doing this for a while just putting the contact form shortcode in a modal, or if I want to jazz it up, doing the ‘old fashioned way’ wit a global block. But anyway, wanted to ask, how do you find it submitting? Sometimes I find if it doesn’t submit via AJAX it closes the modal but doesn’t say whether it’s submitted or there are errors. So the user may assume it’s submitted but if you re-open the modal you realise there’s an error there.
I guess it may also depends on the form plugin functionality too, but be interested to see what you found!

Hi, I’m still building this site at the moment so not done massive testing on the form within a content area but what testing I have done seems to work just fine. I’ll let you know if I encounter the problem you mention

Hi @RubberDuckers,

I’ve seen that before! It’s definitely an issue when using forms that don’t use AJAX. One way I’m thinking we shim that is through the new mechanisms discussed for custom attributes. If there was an attribute like data-x-open-selector=".error-message" and we pointed to an error class from whatever plugin was being used, we could tell the modal to automatically open when the page refreshed. It would have to be configured case-by-case but would at least allow potential compatibility with anything that is output dynamically in the modal/off canvas content.

1 Like

Hey @alexander! Something like that would be good.
In the end, for when I was having issues I found adding this to the functions.php file allowed the form to be submitted using AJAX so it worked:

add_action('wp_head', 'add_loader_gif');

function add_loader_gif() {
  echo '<style>.wpcf7 .ajax-loader{background-image: url('. plugins_url() .'/contact-form-7/images/ajax-loader.gif);visibility:hidden;display:inline-block;width:16px;height:16px;border:none;padding:0;margin:0 0 0 4px;vertical-align:middle}.wpcf7 .ajax-loader.is-active{visibility:visible}</style>';
}

Though, from what I read, CF7 should do that by default so not sure if it’s a clash with something.

Hope all is well!

Thanks! I saw something recently from a customer in support having a similar issue. I do think something is askew with X/Pro not having that style present. We’ll take a closer look at it, and if we change anything in the theme it will be in future release notes so you might need need that extra style in the future.

We would also like to thank you guys.

We’ve been here for a while and shorter and more frequent updates are just perfect with Wp5 making so many changes, so fast. We are seasoned devs who, thankfully, have always found a workaround for everything while the permanent fixes were coming but I know that people that heavily rely on not coding will be the most affected by these releases (in the good way) and that can only improve your sales which in turn will make you live longer… and will continue making our lives easier, lol.

Keep it up.

Thank you!