Reset Admin Password
|
1 |
UPDATE wp_users SET user_pass=MD5('newpassword123') WHERE ID = 1; |
Create New Admin account
|
1 2 |
mysql> INSERT INTO `wp_users` (`user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_status`, `display_name`) VALUES ('username', MD5('password'), 'friendly-name', '[email protected]', 'http://example.com', '0', 'Your Name'); mysql> SELECT LAST_INSERT_ID() INTO @userid;INSERT INTO `wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, @userid, 'wp_capabilities', 'a:1:{s:13:"administrator";s:1:"1";}'), (NULL, @userid, 'wp_user_level', '10'); |
Show error in case white screen appears
Try adding this line to wp-config.php to see the errors on the page:
|
1 |
define( 'WP_DEBUG', true ); |
Change the site URL
|
1 2 |
mysql> SELECT * FROM wp_options WHERE option_name = 'siteurl' OR option_name = 'home' ; mysql> UPDATE wp_options SET option_value = 'http://staging.mysite.com' WHERE option_name = 'siteurl' OR option_name = 'home' ; |
Disable all plugins
|
1 |
mysql> UPDATE wp_options SET option_value = 'a:0:{}' WHERE option_name = 'active_plugins'; |
Show users and Privileges
|
1 2 3 4 5 6 7 8 9 10 11 |
mysql> SELECT user_login,user_registered,meta_value FROM wp_users INNER JOIN wp_usermeta ON wp_users.id = wp_usermeta.user_id and meta_key = 'wp_capabilities'; +---------------+---------------------+---------------------------------+ | user_login | user_registered | meta_value | +---------------+---------------------+---------------------------------+ | administrator | 2013-12-21 10:36:30 | a:1:{s:13:"administrator";b:1;} | | author | 2014-11-25 15:50:34 | a:1:{s:6:"author";b:1;} | | editor | 2014-11-25 15:51:18 | a:1:{s:6:"editor";b:1;} | | contributor | 2014-11-25 15:51:48 | a:1:{s:11:"contributor";b:1;} | | subscriber | 2014-11-25 15:52:11 | a:1:{s:10:"subscriber";b:1;} | +---------------+---------------------+---------------------------------+ 5 rows in set (0.01 sec) |
Update theme to Twenty Fourteen
|
1 2 |
mysql> UPDATE wp_options SET option_value = 'twentyfourteen' WHERE option_name = 'template' OR option_name = 'stylesheet'; mysql> UPDATE wp_options SET option_value = 'Twenty Fourteen' WHERE option_name = 'current_theme'; |
Administration Over SSL
Add the below lines to the wp-config.php file above the ‘/* That’s all, stop editing! Happy blogging. */’ line
|
1 2 |
define('FORCE_SSL_ADMIN', true); define('FORCE_SSL_LOGIN', true); |
This ensures the login AND the administration is done over SSL
You could also use the below .htaccess:
|
1 2 3 |
RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /(.*)\ HTTP/ [NC] RewriteCond %{HTTPS} !=on [NC] RewriteRule ^/?(wp-admin/|wp-login\.php) https://mysite.com%{REQUEST_URI}%{QUERY_STRING} [R=301,QSA,L] |
Find out how many SQL queries are executed every time a page is loaded.
Add the below to one of the theme files, I usually add to footer.php
|
1 2 3 4 5 6 |
if ( current_user_can( 'manage_options' ) ) { echo $wpdb->num_queries . " SQL queries performed."; } else { // Uncomment the below line to show SQL queries to everybody // echo $wpdb->num_queries . " SQL queries performed."; } |
Here are some configuration parameters you can add to your wp-config.php file for FTP.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
define('FS_METHOD', 'direct'); /* forces the filesystem method. It should only be "direct", "ssh2", "ftpext", or "ftpsockets". Generally, you should only change this if you are experiencing update problems. If you change it and it doesn't help, change it back/remove it. Under most circumstances, setting it to 'ftpsockets' will work if the automatically chosen method does not. (Primary Preference) "direct" forces it to use Direct File I/O requests from within PHP, this is fraught with opening up security issues on poorly configured hosts, This is chosen automatically when appropriate. (Secondary Preference) "ssh2" is to force the usage of the SSH PHP Extension if installed (3rd Preference) "ftpext" is to force the usage of the FTP PHP Extension for FTP Access, and finally (4th Preference) "ftpsockets" utilises the PHP Sockets Class for FTP Access. */ define('FTP_BASE', '/var/www/vhosts/example.com/httpdocs/'); // is the full path to the "base"(ABSPATH) folder of the WordPress installation. define('FTP_CONTENT_DIR', '/var/www/vhosts/example.com/httpdocs/wp-content/'); // is the full path to the wp-content folder of the WordPress installation. define('FTP_PLUGIN_DIR ', '/var/www/vhosts/example.com/httpdocs/plugins/'); // is the full path to the plugins folder of the WordPress installation. define('FTP_PUBKEY', '/var/www/vhosts/example.com/httpdocs/.ssh/id_rsa.pub'); // is the full path to your SSH public key. define('FTP_PRIKEY', '/var/www/vhosts/example.com/httpdocs/.ssh/id_rsa'); // is the full path to your SSH private key. define('FTP_USER', 'FTPusername'); // is the FTP username define('FTP_PASS', 'FTPpassword'); // is the password for the FTP User define('FTP_HOST', 'localhost'); // FTP Host - usually localhost. define('FTP_SSL', false); // This is for "Secure FTP" not for SFTP. |
xmlrpc.php
I’d recommend restricting xmlrpc.php POSTs to only IPs that need it by adding the following rules to the top of your .htaccess file, updating accordingly the line ‘allow from’ with a list of IPs space separated or simply completely remove that line to block its execution:
|
1 2 3 4 5 6 7 8 |
# ---------------------------------------------------- # Block WordPress xmlrpc.php requests <Files xmlrpc.php> order deny,allow deny from all allow from 123.123.123.123 </Files> # ---------------------------------------------------- |