Sal Ferrarello

Hi @darkpolo,

I just tested WP Mail SMTP by WPForms and it is not compatible with this plugin.

I’ve added WP Mail SMTP by WPForms to the list of incompatible plugins.

@specialk

Disable Gutenberg v1.3.1 from your download link seems to have corrected the problem.

Recreating the Problem (using Disable Gutenberg v1.3.0)

I’m using Local by Flywheel and below are my steps to recreate the problem on a fresh install.

Create Local by Flywheel new install
disablegutenberg.test
Preferred Setup (PHP 7.1.7, nginx + Varnish, MySQL 5.6)
Not multisite

Log into website (https://disablegutenberg.test/), which is running WordPress 4.9.8

Visit https://disablegutenberg.test/hello-world/, the WP Admin Bar is displaying properly (with the “Edit Post” link)

Add new plugin via web interface (https://disablegutenberg.test/wp-admin/plugin-install.php) (version 1.3)
Install and activate “Disable Gutenberg”

Return to https://disablegutenberg.test/hello-world/, the WP Admin Bar is missing the “Edit Post” link and this
warning appears in the content.

(as noted above Disable Gutenberg v1.3.1 has corrected this issue)

@specialk

– Complete Disable
– Disable Nag

are the only two checked options.

I tried using “Restore default plugin options” and I’m still getting the same behavior.

FYI, I’m running PHP version: 7.0.3

@specialk

I’ve got a local install with theme Twenty Sixteen and the only plugin active is Disable Gutenberg version 1.3.

With this setup the “Edit Post” link is missing from the black WP Admin Bar across the top of the screen.

Deactivating “Disable Gutenberg”, restores the “Edit Post” link.

I’m getting this warning in my error logs.

> Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘disable_gutenberg_get_edit_post_link’ not found or invalid function name in /app/public/wp-includes/class-wp-hook.php on line 288

Hi @darkpollo,

Thank you for your understanding and I appreciate your kind words in the review you left.

I do want to clarify, I don’t think the Sendgrid plugin is doing anything wrong. Unfortunately, the way they are modifying WordPress’s email sending for Sendgrid is incompatible with the way I’m modifying WordPress’s email sending to stop the emails but I wouldn’t call their changes wrong.

I’m going to mark this topic as closed but please feel free to re-open it or open another issue if you have further questions.

Thanks again and have a great day.

Hi @darkpollo,

Thanks for this message. The Stop Emails plugin works by overriding the WordPress mail sending code. Other plugins, like SendGrid, also override the mail sending code but so they can send the message instead. Their overrides allow the messages to be sent through their service despite the presence of the Stop Emails plugin.

Based on your report, I’ve added **SendGrid** to the list of Known Incompatible Plugins.

While I’ve considered adding specific code to target these incompatible plugins one-by-one, ultimately I’ve decided that would be a larger time investment than I can give to this plugin.

If you or someone else has an improved way to prevent emails from sending (without addressing each other plugin individually), I’d love to hear about it.

In summary, I like the idea of stopping emails for these incompatible plugins but I’m concerned trying to addressing them individually would turn into a never-ending game of Whac-a-mole.

I’m sorry I don’t have a more satisfying reply to your request.

@azaozz

Thank you for providing this plugin. While Gutenberg is undoubtably the future of WordPress, I do appreciate the ability to ease into the transition by using this plugin.

Above you mention,

Was considering to change it to replace the editor by default, but for now this doesn’t make sense (the user can simply deactivate the Gutenberg plugin). After the merge the default will probably be changed.

I’d like to suggest modifying this default to replace sooner rather than later. If someone installs this plugin now in preparation for the merge, their option will be set to no-replace.

Even if the default changes in the future, these legacy installs will still have a value of no-replace. (I’m assuming future updates will not modify the existing option).

Those who install the plugin later, will have the new default (replace).

Since the impact of this plugin is not visible until Gutenberg is merged (or the Gutenberg plugin is activated), I suspect many of these sites will be unaware of their setting until the merge occurs.

The result will be that when Gutenberg is merged, the plugin behavior will vary based on when the plugin was first installed, which will be quite confusing.

Would you please change the default value to replace to help avoid this issue.

Thank you again for providing this plugin to our community.

Thanks for checking this out @alexanderfoxc.

I’ve updated this information on the Stop Emails project issue.

Have a great day.

Hi expertoswp,

This is a great question and it looks like @alexanderfoxc has addressed it at https://www.ads-software.com/support/topic/does-this-work-with-the-plugin-stop-emails/.

They write:

just tested and looks like Stop Emails is working as expected with Easy WP SMTP – it blocks outgoing emails when enabled. So you can feel yourself free to use it.

Thanks.

Note: This information is also noted in the project repository at https://github.com/salcode/stop-emails/issues/13

Hi expertoswp,

That is a good question that I do not know the answer to. I’ve opened an issue for this on the Stop Emails project on GitHub.

https://github.com/salcode/stop-emails/issues/13

Thank you for your kind review – you made my day.

I’m glad to hear you’re finding this plugin useful.

Hi Kevin and Tracy ??,

Upon checking today, I am no longer seeing the notice. For reference, I’m running on Siteground’s GoGeek plan, using their built-in caching but no additional caching plugin.

If I experience the problem again, I’ll try clearing the cache.

Thanks for a great plugin.

Thanks for the kind review. I wrote this code to deal with my own problem, which was similar to the one you described. Your message makes me glad I decided to share it with others.

Thanks again for the kind words, you made my day.

– Sal

Hi queeneve,

Since the email delay seems to be unrelated to this plugin and there hasn’t been any recent activity on this thread, I’m going to mark this topic as resolved.

If anything occurs that seems to indicate this plugin is involved in the delay, we can certainly re-open this topic or create a new one.

I hope your new year is going well.

All the best.

When emails are sent they travel through different servers on their way to their destination. Each of these servers adds information in the header fields (which are often hidden by default). This article https://www.labnol.org/internet/email-delivery-delayed/25922/ discusses how to view the the header fields and get information from them.

Using this, you may be able to determine where the slow down occurred. Once you have that information, you may be able to contact your host or email provider with the information and see if they can provide any further information.

Best of luck.