Forum Moderators: rogerd & travelin cat
I don't suppose you have Google toolbar installed?
We see a lot of crappy requests on most of our sites, looking for things like FCkeditor, wp-admin, admin folders. So if we are being targeted they may getting our aliases from DNS and trying each one.
(and then mess with plugins, settings, etc.) The hard part is not having the same path settings for the db name, username and logins, so that gets changed in your wp-config.php file.
// We let test sites override basic connection settings with a local settings file
// with a path based on the current user so that we don't accidentally find other
// files on the server.
// If we don't find a file, we fall back on the settings that work on the live site. So
// that we don't accidentally bring down the live site if there's a problem
//
// Config file must be in a directory one level up from server's DOCUMENT_ROOT
$config_file = dirname($_SERVER['DOCUMENT_ROOT']) . '/wpconfig/wp-config.example.php';
if (file_exists($config_file)) {
include($config_file);
}
else {
define('WP_HOME','http://example.com');
define('WP_SITEURL','http://example.com');
define('DB_NAME', 'dbname');
define('DB_USER', 'dbuser');
define('DB_PASSWORD', 'password');
define('DB_HOST', 'localhost');
}
define('WP_HOME','http://test1.example.com');
define('WP_SITEURL','http://test1.example.com');
define('DB_NAME', 'testdb');
define('DB_USER', 'testuser');
define('DB_PASSWORD', 'testpassword');
define('DB_HOST', 'localhost');
blog CMS that is flexible enough to be used as a general CMS, but it is being used as a web framework
That's the standard serialization format used with the PHP serialize() unserialize() functions, but it's not a very robust way to store data.
So it's not the serialisation format that's odd, it's that WP is not really set up to have a robust pluggable architecture, so developers can fall back on just serializing data and throwing it into the wp_options table as a single DB value.