• PHP 4.3.9
• MySQL Server 4.1.20
• HTTPD 2.0.52

Of course you could search the web for the latest RPMS, find all the dependencies and install everything with the package manager. But there an easier trick than that. It's called the CentOSPlus Repository.

I won't go into details about this repository, you can find more information here.

Enabling The CentOSPlus Repository

I am assuming at this point that you've tested all your PHP scripts on PHP5 and that you've backed up all your MySQL databases. You did it, right? Ok proceed then.

This is quite simple. All you have to do is to edit /etc/yum.repos.d/CentOS-Base.repo with your favorite text editor (no word processor!). Find the following section:

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5

Now simply set the enabled parameter to 1. Save the file and exit the editor.

When you're done, you can update Yum before going further (optional):

# yum update yum

After that you can update PHP, Apache and MySQL:

# yum update php mysql apache

When you're done, you can either reboot your server or restart httpd and mysqld:

# service httpd restart
# service mysqld restart

Once the upgrade is finished, you should now have the following versions installed:

• PHP 5.1.6
• MySQL Server 5.0.54
• HTTPD 2.0.59

Good luck!

This short tutorial will show you how to access your website's statistics without logging into cPanel.

1. Grab yourself a copy of AwStats over at http://sourceforge.net/project/showfiles.php?group_id=13764

2. Unzip all the content from the archive in a temporary folder on your hard drive.

3. Using your favorite FTP client, connect to your web server.

4. Create a directory named awstats into /public_html/cgi-bin.

5. Upload all the content from the /wwwroot/cgi-bin folder you've extracted (not the folder itself!) to your web server into /public_html/cgi-bin/awstats

6. Still using your FTP client, create two directories on your webserver:

• /public_html/images
• /public_html/images/awstats

7. Upload the content from the /wwwroot/icon folder to your web server into /public_html/images/awstats

8. Download /tmp/awstats/awstats.[your-website-name].conf from your web server to a temporary folder on your hard drive.

9. Upload the file you've just downloaded back on your web server but this time into /public_html/cgi-bin/awstats

At this point you should be able to access your website's statistics at http://www.yourdomain.com/cgi-bin/awstats/awstats.pl?config=yourdomain.com but the fact that it's publicly available to anyone is a security concern.

Here's how to protect your statistics:

1. Log into cPanel and click on the Password Protect Directories icon.

2. Browse to the /public_html/cgi-bin directory and select the awstats folder. You should now see this page:

3. Make sure you're about to protect the right directory. You can find this information at the upper left corner of the screen. Of course I've hidden the directory name from my own web server.

4. Check the Directory requires a password to access via the web checkbox and enter a name for the resource to protect. Click on Save.

5. Add the user accounts you want to give access to in the section below. When you're done adding users you can close cPanel.

This way the visitors will be prompted to enter a user name and password when trying to access AwStats.

You might encouter some problems if you have Wordpress installed at the root of your web server (i.e. directly into /public_html). This is caused by the rewrite rules in the .htaccess file. If that's the case, a quick and easy workaround would be to create a subdomain and use it to access AwStats (example: awstats.yourdomain.com/cgi-bin/awstats.pl).

Step 1 - Create your SPF record

Visit openspf.org and use their SPF wizard to create your SPF record.

Here is the record for hosthow.com:

"v=spf1 a mx mx:viper.hosthowservers.com ~all"

When a client tries to send email from hosthow.com, it looks for the SPF record, which in hosthow.com's case means:

v=spf1 declares that the record is SPF version 1

a means that all A records for the domain hosthow.com can send mail

mx means that all MX records for hosthow.com are checked, and all their A records are checked. Remember that when you are using a 3rd Party mail service such as Google Apps Gmail, you need to include their MX server(s) here.

mx:viper.hosthowservers.com means that all of viper.hosthowservers.com's MX records are checked, and their A records checked. This is because the hosthow.com site sends automatic emails such as the website signup confirmations, and they are sent by viper.hosthowservers.com

~all means that this SPF record lists all servers that send mail for hosthow.com - and the tilde ~ means that if a server is not listed here but is trying to send mail, it should be a "soft" fail, meaning it won't be rejected completely but may be marked with a higher chance of being SPAM. You should use this so that if there is a legitimate server problem on your send, your mail is not automatically rejected.

Step 2 - Add your SPF record to the domain's zone file

