Version: 13.1
Revision: 43 Build 13
Encrypt your Wordpress from attackers!
Introduction: This year is nearly Christmas! Therefore, here is a short tutorial that can help publishers enable SSL or Secure Sockets Layer for Wordpress. But, don’t panic! If you don’t know how to install it on your server, then why don’t you ask your hosting provider to install it for you? It’s not that bad…
Advantages: Encrypting your admin pages, it will provide more security for your Wordpress login – session and your control panel. In order to enforce SSL in your admin pages you need to apply some codes into your “wp-config.php” file.
1.] In order to install SSL encryption, you will need to have a dedicated IP address. You can get this from your hosting provider. However, when you have your dedicated IP address, you will need to wait for another 24 hrs for your website to propagate.
Notes: It’s best if you ask the staff to install your SSL encryption. It’s a lot safer and they can install it without a single – fuss! However, if you decide to install it by yourself, there might be a problems like… the page is not appearing correctly or the passport control is warning the users to stay away from your website. So, please be careful and ask the staff!
2.] When you got a dedicated IP address and SSL encryption, you will need to modify your “wp-config.php” file. Here is the following code…
define(’AUTH_KEY’, ‘the auth key’);
define(’SECURE_AUTH_KEY’, ‘the secure auth key’);
define(’LOGGED_IN_KEY’, ‘the logged in key’);
Notes: you will need to generate your personal codes from this link: http://api.wordpress.org/secret-key/1.1/ and insert it into your “wp-config” file.
3.] Now, you’ll need to add these codes and set it as: “TRUE”.
define(’FORCE_SSL_ADMIN’, true); // integrate this if you want your admin site to use SSL
define(’FORCE_SSL_LOGIN’, true); // integrate this if you want the login page to use SSL
Warning: “FORCE_SSL_ADMIN” is a little strict on your plug-ins. So, you will need to double – check your plug-ins, before you try this setting. But, don’t worry about “FORCE_SSL_LOGIN”. This setting will only encrypt your login page so that your login password will be encrypted.
4.] You are done!
Copyrighted By Lair360
Version: 13.2
Revision: 34 Build 11
Five important backup – rules for Wordpress publisher!
Introduction: In this tutorial, we are going to learn the basic about backing up your important ‘Wordpress’ files & folders. This tutorial is pretty easy to read and it should make you aware. This is also like a checklist, to let you backup the important items, just before upgrading to a newer version of ‘Wordpress.’
1.] When you’re prompted to upgrade, you’ll need to disable all of your ‘Plug-ins’. If you ignore this crucial step, there may be some side effects or errors, when you update your Wordpress engines and your SQL database.
2.] Always check your ‘wp-config.php’ file and keep a backup of that file. This file is the hearth of your ‘Wordpress’ engine and it also controls your SQL database and your Administrator’s settings. If you lost this file or the file becomes corrupted, then, your SQL database is completely useless.
If this situation is severe, you will need to consult this problem with your ’server provider’. They might have a backup of your ‘config.php’ file or your database’s password. However, it depends on your hosting – provider – services.
3.] When you’re upgrading, you might want to create a backup of your costume -Wordpress – theme folder. This is only for users who had purchased their own template or had their template completely modified. This tactics is very useful and it will also reduce your time, instead of modifying from scratch.
4.] When you’re are using your FTP server, you will need to create a backup of your ‘.htaccess’ file. This file is also very important, if you have a lot of coding that use to block spammers, evil robots and hot-linkers.
5.] This backup is optional. But, it is useful if you don’t want to re-download or search for the correct plug-ins. All you need to do is look for your ‘plug-in’ folder and compress it as a zip file. That is all…
Simple? I think so…
Copyrighted By Lair360
Version: 12.1b
Revision: 44.2 Build 11
Wordpress – Delete Existing Post Revisions
Introduction: on the 7th of June, 2009, my Wordpress SQL database was accumulating like crazy. However, I didn’t noticed this, right until I checked my Control Panel. After the initial login, I clicked on my server – upload statistic. Then, I checked my SQL Database – load – queries.
Guess what? My database size had about 10 MB of “WP Post Revisions” and the file is like…big!
So, I decided to use these tricks and disable my Wordpress post – revision. The process is very simple…
1.] Log into your Cpanel and backup your “wp-config.php” file. Then, add this “define” strings into your real (original) “config” file. However, you’ll need to place this code above your “database name, users and password.” But, if you add this code below these database strings, there is a high chance that you might delete your database password or username.
—Copy Source Code—
// ** Post Revision ** //
define('WP_POST_REVISIONS', false);
—End Source Code—
2.] When you’re done, please save your “wp-config.php” file and exit.
3.] Close your “FTP file manager” and direct yourself to “phpMyAdmin”.
Then, all you need to do is copy this code into the “Query”.
Warning: be sure to backup your database first, before performing any queries in phpMyAdmin.
—Copy Source Code—
delete x,y,z
from wp_posts x
left join wp_term_relationships y on (x.id = y.object_id)
left join wp_postmeta z on (x.id = z.post_id)
where x.post_type = 'revision'
—End Source Code—
4.] After this process, just relax and keep blogging!
You will also notice that your blog, it will respond faster.
Thanks for the support!
Copyrighted By Lair360
