I can confirm that using the pixel option instead of the dropdown UI does work. I’m not sure where the UI is coming from, honestly. I don’t think I’m using anything obviously related, but I’m also not experienced enough with Gutenberg to know what’s normal.
To check, I spun up a vanilla WP 6.8.3 instance and installed just Meta Field Block. The interface looks slightly different from the screenshots I posted earlier, but functions the same:
UI on the minimal install
The effect in that case is identical with the --mfb--gap is not defined situation. But again, setting it to 0px is a viable workaround.
+1 on the original complaint. It’s very unexpected to click the close button just to have the upsell show up again on the next page… over and over and over…
My issue and solution were similar to @khdigital’s, except in my case the configuration file was correct but the file ownership wasn’t. When I updated the files and folders to belong to the user specified in the configuration, the error went away.
I encountered the same issue, but noticed that my existing, unmodified widgets were still following the rules; only a new one was affected. This made me think that the issue isn’t in the code that displays the widgets, but rather with the code that saves the rules from the settings screen.
With that in mind (and after reading the other comments in this thread), I downgraded the plugin, set up the new widget, and then upgraded the widget again to the latest version. That worked, and since I prefer to have the 1.5.14 update, I’ll jump through the hoops again if I need to make changes before the issue is resolved.
Jumping in to say I encountered this same issue, only on one page, and it turned out to be a PHP error in a (custom) module. For any future debuggers reading this, take a quick peek at your PHP error log to rule that out, too.
Is this fix still in the works? I’m having trouble with PowerPack Beaver Addons (I know it’s not your product) and it seems to come back to this same issue with fancybox 3.
I’d love to know if it should be working before I spend time debugging it.
@amber, that’s exactly what it was for me, too. I’m encouraging my client to switch to a better host, but in the meantime, following Woo’s recommended workaround works.
For me, it was my theme (Thesis 1.8.5). On the upside, I’ve been meaning to get a better theme anyway, and this gives me motivation to make that sooner rather than later. 😉
This post details using IFTTT to do it… it’s not a perfect method, but it is better than nothing (since there really does appear to be no other good options right now).
I’m working on a super-simple plugin to enhance the IFTTT method. Let me know if you’re still looking for a solution!