Log into WHM and click the “DNS Functions” icon. Then, select “Edit DNS Zone”.

On the right, click on the domain in question, and click “Edit”. The DNS zone page will open. Scroll all the way down to the bottom to "Add New Entries Below this Line", where you can enter your SPF record:

Remember the intentional period "." at the end of hosthow.com - this is required, and select TXT from the drop-down menu. Also note that the SPF record is enclosed in quotes.

Click "Save" to make the change live.

Step 3 - Test your SPF record

There are a few ways to test your SPF record. One is to use OpenSPF's Why page, an another is to check the headers of the emails that are being received. To view the headers of an email, you need to "View Source" in Outlook for example, or "View Original Message" in Gmail.

You should see an SPF line, and if it was successful it will be similar to this:

Received-SPF: pass (google.com: domain of wordpress@hosthow.com designates 72.52.252.76 as permitted sender) client-ip=72.52.252.76;

Now all you need to do is look forward to less SPAM!

You will need: Adobe Flash Professional

Step 1 - Download the latest version of sIFR

Visit the sIFR website for the latest version and download to your computer. Extract the .zip file and look for the the sifr.fla file.

Step 2 - Choose your font and edit sifr.fla

You need to manually create special .swf (Flash) files for each of the fonts you plan to use for sIFR. In this example I will be using Gill Sans MT. Open the sifr.fla file and double-click on the invisible text box in the centre of the window.

This will open the holder Movie Clip with the above text box showing. Select this text box by clicking it, and in the Properties panel, change the font to the one you want to use. If the Properties panel isn't visible, show it by pressing Ctrl+F3.

Step 3 - Export your sIFR flash file

Click File > Export > Export Movie... and save your .swf file as gillsansmt.swf, for example.

Make sure when you see the export settings dialog, to choose "Flash Player 6" if it's not selected already. All the remaining settings can be left as they are.

After this you can close the sifr.fla file without saving.

Step 4 - Add the sIFR CSS and JavaScript to your page

You'll need to include the sIFR CSS files and the sifr.js file in the <head> part of the page that will contain the sIFR text.

<link href="sIFR-print.css" rel="stylesheet" type="text/css" media="print" />
<link href="sIFR-screen.css" rel="stylesheet" type="text/css" media="screen" />
<script src="sifr.js" type="text/javascript"></script>

You should correctly format your existing text so that it will look right when viewed with a browser that doesn't support sIFR. I have formatted the <h3> element below in Verdana.

Step 5 - Add the final sIFR commands

The final commands you need to add are the sIFR.replaceElement JavaScript commands at the end of your HTML. For this one element, the following code is added just before the </body> tag (in tags):

sIFR.replaceElement("h3", "./gillsansmt.swf", named({sColor : "#000"}));

This tells sIFR to replace <h3> text with our newly-created gillsansmt.swf. The last command, sColor sets the color of the text in hex. There are many more options, described in detail on the sIFR website.

Step 6 - Try out your new sIFR text

Test your page in your favorite browser, and the result should be something like this:

Be sure to also test in other browsers to make sure your page will look as you want it to, to the majority of your visitors.

Step 1 - Download the latest version of Pixelpost

Visit pixelpost.org website to download the latest version. Here you'll also be able see a demo of the software and check out the various tools and extensions that are available.

Step 2 - Unzip and upload to your web server

f you are using Windows XP, right-click on the Pixelpost file and select "Extract all.." and click Next to extract the files.

You may want to have the photo blog as your main website (ie. www.yourwebsite.com), in which case you would just upload all the files directly to the public_html folder. Alternatively you can have Pixelpost work as an addition to your site, like www.yourwebsite.com/photo. Create the directory if need be, and upload the whole lot to your web server.

Step 3 - Change permissions for folders

Because Pixelpost will be managing your images once you have uploaded them, you'll need to set the permissions (known as CHMOD) on the images and thumbnails folders so they can be written by the software. To do this, in your FTP software right-click the folder and look for "CHMOD" or "Permissions".

Then in the window that appears, you'll need to type 777 in the box, which sets read, write, and execute permissions for all.

Step 4 - Set up a MySQL database for Pixelpost

This is another step that the install program can't do for you. For full details on how to set up a MySQL database, see the How-To Setting up a MySQL database and accessing it with phpMyAdmin

I have set up the database as follows, with ALL privileges because Pixelpost needs to create/drop tables during setup:

