dg

Thanks, all is resolved now.

Best,

Thanks, the update solved the checkbox issue.
However in my case, a new problem occurs with the latest update. The plugin starts asking for visitor’s location even though a fixed location is set in the weather settings. I did not have this issue with 5.3.1 or 5.3.2.

Thanks,

Yes, it does update upon post/page update, without manually purging cache.

I’m also experiencing the same issue. For me, it happens on some servers, not all.

1- Varnish is enabled, Breeze is on. On a private window, everything works normally.
2- Purge all cache through Breeze, new private window: grouped CSS and JS files are not found.
3- Purging again through Breeze does not help, purging only varnish on Breeze does not help. Logging in to Cloudways account and purging varnish manually through server settings does solve the problem.

– I also tested using other caching plugins, with varnish proxy configured correctly. Purging through those plugins does not work either.
– I tried disabling varnish and enabling again, no luck.
– Breeze purge function does not return any errors, just the success message.

Seems to be a problem with the server’s Varnish settings, but for me, everything is default. Could it be related to the latest Breeze update? I haven’t had a chance to try with the same setting using the previous version of Breeze but I don’t think this will solve it.

Perfect! Thanks

Thank you for the answer, but it does not seem to work. All scripts and styles related to the plugin are still loading on every page. Should I dequeue everything first and then conditionally load them as you suggested?

It also does not seem to save address information provided when logged-in via Google. What I mean is, the address provided when first logged-in via Google is not visible on the next time customer logs-in via the same Google account.

Did you try the following?

[description autolink="yes"]

Here you can find the complete list of template tags.

Thank you for the fix Damian! Any chance this will be implemented to the plugin itself in the future?

@bortnikovarkadiy you can follow the steps, mostly explained in youtube.php:

1- Put script.js and youtube.php files in your WordPress “plugins” folder.
2- Go to wp-admin/plugins and enable the “Popups plugin Youtube fix”
3- In script.js file, replace ‘ID_POPUP’ with the id of your popup (do not include “spu-“, just write the numbers)
4- Edit your iframe by wrapping it in a <div id=”popupVid”>
5- Add ?enablejsapi=1 at the end of your youtube embed code.

After steps 4 and 5, your iframe code should look similar to this:

<div id="popupVid">
   <iframe width="500" height="315" src="https://www.youtube.com/embed/T39hYJAwR40?enablejsapi=1" frameborder="0" allowfullscreen></iframe>
</div>

Now I found out that just “novalidate” is enough. And it works.

Sorry for disturbing the support forum:)

Ok I think I got it by setting ‘novalidate’ => true, in “PhpFormBuilder.php” file. Although on browser I don’t see anything next to novalidate, it seems to work.

Is this the right method? I thought I needed something like novalidate=”something”.

Thanks,

I somehow solved it by commenting out the code on the 5th line, in filters.php. I’m not sure if this is an acceptable solution, but looks like it works for me.

Hello,
Have you been able to find a solution to this?

Thanks,

Hello,
Thanks for the update. Sorry I couldn’t get back to you since I’ve been away for a while. I’ll give it a try this week, and give you feedback.
Thanks again.

I will, at once. Thanks for informing me.