fraughtithrouble

You could easily change the name of this plugin to Accept Payments rather than Accept Donations. The problem is entirely your own. Also, the Stripe interface is impossible. It wants a 25% owner to fill out the form. Some companies have no one with such an ownership level. Then it wants photos of ID without fingers being show. Then it claims it cannot use the webcam on major computer company’s hard ware and using major and commonly used browser interfaces. Stripe’s responsibility, but adding them to your donation plugin just makes it worse. And that is your problem.

I use classic editor only. So your example does not help. However, I find the problem happening whether I use I frame or simply the Rumble url. I presume that in the classic editor, Embed Press embeds both, automatically. I know that a tweet gets the [embed] tags inserted automatically, though in the last 4 months its leaving much too much space below the tweet when text follows the tweet.

And yes, I have purged the cache on my browswer and erased the cookies, so its not a problem of the browswer cache.

I agree with both comments above. The last thing I want as an admin is a plugin trying to establish a NANNY state.

I can confirm that this plugin is not displaying statistics data in the FireFox browswer on all my sites, checked with firefox from two different locations and two different devices.

I uninstalled the + version of this plugin, and reactivated the old version. And the problem went away. I will not revise my rating therefore.

Numerous subscribers report this same error to the admin, that they cannot unsubscribe, But in nearly all cases, they are unsubscribed already when the admin checks the logs in the plugin. However, I think that if there are notifications in the queque they still go out. Still, I have the opposite problem, of subscribers who are unsubscribed not by themselves nor by the admin. Alas this plugin seems abandoned.

I have had the same problem since april, but not only gmail, many …. and I found recently that as of May, somehow, no one with an email which begins with the first half of the alphabet can subscribe…. what is going on with this plugin?

Gotfiero, I am glad someone finally said it. I run nearly a dozen wordpress sites and have been trying to get Gutenburg to at least do what the classic editor could do and more. After 6 months of frustration, I reasonably conclude that the entire concept of block editing was invented by coders to make us hire them to do the 1000 things we could do on our own.

Gutenberg is 100% junk. You would have to take a course to understand how to use it, and then spend 100x more time using it than you could in classic editor. The other block editors are not much better, such as elementor.

The whole concept of blocks is retrograde invented by persons who do not give a bleep about user friendly…

Ok when you find the code, let me know, and this fix should go on the GitHub site for this plugin

Yes, I found that the drop down menu on the page somehow ad the wrong value and when it replaced it, it fixed itself. Thanks. Why only on the drop down menu was I able to fix it and not in the back end panel of the plugin, I cannot understand. As for turning off the SEO patterns, I do not understand what you mean.

I have spoken with my hosting company and I am beginning to think that all the images have disappeared from the database. Pages which call them still have their urls, but no image is imaged when loading the page.

All permissions are granted. Including that one.

When wordfence updated to 7.1.2 it crashed one of my sites, in that it only showed 503 errors to everyone logged in or not. But it did not crash the other of my sites, so with some wise counsel I copies the WF folder on one which was still 7.1.1 and erased the 7.1.2 on the problem site and replaced it with the 7.1.1. Then I turned off automatic updates for the problem site. That solved my problem, however, I want to know when WordFence will fix this problem so I can turn updates back on. I dare not run the site without WF on.

The touchscreen problem occurs both when accessing the theme in latest version of Firefox and Google Chrome.