Step 5 - Run the Pixelpost install script

Handily, there is a step-by-step wizard for installing the rest and checking your settings. Simply open your web browser and go to www.yourwebsite.com/(photo blog folder, if any)/admin/install.php

All should run smoothly, but I came across an error on the "Requirements" page that said that the GD image library was missing. To fix this, I recompiled PHP with the GD library using the "Apache Update" feature in Web Host Manager

Once you're past the requirements page, you're home free and can customize the various settings and options for using Pixelpost. Happy photoblogging!

The downside to FXP is that it can be a security risk when enabled, commonly used for illegal software transfers across the Internet. Therefore there may be a couple of extra steps to enable FXP on your web server, as by default it is disabled on FTP server software.

Step 1 - Determine the status of FXP on your servers

Most FTP clients show you the raw commands as they are sent to the server, especially when logging in. Look for the "Transfer Window" or "Log Window" on your FTP client. This is what is shown when logging into hosthow.com:

[R] Connecting to hosthow.com -> DNS=hosthow.com IP=72.52.252.78 PORT=21
[R] Connected to hosthow.com
[R] 220---------- Welcome to Pure-FTPd [TLS] ----------
[R] 220-You are user number 1 of 50 allowed.
[R] 220-Local time is now 08:27. Server port: 21.
[R] 220 You will be disconnected after 15 minutes of inactivity.
[R] USER how
[R] 331 User how OK. Password required
[R] PASS (hidden)
[R] 230-This server supports FXP transfers
[R] 230 OK. Current restricted directory is /

The items in bold are the key ones we are looking for: Pure-FTPd is the FTP server software, and the second item tells us that FXP is supported (which means it is enabled).

Step 2 - Enable FXP on both FTP servers, if needed

If you can't see the line that indicated that FXP is enabled, visit the website of your FTP server for details on enabling it. In the case of PureFTPd, you need to change the line "AllowUserFXP" to "Yes" in pure-ftpd.conf

After any changes to settings like these, you'll need to restart your FTP server, and while in the shell you can type the following to do so:

service pure-ftpd restart

or you can use the Restart Services option in WHM:

Remember that FXP must be enabled on both servers in order to work properly.

Step 3 - Log into both FTP servers and prepare to transfer files

Because of its insecure nature, many FTP severs will only do FXP using a secure (SSL or TLS) connection. To enable this, go to the "Site Manager" in your FTP program and change the settings for both the FTP connections.

Once this is done, you need to log into both servers at the same time. In the FTP program FlashFXP, this is shown with one site on each side of the program window.

Step 4 - Simply drag and drop to start your FXP transfer

In most programs you'll only have to drag and drop the file(s) to the other site's window. Sometimes you may need to right-click and select "Site to Site Transfer".

Your logs will look something like this:

[R] CWD /server2
[R] 250 CWD command successful.
[R] PWD
[R] 257 "/server2" is current directory.
[R] PROT C
[R] 200 Protection set to Clear
[L] PASV
[L] 227 Entering Passive Mode (208,36,222,4,224,119)
[R] PORT 208,36,222,4,224,119
[R] 200 PORT command successful.
[R] STOR index.htm
[R] 150 Opening ASCII mode data connection for index.htm.
[L] RETR index.htm
[L] 150 Accepted data connection
[L] 226-File successfully transferred
[L] 226 0.011 seconds (measured here), 78.84 Kbytes per second
Transferred: index.htm 897 bytes in 0.52 seconds (1.7 KB/s)

The [R] and [L] are left and right windows - you can see one side is RETReaving the file, and the other is STORing it.

Remember: You have to keep your FTP program for the entire transfer! This is Site to Site, but your computer is executing the commands to transfer the files.

Step 1 - Log into cPanel and select MySQL Databases

When you log in to cPanel, you should see a breakdown of your hosting package on the page. Make sure you have the ability to add new databases in the Databases section.

Depending on your version of cPanel and theme in use, this may be shown with an icon like here, or a simple text link.

Step 2 - Create a new Database

Strictly speaking, MySQL is the database engine which can run multiple databases at the same time, so the same copy of MySQL runs no matter how many databases there are. Very often it's easier to create a separate database for each application or system you are using, eg. one for your phpBB Forum, and another for your WordPress Blog. This reduces the possibility of conflicting table names, and makes it easier to remove certain software from your website by simply deleting (or "dropping" in MySQL speak) the whole database.

