• I’ve got the plugin all setup up and working fine, however periodically when I log back into wordpress admin area the plugin is displaying a message saying it is inactive and to check configuration! This makes no sense as it works fine up until it turns itself off! I’ve tried ticking the force activation box but it still turns itself off by my next visit. I have an IAM user setup and everything works as it should, it just doesn’t stay active! Any ideas what’s causing this?

Viewing 11 replies - 1 through 11 (of 11 total)
  • Did you ever get an answer to this? I am experiencing the same thing.

    Thread Starter damster

    (@damster)

    No I’ve had no response from the plugin author and I’ve not found a suitable alternative so far. I’m stuck with email that works some of the time which is less than ideal!

    Plugin Contributor Sylvain Deaure

    (@sylvaindeaure)

    Hi,

    Sorry I didn’t see that thread.

    The plugin deactivates when the SES or Mail config changes, or wether another plugin does rewrite the wp_mail() function.

    First thing would be to activate the log function of the plugin, wait for it to deactivate, then look at the log file. If it deactivates itself, there will be a reason in the wp-ses logs.

    Thread Starter damster

    (@damster)

    I’ve switched the logs on and they contain this error

    1484114165 ERROR wp_mail override by another plugin !!
    1484114165 Then deactivating plugin
    1484114165 wp_mail already defined in /home/sitename/public_html/wp-includes/pluggable.php

    I really need to sort this problem out as mail sent through the default WordPress function doesn’t get delivered most of the time which is why I need Amazon SES in the first place!

    • This reply was modified 8 years, 2 months ago by damster.
    Plugin Contributor Sylvain Deaure

    (@sylvaindeaure)

    So, that’s not another plugin trying to rewrite wp_mail, that’s a poorly written plugin that includes or requires pluggable.php
    That breaks all pluggable functions for all other plugins.

    Find out which other plugin you use that mentions “pluggable.php” in the source code, and you’ll find the culprit.

    Nothing I can do on my side, it’s another code that breaks a core WP functionnality.

    Thread Starter damster

    (@damster)

    Is there an easy way of doing this or is it a case of going through the code for each manually?

    Plugin Contributor Sylvain Deaure

    (@sylvaindeaure)

    If you’ve got access to a shell, it’s a grep away.
    Or you can download your plugins directory and do a local search within the files.

    If you don’t know how to do a search within the files,
    You can also use the contact form on the wp-ses.com website, then send me the zip of your plugin directory and I’ll search for you.

    Plugin Contributor Sylvain Deaure

    (@sylvaindeaure)

    Plugin “String Locator” may be of help.

    Thread Starter damster

    (@damster)

    Thanks very much for your help I’ll give it a try ??

    Thread Starter damster

    (@damster)

    I found that two plugins mention pluggable.php in their code, Wordfence and WP Fastest cache. Of the two of them only wordfence uses the mail function (to send alerts) as far as I can tell.

    I have tried disabling the alerts for now to see if this affects the WP SES deactivation issues. I’ll check back here with the result.

    Plugin Contributor Sylvain Deaure

    (@sylvaindeaure)

    In fact, it doesn’t matter wether or not the mail function is used.

    The inclusion of pluggable.php alone kills all pluggable functionnality.
    pluggable.php never shoud be included by a plugin.
    It’s loaded by te WP core at the required level.

    Both these plugins are then potentially breaking several other’s functionnality.

    You can alert the authors of these plugins and ask them to fix.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Plugin switching itself off’ is closed to new replies.