0

I know this subject has been covered many times here. But despite all the informations I have I am not able to solve the issue ,I require your help :

Warning: Cannot modify header information - headers already sent by (output started at /homepages/3/d885479298/htdocs/clickandbuilds/WordPress/Chrono/wp-config.php:1) in /homepages/3/d885479298/htdocs/clickandbuilds/WordPress/Chrono/wp-includes/pluggable.php on line 1329

THERE IS NO BLANK SPACE BEFORE <?php

WP-config.php

<?php
define('COOKIE_DOMAIN', $_SERVER['HTTP_HOST'] );
define('WP_AUTO_UPDATE_CORE', 'minor');// This setting is required to make sure that WordPress updates can be properly managed in WordPress Toolkit. Remove this line if this WordPress website is not managed by WordPress Toolkit anymore.
/**
 * 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', '*******' );

/** 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', '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',         '4xbvq)bmP)SM2oGAwM^orOI857WtWdy#qsVF!YsG1mWQX&2J859RMk!*woQhwRMW');
define('SECURE_AUTH_KEY',  'y^tjOZy3Xykg()7&Saj3KRQn@NaHZ#h^P#X&y16GNK^sYdL*2guZ&4Eba6eP6Zzc');
define('LOGGED_IN_KEY',    '@T1)6h&44q)8DW5#NG2nZfY#J^VhHt)TCek)CvP9UB1D0Tymn@lN^EP2mWp53@R7');
define('NONCE_KEY',        'ZgHfVglqb45AMT7s%nWMOJ@Np)Z*0B9rnDCcV!&@n3^hxNKq8Q7mZk*EOJvuacTi');
define('AUTH_SALT',        '*w(N6B%dR23GOR*@P#zNw65hVceC@pqZ7!9sZ#&0iE9D1D6w1DS3r%P!78OyXenB');
define('SECURE_AUTH_SALT', ')BhLvKNY9tj95kM^!Z!Tmjd@Z)ixlFy)zt)FbtsP3bZHHemfg(GZ4f02GyN#E&w6');
define('LOGGED_IN_SALT',   'JhUo1jhPntA)yBG2&ewEKsRSC(UZH5A%6n&aVBET9mkEQpLLi6mNch0v(!r0uAgc');
define('NONCE_SALT',       'e#iK9XmQ12529(x!VeV9rZ8K^Z2JAuue@HmL%CCVW1BGZ(KAZOdi#1oWaoVjDr#%');
/**#@-*/

/**
 * 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  = 'lhk9q0p1z0';

/**
 * 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', true);
define('WP_DEBUG', false);
define('WP_DEBUG_DISPLAY', false);*/

/* 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( 'WP_ALLOW_MULTISITE', true );

define ('FS_METHOD', 'direct');
Paul Martinez
  • 562
  • 1
  • 9
  • 19
  • 1
    This is indeed a common question. There can be more things wrong than just a space in the wrong place. See: https://stackoverflow.com/questions/8028957/how-to-fix-headers-already-sent-error-in-php – KIKO Software Nov 25 '21 at 19:03
  • I see blank space before PHP open tag ` – vee Nov 25 '21 at 19:10
  • I was hoping that someone could find out the issue in the wp-config file, as the file is mentionned in the message error...because I am not good enough to find it out by myself. – Paul Martinez Nov 25 '21 at 19:20
  • Your config file looks good now. I don't see any output here but please check the link that @KIKOSoftware said. That is very useful. – vee Nov 25 '21 at 19:33

0 Answers0