Enter a descriptive name for your new database:

Step 3 - Create a new "database user"

In the next section, choose a username and a secure password. Note that the system may add your hosting username to the beginning, so keep it short.

Step 4 - Assign database privileges

A database can have different users that have varying privileges. Best practice is to give only the minimal permissions to a user/script that they need to function correctly, so that if there is a security breach those credentials can't be used to compromise the database. Here I have selected SELECT, INSERT, UPDATE, DELETE - these are the basic commands needed in most day-to-day operations. Being cautious like this also helps prevent bits of the database being deleted accidentally! After checking the correct boxes, click "Add User to Database".

Step 5 - Try accessing the database with phpMyAdmin

phpMyAdmin is a great tool included in cPanel that lets you view and edit your database directly. Normally you'd use phpMyAdmin to set up your tables and check that everything is running smoothly. Click the link at the bottom of the screen, or the phpMyAdmin icon in the main cPanel menu (versions differ). You should see the following:

You can see that the hosthow_events table appears on the left with (0) by it - which means no tables have been created. You will now be able to use the username and password in any script or program that is using MySQL, and the host localhost in this case, indicated after the @ sign in the figure above.

Spammers have become wise to sites that use a "web form" to collect information, like "Comment" forms on YouTube. They use programs to send fake submissions using these forms, usually full of links to undesirable websites. This tutorial will show you how to eliminate SPAM using a clever version of the CAPTCHA system.

CAPTCHA stands for Completely Automated Turing Test To Tell Computers and Humans Apart - it's the image of jumbled and obscured letters you have to enter before buying your tickets on TicketMaster. Making it very difficult for a computer to "read" what's in an image, CAPTCHA ensures that only a human can use a form or system where the image is present.

Step 1 - Sign up for reCAPTCHA

reCAPTCHA is a cool version of this system that puts the entries of the obscured words to good use - they are used to digitize old books that computers couldn't recognize. Sign up for free at http://recaptcha.net/whyrecaptcha.html

