Emails not sent – at least two bugs in plugin

  • This plugin has several major bugs in it.

    a) Your code is meant to only postpone notifications generated from the front-end, not the backend. It tries to do this by return false in the applies() function in Postponed.php.

    However, with the Gutenberg editor which has been around for a long time now, is_admin() returns false, as changes uses the REST Api. So all notifications in the backend are postponed too.

    b) Your code handles postponed notifications by calling set_transient. It then hooks into the wp_loaded action to fetch all transients that match a certain pattern directly from the database.

    However, transients should never be fetched directly from the database; if you use a host that enables object caching (standard for most big sites), they are stored in the object cache instead. The database call to fetch transients returns no results, and emails are never sent.

    With two fundamental aspects not working, this doesn’t seem like a well-maintained plugin.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter smerriman

    (@smerriman)

    Note, if it helps, this was tested on a default installation on WP Engine, so if it works elsewhere, it definitely doesn’t work there.

    Plugin Author Timo

    (@worschtebrot)

    Thanks for your feedback. `I can agree with you on your points. Sending email is a complex issue and you may encounter different problems on each server. The current implementation was created based on years of experience with this topic, because unfortunately the most obvious way of implementation did not work in all cases. Additionally it has to be considered that this is a free version. In the premium version, some things are more advanced and have additional features.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Emails not sent – at least two bugs in plugin’ is closed to new replies.