• Hello everyone, I am faced with the following error:

    Warning: Cannot modify header information - headers already sent by (output started at /home/----/public_html/wp-config.php:1) in /home/-----/public_html/wp-includes/pluggable.php on line 1216

    When I try to log in, it tells me I cannot use cookies.

    Warning: Cannot modify header information - headers already sent by (output started at /home/------/public_html/wp-config.php:1) in /home/------/public_html/wp-login.php on line 421
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/------/public_html/wp-config.php:1) in /home/------/public_html/wp-login.php on line 434
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/------/public_html/wp-config.php:1) in /home/------/public_html/wp-includes/pluggable.php on line 920
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/------/public_html/wp-config.php:1) in /home/------/public_html/wp-includes/pluggable.php on line 921
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/------/public_html/wp-config.php:1) in /home/------/public_html/wp-includes/pluggable.php on line 922

    =============

    How it happened:

    I was having some connectivity issues to www.ads-software.com, found out my SSL certificates needed appropriate installation, but I found that out after I had already upgraded from 4.9.4 to 4.9.5

    I got the connectivity fixed and enjoyed functionality for a night. Woke up to this today.

    Here is a look at my wp-config

    <?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.www.ads-software.com/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', '------');
    /** MySQL database username */
    define('DB_USER', '-------');
    /** MySQL database password */
    define('DB_PASSWORD', '-------');
    /** MySQL hostname */
    define('DB_HOST', '--------');
    /** Database Charset to use in creating database tables. */
    define('DB_CHARSET', 'utf8mb4');
    /** 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.www.ads-software.com/secret-key/1.1/salt/ www.ads-software.com 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',         'lolmodifiedbecauseno');
    define('SECURE_AUTH_KEY',  'lolmodifiedbecauseno');
    define('LOGGED_IN_KEY',    'lolmodifiedbecauseno');
    define('NONCE_KEY',        'lolmodifiedbecauseno');
    define('AUTH_SALT',        'lolmodifiedbecauseno');
    define('SECURE_AUTH_SALT', 'lolmodifiedbecauseno');
    define('LOGGED_IN_SALT',   'lolmodifiedbecauseno');
    define('NONCE_SALT',       'lolmodifiedbecauseno');
    /**#@-*/
    /**
     * 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  = '----_';
    /**
     * 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.www.ads-software.com/Debugging_in_WordPress
     */
    
    define('WP_DEBUG', true);
    /* That's all, stop editing! Happy blogging. */
    /** 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( 'FS_METHOD', 'ftpext' );
    define( 'FTP_BASE', 'home/public_html/' );
    define( 'FTP_CONTENT_DIR', 'home/public_html/wp-content/' );
    define( 'FTP_PLUGIN_DIR ', 'home/public_html/wp-content/plugins/' );;
    define( 'FTP_USER', '-------' );
    define( 'FTP_PASS', '-------' );
    define( 'FTP_HOST', 'heartlandhempinc.com' );
    define( 'FTP_SSL', true );
    
    ?>

    If anyone has any idea as to what I can do to repair this I would be very greatful. I’ve been at it touching files for a few hours now and it’s either try this, or reinstall and re-build.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘wp-config and headers trouble with pluggable.php’ is closed to new replies.