Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter pixelready

    (@pixelready)

    @danieliser
    Okay, the workaround works: setting the title font to Arial or “Use your theme fonts” for the Hello Box theme kicks the Google font from loading – thanks for the tip.
    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?

    I don’t quite understand where the problem lies either? You would only need to change line 165 in pum-install-functions.php so that, like with the other themes, the Montserrat font is no longer loaded from Google. As far as I understand, that would be a 5-minute fix, and everything would be GDPR compliant again!?

    The problem for users in the EU arises precisely because no normal user even notices this and might then end up with a lawyer’s letter on their desk!

    “So to confirm, are you saying on your tests you deleted the built-in themes and they came back? If so, that is definitely a bug we haven’t covered.”

    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). In any case, in order to avoid liability as an agency, we have to implement your workaround for a large number of clients until you provide a fix. Therefore, the 2-star rating remains for now, even though I’ll tone down the review a bit in a moment. Anyway, the problem and our conversation are already costing me a lot of time that I don’t really have. 😉

    Thank you and have a nice day.

    Thread Starter pixelready

    (@pixelready)

    @danieliser
    Thank you for your reply and the tip about deleting the themes! We didn’t think of that, because it doesn’t really make sense for us – because then you wouldn’t need any pre-built themes.
    Specifically, in your pum-install-functions.php file, the “Hello Box” theme loads the Montserrat font directly in the code. And the parent function “function pum_install_built_in_themes” can’t even be deactivated quickly via remove_action – which would also lead to the same result as deleting all themes.

    That wasn’t the case a while ago – everything was fine with the GDPR! It’s all the more annoying when you suddenly run into problems because a Google Font “nests” itself in again.

    Oh, and yes, I do have to apologize!
    Unfortunately, my colleague did post it on one of the “many other popup makers”! I’m very sorry about that, and I’m upgrading the review to 2 stars. This is because there are actually letters from lawyers to customers, precisely because of the integration of Google Fonts via Google. This costs customers money and hassle. We only discovered the problem by chance, precisely because the plugin was previously GDPR compliant.

    It would be great if the problem could be resolved quickly, because otherwise it would cause a lot of work for us to replace the plugin for all our customers. Then I could imagine updating this review.

    Thanks and good luck

    • This reply was modified 8 months, 1 week ago by pixelready.
    • This reply was modified 8 months, 1 week ago by pixelready.
    Thread Starter pixelready

    (@pixelready)

    yeah, yeah – there are other bad reviews here from users of the Pro version, too – where else should we rate it? And: Did you read my review? Why should I submit another support request now when your two previous answers to our five requests didn’t help and the last three requests weren’t answered at all?

    Just bring back the old reliability, which hasn’t been there since about a year – then you don’t need to waste your time answering bad reviews here. Until about a year ago it was a great plugin – and when it hopefully becomes reliable again, I’ll be happy to correct my rating here.

    We definitely need two breakpoints to display the carousels adaptivly for tablets and mobile!

    Yes, please fix it as soon as possible. I run it on a multisite installation and all templates and pages now shows “this block isn’t supported by your theme” …
    As WordPress releases beta versions early enough for developers to update their plugins you should make sure next time that a WP update doesn’t break your block – otherwise I can’t recommand it for professional use 😉
    By the way: if it works, it’s a great plugin, giving users the opportunity to have a WYSIWYG slider instead of building sliders outside of the page designs.

Viewing 5 replies - 1 through 5 (of 5 total)