SyntaxHighlighter2 WordPress plugin released

SyntaxHighlighter2 WordPress plugin was released yesterday on WordPress Extend plugin repository. SyntaxHighlighter2 allows you to easily post syntax highlighted code all without loosing it's formatting or making an manual changes. Main addition is upgrade to SyntaxHighlighter JavaScript 2.0 by Alex Gorbatchev. Also in this release the web master/blogger is given the ability to choose from 6 themes for the SyntaxHighlighter.

If you already using SyntaxHighlighter WordPress plugin and using XHTML, you should upgrade to SyntaxHighlighter2 because SyntaxHighlighter uses invalid XHTML. Bellow you will find the sample WordPress configuration file with SyntaxHighlighter2 :) .

<?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’, ‘putyourdbnamehere’);

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

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

/** MySQL hostname */ define(‘DB_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. *
• 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} *
• @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’, ‘’);

/* 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’); ?> <?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’, ‘putyourdbnamehere’);

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

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

/** MySQL hostname */ define(‘DB_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. *
• 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} *
• @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’, ‘’);

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