Support » Plugin: WP Offload SES Lite » Plugin update has caused it to break

  • eMonkey64

    (@emonkey64)


    I received a plugin an update alert this morning so I ran the update for this plugin (or predecessor).
    After the upgrade I get messages about my AWS keys being wrong and that they are in my wp-config file.
    I don’t believe I added them to wp-config and when I look at wp-config I can’t see any AWS SES keys in there.
    The plugin setting won’t let me enter the keys (fields locked due to wp-config).

    So, I’ve had to disable the plugin and find a replacement.

    I was fairly happy with it but now disappointed that maintenance has broken it.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Delicious Brains Inc.

    (@deliciousbrains)

    Hi,

    Sorry to hear you ran into trouble with the update. Did you have any constants in your wp-config at all? I haven’t seen any other reports of this, and we didn’t run into it into testing, so it’d be interesting to see what caused it.

    eMonkey64

    (@emonkey64)

    Hi Delish,
    Here’s the file:

    <?php
    /**
    * The base configuration for WordPress
    *
    * The wp-config.php creation script uses this file during the
    * installation. You don’t have to use the web site, you can
    * copy this file to “wp-config.php” and fill in the values.
    *
    * This file contains the following configurations:
    *
    * * MySQL settings
    * * Secret keys
    * * Database table prefix
    * * ABSPATH
    *
    * @link https://codex.wordpress.org/Editing_wp-config.php
    *
    * @package WordPress
    */

    // ** MySQL settings – You can get this info from your web host ** //
    /** The name of the database for WordPress */
    define(‘DB_NAME’, ‘XXXXXXX’);

    /** MySQL database username */
    define(‘DB_USER’, ‘XXXXXXX’);

    /** MySQL database password */
    define(‘DB_PASSWORD’, ‘XXXXXXX’);

    /** MySQL hostname */
    define(‘DB_HOST’, ‘XXXXXXX’);

    /** Database Charset to use in creating database tables. */
    define(‘DB_CHARSET’, ‘utf8’);

    /** The Database Collate type. Don’t change this if in doubt. */
    define(‘DB_COLLATE’, ”);

    /**#@+
    * Authentication Unique Keys and Salts.
    *
    * Change these to different unique phrases!
    * You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
    * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
    *
    * @since 2.6.0
    */
    define(‘AUTH_KEY’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);
    define(‘SECURE_AUTH_KEY’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);
    define(‘LOGGED_IN_KEY’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);
    define(‘NONCE_KEY’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);
    define(‘AUTH_SALT’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);
    define(‘SECURE_AUTH_SALT’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);
    define(‘LOGGED_IN_SALT’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);
    define(‘NONCE_SALT’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);

    /**#@-*/

    /**
    * WordPress Database Table prefix.
    *
    * You can have multiple installations in one database if you give each
    * a unique prefix. Only numbers, letters, and underscores please!
    */
    $table_prefix = ‘wp_’;

    /**
    * For developers: WordPress debugging mode.
    *
    * Change this to true to enable the display of notices during development.
    * It is strongly recommended that plugin and theme developers use WP_DEBUG
    * in their development environments.
    *
    * For information on other constants that can be used for debugging,
    * visit the Codex.
    *
    * @link https://codex.wordpress.org/Debugging_in_WordPress
    */
    define(‘WP_DEBUG’, false);

    /* That’s all, stop editing! Happy blogging. */

    define(‘FS_METHOD’, ‘direct’);

    /**
    * The WP_SITEURL and WP_HOME options are configured to access from any hostname or IP address.
    * If you want to access only from an specific domain, you can modify them. For example:
    * define(‘WP_HOME’,’http://example.com&#8217;);
    * define(‘WP_SITEURL’,’http://example.com&#8217;);
    *
    */

    if ( defined( ‘WP_CLI’ ) ) {
    $_SERVER[‘HTTP_HOST’] = ‘localhost’;
    }

    define(‘WP_SITEURL’, ‘http://&#8217; . $_SERVER[‘HTTP_HOST’] . ‘/’);
    define(‘WP_HOME’, ‘http://&#8217; . $_SERVER[‘HTTP_HOST’] . ‘/’);

    /** Absolute path to the WordPress directory. */
    if ( !defined(‘ABSPATH’) )
    define(‘ABSPATH’, dirname(__FILE__) . ‘/’);

    /** Sets up WordPress vars and included files. */
    require_once(ABSPATH . ‘wp-settings.php’);

    define(‘WP_TEMP_DIR’, ‘/opt/bitnami/apps/wordpress/tmp’);

    // Disable pingback.ping xmlrpc method to prevent WordPress from participating in DDoS attacks
    // More info at: https://docs.bitnami.com/?page=apps&name=wordpress&section=how-to-re-enable-the-xml-rpc-pingback-feature

    if ( !defined( ‘WP_CLI’ ) ) {
    // remove x-pingback HTTP header
    add_filter(‘wp_headers’, function($headers) {
    unset($headers[‘X-Pingback’]);
    return $headers;
    });
    // disable pingbacks
    add_filter( ‘xmlrpc_methods’, function( $methods ) {
    unset( $methods[‘pingback.ping’] );
    return $methods;
    });
    add_filter( ‘auto_update_translation’, ‘__return_false’ );
    }

    eMonkey64

    (@emonkey64)

    It’s the Bitnami AMI on AWS.

    Plugin Author Delicious Brains Inc.

    (@deliciousbrains)

    Thanks for the additional info. Unfortunately I’m not seeing anything there that is obviously related to the issue. You mentioned that you’ve already found a replacement plugin, but if you’d like to troubleshoot further the next steps would be to enable debug logging and see if there is anything helpful in the PHP error logs.

    You could do that by changing this line:

    define( 'WP_DEBUG', false );

    To these lines:

    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );

    And then try reloading the plugin page again. Any related errors would likely be logged to the wp-content/debug.log file.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin update has caused it to break’ is closed to new replies.