• Resolved evieao

    (@evieao)


    i get this message when i try to install on my server.

    Parse error: syntax error, unexpected ‘.’ in /opt2/home3/ezgsa/public_html/blog/wp-includes/user.php on line 492

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter evieao

    (@evieao)

    sorry about the shortness of the message above. i hit return without formally asking for help. please help!

    thanks,
    evie

    Thread Starter evieao

    (@evieao)

    oh, and i haven’t changed that file at all.

    Have you changed any other files??? Have you tried to de-activate the plugins manually?

    Thread Starter evieao

    (@evieao)

    i changed wp-config. i haven’t done anything with any plug ins. i’ve just followed the instructions for install.

    then you probably made a mistake in wp-config. Try pasting your wp-config changes here but please remove your connection details (username / passwd).

    Thread Starter evieao

    (@evieao)

    <?php
    /**
    * The base configurations of the WordPress.
    *
    * This file has the following configurations: MySQL settings, Table Prefix,
    * Secret Keys, WordPress Language, and ABSPATH. You can find more information by
    * visiting {@link https://codex.www.ads-software.com/Editing_wp-config.php Editing
    * wp-config.php} Codex page. You can get the MySQL settings from your web host.
    *
    * This file is used by the wp-config.php creation script during the
    * installation. You don’t have to use the web site, you can just copy this file
    * to “wp-config.php” and fill in the values.
    *
    * @package WordPress
    */

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

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

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

    /** 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.
    *
    * Change these to different unique phrases!
    * You can generate these using the {@link https://api.www.ads-software.com/secret-key/1.1/ 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’, ‘fld1bJ3,aosrLe[n]hzdq_L2#JMjS)Qqkq7&>l>,2o]|S5V8xhmkb*^U6X9{e1@+’);
    define(‘SECURE_AUTH_KEY’, ‘U9+WQ;9(X]k,37q|cfIUg(}0=lpUzFmrJFV.[I^Y|JccW^5L9|>(5#[4C@K#ppk?’);
    define(‘LOGGED_IN_KEY’, ‘H+)50c+x8l;Jk~I`4K6?1m,!lZYdh)-l6]|}^|b@{Q3 IQ/yRMq}X.7XgXW |nM.’);
    define(‘NONCE_KEY’, ‘!%peANNm;Z,dj}V]hgGvvy@E1y*pOU~#B;tv%/@-,T<8mS>Vz@;Pq,@0tcX+l{‘);
    /**#@-*/

    /**
    * 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 = ‘blog_’;

    /**
    * 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.mo to wp-content/languages and set WPLANG to ‘de’ to enable German
    * language support.
    */
    define (‘WPLANG’, ”);

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

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

    Thread Starter evieao

    (@evieao)

    never mind. i re-downloaded and re-installed and it’s working.

    thanks,
    evie

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘install error’ is closed to new replies.