Layerslider gibberish ?

As you please :-)

Kim

Hi Ismael

Thanks, but by doing so I get this error : Notice: Constant WP_DEBUG already defined in /var/www/web/web3198/edsbjerg/wp-config.php on line 92 Notice: Constant WP_DEBUG_DISPLAY already defined in /var/www/web/web3198/edsbjerg/wp-config.php on line 93

And there is no change in the gibberish. But as you say, I will also ask my hosting provider to upgrade.
But if the gibberish has no practical value, then do not use any more time on it. As long is doesn’t are visible to my users :-)

This is the content of the config file :

 <?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', 'weXXXX_3pxy4r');

/** MySQL database username */
define('DB_USER', 'XXXX_3pxy4r');

/** MySQL database password */
define('DB_PASSWORD', 'XXXXXc85j');

/** MySQL hostname */
define('DB_HOST', 'XXXXXXX6');

/** 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',         '06b850784b176300dXXXXXXa698YTkzZjY5ZjJhOGM1NzllZmViZDFiNmY0MDc5ZTJlYjM=');
define('SECURE_AUTH_KEY',  'a24fbf1bd250408XXXXXXdZTZmNmFlYWM1YmRiMjg3YTlhNzEzYTE5ZWRlMzFjODk=');
define('LOGGED_IN_KEY',    'bbaf260c7293c84e3XXXXXXhYTllMmQxY2Q5MjJiZjQ1MDBhNzUwNTUzZWY=');
define('NONCE_KEY',        'bbaf260c7293c84e30988cbdb42512d2M2IzYTBXXXXXXXwNTUzZWY=a24fbf1bd25040821b1346a26a30e67dZTZmNmFlYWM1YmRiMjg3YTlhNzEzYTE5ZWRlMzFjODk=');
#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', 'da_DK');

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

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

• This reply was modified 9 years ago by Edsbjerg.