Daniel Iser

Early copy if your inclined to test and confirm for us: https://drive.google.com/file/d/11og7MzMndCkUN0PL0lzWkASsBRkGna_C/view?usp=sharing

Okay, the workaround works

Glad to hear. Sorry it wasn’t a more obvious solution right away sadly.

—–

Deleting Hello Box sometimes worked, sometimes it didn’t – and as I described, deleting installed themes isn’t intended to make things easier for users, is it?

No, simply meant to be a solution you could deploy instantly. You could even just mark them draft if your not using them. They are really old and meant to be examples of the variation more so than “hey, use this”.

We are likely eliminating the concept of separate themes in the near future anyways, in favor of saved presets, and you will create/edit them directly in popup editor. Unify the entire experience in a way.

——

that would be a 5-minute fix, and everything would be GDPR compliant again!?

That would only help new installs, but then as soon as they picked a font from the google list they would be in violation again. We need a more robust solution long term.

We’ve got you covered though, used Claude late last night to come up with a plan and experiment; came up with something extremely versatile and reliable, but its a rather large change and would ultimately need to land in a minor release, not a point release:

• Remove usage of API based fonts entirely.
• On release use API to build static JSON file with all current options.
• In all usage, load that JSON, removed the API entirely.
• When selecting fonts it downloads them to wp-content/uploads/pum/fonts
• CSS then uses the local fonts only.

Permanent, reliable solution that works instantly for all existing users as well.

Added benefit of no API usage limits etc.

ETA likely next week or 2, we are actually aiming to get out at least one minor release every 3-4 weeks, patches as needed. The list of new features & improvements has grown extensively over the past 18 months rebuilding a lot of the plugin. So we are happy to iron out any lingering technical debt, GDPR kinks etc.

To be honest we were the first popup plugin and one of the first plugins in general to intentionally support GDPR, same for Accessibility, performance and such. Doesn’t mean there weren’t flaws 🙂

—–

No, that wasn’t the case in our tests. But it did happen that we deleted all the themes and Montserrat still loaded (all caches cleared certainly, tested in different browsers)

Hmm, 🤔. I think you could actually have had our AssetCache generated CSS saved and that wouldn’t necessarily be purged when you purge your caching plugin, though its probably something we can add in a future version.

In that case, just checked and deleting a theme wouldn’t trigger a regneration it seems, small oversight a decade ago, but only updates the CSS on save of a theme/popup or update of the plugin.

There is an item in Popup Maker -> Tools -> Clear popup asset cache in the frontend admin toolbar that does it instantly.

Hope that helps.

@guillemgalli – Do you use any elementor templates or similar shortcodes within your popups? If so the problem may revolve around content in one of the popups. You can use the Enable toggles to quickly disable all of your popups, then retest.

If that fixes it, the plugin alone isn’t the problem and we can dig deeper.

Next would be reactivate them one by one til it breaks again to identify the specific popup or popups with content that conflicts.

In the mean time I’ll review all changes to the popup loading flow, which there were not very many honestly as this update was more around adding Call To Actions than updating popup. The only major change for the popup editor in reality was switching to block editor by default.

That said we have a report from a Beaver Builder user with some new rendering issues. We will get to the bottom of both fairly quickly once we get more debug info to narrow in.

Typically issues like you describe means that some content was either enqueued too early or too late, and the page builder wasn’t built to account for popups or any code rendering their templates outside of a specific box (the loop). Granted our plugin has always done this, but the breaking change could literally be one action hook changed priorities too early/late.

@pixelready – any chance we can soften the review title a bit in the mean time? Of course once I fix it I’d love a full update on the review/stars, but will make sure its working before I make that ask.

• This reply was modified 8 months, 3 weeks ago by Daniel Iser.

@dissoskaarki – Sorry to hear that. That said you can simply mark the box to disable asset caching and this notice would be gone, same as clicking the “Keep Current Method” link should have.

The notice is simply saying were defaulting to fallback mode because your server didn’t let us write files as expected.

It definitely shouldn’t be annoying you, but it shouldn’t be dismissable without a decision made either, which is what its trying to enforce.

If the “Keep current method” option isn’t dismissing it properly, were happy to help work that out for you, nobody likes annoying notices, including us.

Ping us at https://wppopupmaker.com/support/ if you wanna try to resolve an issue, if not would love to get this review updated given its not really supposed to be annoying, that is clearly a bug or simply not as clear with our messaging about choosing to leave things in the fallback mode. But neither feels like a great reason to lose 4 stars if were being honest?

@samuelng527 – In the latest version we changed to support the block editor by default, you should simply be able to use /column I believe within the block editor to show the columns block which should handle it for you quite nicely.

In the next major update we should be adding premade layouts as well to help speed things up greatly going forward.

Hope that helps.

PS if you use a page builder, then you can likely make a saved template and insert that into your popups via shortcode as well.

@dmpinder – HUGE!!! That is great to know. This release was a massive step for us revamping this plugin. All new build processes, more automated testing, complete restructuring of our premium features from 14 disparate features to a new Pro plugin, along with only a few niche Pro+ addons focused on LMS/Ecommerce, addition of trackable CTAs, new pro analytics, revenue tracking, advanced reporting etc.

Honestly I’ve been putting off pushing the button for nearly a week, finally wife said stop tinkering and put it out. Went well for over 2+ hours before this report, thank goodness I had already planned my day around watching for issues.

So your confirmation is great news for sure!

Sample of what I’m about to release in the next few hours hopefully. This is our own cart abandonment popup for the past few weeks running the new stuff on our own site.

Huge plans for the next few updates as well.

@dreamingat30fps – Took a bit longer than I said, but we wanted to dissect this properly, any blanket solutions would have likely led to further issues.

We patched only as much as needed to get it working on 7.4 again.

Apologies, we tested on 7.4 a lot, but then did a bunch of type work which we assumed was all PHP 7.4 safe. Seems it all was except trying to declare a type of string|array using the | seems to be completely unavailable until 8.0. Small oversight but huge potential impact, and likely minimized by your quick ticket. 🙏