Sal Ferrarello

Wow, thanks for your work on the develop branch on GitHub.

Looks good ??

More details in this comment in GitHub.

Hi Andy ??

Based on your explanation, the behavior makes sense.

However in terms of user experience, listing the possible version and then updating to something that does not appear on the list is disconcerting.

I wonder if the message could be modified to avoid this.

i.e. instead of

Currently your site is set to update to version 6.2.3, 6.3-RC1, or 6.3, whichever is released first.

perhaps

Currently your site is set to update to version 6.2.3, 6.3-RCx, or 6.3, whichever is released first.

or

Currently your site is set to update to version 6.2.3, 6.3-RC1, 6.3-RC2, etc. or 6.3, whichever is released first.

or

Currently your site is set to update to version 6.2.3, 6.3-RC1 (or higher) or 6.3, whichever is released first.

I understand if this is a wontfix (and that might be my decision if this were my plugin ??) but in case you want to try adding “(or higher)” I’ve opened a PR at https://github.com/afragen/wordpress-beta-tester/pull/76

Hi Chris,

Thank you for your thoughtful feedback and kind words.

I think you bring up some good points and I’ve opened an issue about this on GitHub (where I track the development of this plugin).

It seems there is a balance here between presenting enough information, keeping the message easily digestible for those users who don’t have email plugin experience, and keeping the message brief.

I’ve started making some notes about how we might change the notice message in the GitHub issue.

Do you have any thoughts about the message text?

Thanks again for the feedback!

– Sal

Hi @wprun,

When emails are logged, the PHP error_log() function is used. The location of the file used by error_log() is going to vary based on how your hosting company is configured.

You could try searching online for your hosting company name along with something like “php error log” or you could contact your hosting company directly and ask them “How do I view my PHP error log?”

Best of luck.

Hi @jodzeee,

“Known Incompatible Plugins” now appears in the list of FAQs.

Thank you for this suggestion.

Hi @jodzeee,

Thank you for this suggestion, making this information more visible to users is an excellent idea.

I’ve opened a GitHub issue to make this change (https://github.com/salcode/stop-emails/issues/21)

Thank you.

Thank you ??

I’ve just release version 1.2.1 of this plugin which eliminates the

PHP Deprecated: class-phpmailer.php is deprecated since version 5.5.0!

message in the error log. This change is backwards compatible and will work on previous versions of WordPress, as well.

Thank you all for your patience and kind words.

Thank you both for your feedback.

While I was aware of the impending deprecation notices, I underestimated the impact it would have on people who use this plugin. I apologize for this.

I am tracking the technical details of the changes I need to make at https://github.com/salcode/stop-emails/issues/18

I have some dedicated time this Friday, 2020-08-28, that I plan to use to resolve this issue and release a new version of the Stop Emails plugin.

Thank you again for your helpful feedback.

Hi @yonisink,

I appreciate you sharing your personal experience and I understand that a filter would be helpful in your situation. Unfortunately, I do still feel that adding this filter would not in the best interest of this project.

While I understand that if the filter were added you would be using it in a responsible manner, I am concerned about the problems it could easily cause when others use it less responsibly.

I suspect your best option is to hide the notice via CSS. If for some reason, that does not work you could modify the source code. Generally, updates for this project are rare and if an update did occur, the plugin would still function properly (but the notice would return).

Hi @yonisink,

Currently, there is no way to disable the “Emails Disabled” alert.

I’ve always thought of this as a plugin to be used during development or troubleshooting rather than a permanent solution. Stopping emails is a pretty drastic measure and has some pretty important implications (for example you can’t recover you password via email with emails turned off).

Because of all of this, I feel rather strongly about not providing a way to remove the “Emails Disabled” alert however I’m certainly open to hearing your thoughts on the topic.

Thanks.

Since there has been no further discussion and I hope it has been answered to your satisfaction, I’m going to close this issue. If you need more information, you can re-open this issue or create a new issue.

Thanks.

Hello,

Yes, I’ve confirmed specifically that Stop Emails works with WordPress v5.2.2 and PHP v7.3.2.

Please note there are some plugins that can interfere with how the Stop Emails plugin works. Some known incompatible plugins are listed at https://github.com/salcode/stop-emails/wiki/Known-Incompatible-Plugins.

I hope this information is helpful. Have a great day.

I will try to figure out another way and maybe publishing the solution here.

Cool, if you do figure out a way to do it, I’d love to hear about it. Thanks.

Hi @darkpollo,

Unfortunately, this plugin does not support whitelisting emails.

This plugin works by replacing the mailer with a non-functional version during the website start up, kind of like replacing a mailbox with a trashcan. Since this replacement happens early in the page request, by the time emails are being sent the replacement has already occurred.

To get the behavior you are describing would require a different approach and in the interest of keeping this plugin simple, I do not plan to change the approach currently being used.

I hope you find a solution for your issue.