Registering adds an extra level of security, meaning that the CAPTCHA image can only be shown on your website, and not by others trying to mass solve CAPTCHAs (yes, that's right)

Step 2 - Get the relevant reCAPTCHA API or Plugin

reCAPTCHA provides easy-to-use plugins for various website systems, like WordPress, Moveable Type, MediaWiki, phpBB, Joomla and more. Go to the reCAPTCHA plugins page to see if they have a plugin for your system.

If they don't, you can still manually add reCAPTCHA to your PHP-based website. Download the reCAPTCHA library for PHP from Google Code as you will need to include recaptchalib.php in the relevant PHP pages.

Step 3 - Add the code to your existing system

The example code included with the reCAPTCHA library is good, but only applies if you are "post"-ing a form to the current page. Very often you'll be posting to a new page, for example from register.php which contains your form, and register_complete.php which deals with your information and might send a confirmation email. You'll need to add code to both pages to ensure the reCAPTCHA is checked properly.

On the page containing the form, in this case register.php, add the following code where you want the reCAPTCHA box to appear:

require_once('recaptchalib.php');

$publickey = "KEY_HERE";
$privatekey = "KEY_HERE";

echo recaptcha_get_html($publickey);

Replace KEY_HERE with the keys you got in Step 1. Then on your receiving page, add the following BEFORE your other code. This is because we will be sending people back to the original page using header() which only works before anything had been sent to the browser.

require_once('recaptchalib.php');

$publickey = "KEY_HERE";
$privatekey = "KEY_HERE";

# the response from reCAPTCHA
$resp = null;
# the error code from reCAPTCHA, if any
$error = null;

$resp = recaptcha_check_answer ($privatekey,
$_SERVER["REMOTE_ADDR"],
$_POST["recaptcha_challenge_field"],
$_POST["recaptcha_response_field"]);

if ($resp->is_valid) {
	// Do nothing here, but continue with the rest of the page
}
else {
	# set the error code so that we can display it
	$error = $resp->error;
	header("Location: register.php?error=".$error);
	exit();
}

Notice that there's the error appended to the URL in the header() section. To display the error and let your users know that the CAPTCHA was wrong, you'll need to add one last bit of code on the first page in the appropriate place:

if ($_REQUEST['error']) {
	echo "Please check the validation image";
}

You could show this in red, or highlighted in a box to draw attention.

Step 4 - Test your form!

It always pays to check and double-check, making sure that there aren't security holes in your code. If all has gone to plan, you shouldn't have any nasty spam to deal with!

A .htaccess file is a small text file that has many uses, and is placed in directories on your webserver. Often, FTP clients have trouble transferring these files, so cPanel has a convenient function for adding password protection to your site with .htaccess - here's how.

Step 1 - Select "Password Protect Directories" in cPanel

Log in to cPanel, and select "Password Protected Directories" from the options. In newer cPanel versions it's located in the "Security" section.

You may see the screen below, asking where you want to start when looking for which directory you want to protect. Choose the top option, "Web Root". This starts at public_html/ aka www.yourdomain.com/

Step 2 - Choose the directory to protect

If you want to prevent anyone from accessing anything on your site (if your website is in test mode, for example), choose "/" - which is the root of your website. Anyone trying to access something at www.yourdomain.com will be asked for a password. Otherwise, use the folders to navigate to the directory containing your private files.

Step 3 - Choose a "login message"

cPanel calls this "Name the protected directory" but basically it's a little message that will be shown along with the Username/Password box, when people try to access the directory in question. This could be "Keep Out!" or simply "Please enter your username and password"

Step 4 - Set username and password information

Further down the page, you'll see a place to enter a username and password for the directory. Note that it is possible to have more than one username and password that you can distribute to your users. This is useful as their username will show up in your access logs and statistics, should you wish to track it.

Click "Add/Modify Authorized User", and you're all set! Be sure to test it!

The majority of web browsers have support for gzip compression, which compresses the web page between the server and the browser, with virtually no extra processing power needed on the client side.

If you are running a PHP-enabled web server, place this line of code at the top of your PHP pages:

ob_start("ob_gzhandler");

Bingo! Faster loading pages. Remember that this only applies to the final page that gets delivered to the browser, so if you are calling any external scripts or .css files, these won't get compressed.

Check out your before and after page sizes at the Web Page Analyzer.

Contrary to popular belief, SSL certificates are quite straightforward and can even be fun! In this tutorial you'll learn how to set up SSL on your domain from start to finish.

Step 1 - Choose your SSL domain

If you are purchasing a basic "single root" SSL certificate (usually the cheapest), make sure you choose a domain that will cover all types of secure transactions that you will perform on your site. Once you have purchased the certificate, the domain can't be changed.

You may need to secure your login system, and choose login.mydomain.com, but you may later open an eCommerce store where the domain may not be appropriate or could be confusing to your customers. Often, choosing secure.mydomain.com is the best option that covers everything.

Step 2 - Generate your CSR and Private Key

Thankfully, the latest version of WHM makes this a lot easier than it used to be. Log in, and select "SSL/TLS" from the menu. Then select "Generate a SSL Certificate & Signing Request".

On the next screen, enter the relevant information that will be used to create your certificate. Make sure that the email address you use at the bottom is one that will still be available a year or two down the line. For "Company Division" you may want to enter "Sales" or "Customer Service", depending on your company. Finally, the password will be needed should you wish to reinstall the certificate on another server, so don't forget it!

Now go and check your email for the 2 pieces of information you'll need in Step 3.

Step 3 - Choose an SSL Provider and buy your certificate

Important: Protect your Private Key and do not give it to anyone! This is what keeps your website secure.

There are many certificate providers to choose from, and in this example we will be using RapidSSL.

Select the "Buy Now" link next to the certificate you require. Normally you shouldn't need the extra "support" options, but I guess it's there if you need it!

On the next page you can change how many years you wish to pay for, if you want any kind of insurances (I'm choosing none), and how many servers (in this case, 1).

Click "Continue" and on the next page, copy-and-paste the "Certificate Signing Request" from your email, into the space provided. Be sure to include the top and bottom "BEGIN" and "END" lines. The next page will confirm your details, and domain name (check for typos!)

Step 4 - Authorize your certificate via email and phone

In the next step of the purchase process, you will be presented with a list of email addresses suitable to authorize your certificate. These will include the domain's admin and technical contacts, as well as various addresses @yourdomain.com.

Choose one that either you or your client has access to, and click Continue.

Now the fun part! Enter your phone number, and the certificate provider's automated system will call you and ask for the number on screen. When you click "Call Now", you know they're calling, but remember to say "Hello" when you answer!

After the telephone process is over, an email will be sent to the address you chose earlier in this step. All that needs to be done now is the link in the email has to be clicked and "Approved" by you or the client.

Step 5 - Install your new Certificate on the server

Once you have paid for the certificate online, you will receive yet another email that will contain the SSL Certificate itself.

Back in WHM, select the "Install" option from the "SSL/TLS" menu this time. Paste in the SSL Certificate in the top box, and the Private Key from Step 2 in the bottom box.

"User" is the username of the account on your server that will be hosting the domain. You will also need the IP address of the domain, which can be found on the "List Accounts" page.

Note: You can only have 1 certificate per IP address, so if you need to have more than one secure domain and your hosting is shared, you'll need to get an extra IP address. These are usually available from your hosting provider or datacenter.

Step 6 - Test your new SSL secured domain

Remember to use https:// when accessing your secure domain. If all has gone to plan, you should see the little yellow padlock icon in the address bar or bottom right hand corner of your browser.

This how-to will show you how to make the transition to Google Apps’ Gmail service, smoothly and with minimal disruption to your clients’ email. These instructions also apply to any other 3rd party email service.

Step 1 - Sign up for Google Apps and set up email accounts

If you or your client have not already done so, sign up for Google Apps at www.google.com/a

Once you have completed the setup, click on “User Accounts” to set up the email addresses that will be used (ie. Those that are already in use on the existing server.) This will ensure that no email is lost in the process.

Step 2 - Log into WHM and go to “DNS Functions”

Depending on your web host, these kind of changes must usually be made via WHM (Web Host Manager). Log into WHM and click the “DNS Functions” icon. Then, select “Edit DNS Zone” - NOT “Edit MX Entry”. This is because the “Edit MX Entry” Function will not show the complete set of existing MX records.

Step 3 - Select your domain to edit the DNS zone

On the right, click on the domain in question, and click “Edit”. The DNS zone page will open. Scroll down and look for the MX line.

MX or Mail Exchanger records tell email servers where to send email for a particular domain. They are only concerned with incoming mail. In the example above, the default is to allow the server the domain is hosted on to handle the incoming mail - hence the domain hosthow.com is on both sides, the right hand side being the server to handle mail. Notice the extra period after the domain names - this is not a mistake! This is known as a fully qualified domain name (FQDN).

Step 4 - Carefully update the MX records to Google’s mail servers

Back in Google Apps, click “Activate Email” to view the list of mail servers as shown here.

First, edit the existing entry zero, and replace it with Google’s top entry, like this:

Then, scroll to the bottom of the page to add the remaining MX entries. Remember to select “MX” from the drop-down list, and don’t forget the “.” period at the end of each domain!

Step 5 - Save, and activate your new mail service!

Click “Save” at the bottom of the window. You’ll see a message saying “Bind reloaded …” - this means it has worked. Pop back to Google Apps, and select “I’ve Completed These Steps” - and Google will then check that you’ve set up the MX records correctly. Within a few minutes, you’ll be receiving email at your new Gmail accounts!

rm -f /usr/local/cpanel/cpanel  

/scripts/installgd  

/scripts/cleanmd5  

/scripts/upcp

This will - delete the main cpanel program (causing it to be reinstalled completely), reinstall the GD perl graphics library, fix any MD5 problems (a common cause of problems on cPanel) and then do a cPanel upgrade.

Make sure you let all commands complete successfully, this may take a while!

Step 1 - Log into Cpanel and click on "File Manager"

Once you are logged into Cpanel, click on the "file manager". The file manager location will vary depending on which theme you are using. Once in file manager, browse to the location that you want to upload your zip file. I have chosen /wp-test/ for this tutorial.

Step 2 - Browse for the file on your desktop

Step 3 - Select the uploaded file and Extract

Click on the file that you just uploaded.

Now, look for the "extract" icon and click on it. Some Cpanel themes use text links instead of icons. It should be around there somewhere.

After you have clicked on "extract" a box will pop up asking you to choose the location. The default location is the directory that you are currently in. You can change this if you wish.

Once you have clicked on "extract files" you will see the results box. Simply close this box.

Thats it! Depending on the speed of your internet connection, you just saved yourself at least a couple of minutes. Some programs have thousands of tiny files such as graphics that take forever to upload one at a time.