• I went into my wp-config file to change my SSL settings and after updating the file on my server I started receiving this error –

    Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING in /data/21/2/70/147/2722310/user/2991236/htdocs/WordPress/wp-config.php on line 105

    There is no line 105 in my code and I’ve tried everything but it’s still broken.

    The site is http://www.backcountryrecumbentcycles.com

    Code :

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

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

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

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

    /** TR88575 */
    define(‘FTP_HOST’, ‘localhost’);

    /** 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.ww.wp.xz.cn/secret-key/1.1/salt/ ww.wp.xz.cn 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’, ‘put your unique phrase here’);
    define(‘SECURE_AUTH_KEY’, ‘put your unique phrase here’);
    define(‘LOGGED_IN_KEY’, ‘put your unique phrase here’);
    define(‘NONCE_KEY’, ‘put your unique phrase here’);
    define(‘AUTH_SALT’, ‘put your unique phrase here’);
    define(‘SECURE_AUTH_SALT’, ‘put your unique phrase here’);
    define(‘LOGGED_IN_SALT’, ‘put your unique phrase here’);
    define(‘NONCE_SALT’, ‘put your unique phrase here’);

    /**#@-*/

    /**
    * 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_’;

    /**
    * WordPress Localized Language, defaults to English.
    *
    * Change this to localize WordPress. A corresponding MO file for the chosen
    * language must be installed to wp-content/languages. For example, install
    * de_DE.mo to wp-content/languages and set WPLANG to ‘de_DE’ to enable German
    * language support.
    */
    define(‘WPLANG’, ”);

    /**
    * 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.
    */
    define(‘WP_DEBUG’, 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”);

Viewing 3 replies - 1 through 3 (of 3 total)
  • It is normal to see errors on lines that do not exist.

    What di you change in the file?

    If you used FTP then maybe it failed and id not upload the file all the way.

    One thing I see that is different in the file is that double quites are being used for

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

    This should not matter here but really thats all I am seeing. This error can happen for many reasons but I normally see it when a period (.) is missing when defining a constant

    Thread Starter Sprocketish

    (@sprocketish)

    It was the FTP server! Thanks so much! I was going crazy! haha

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Syntax Error for a Line that Does Not Exist’ is closed to new replies.