What is PHP?

PHP stands for PHP: HyperText Preprocessor, it is a server-side scripting language, and as the name goes, it is to create dynamic and interactive Websites for your visitors. Maybe you currently make your Websites in HTML? HTML alone cannot create dynamic Web pages, HTML is clearly defined as a static language, as it is always static and mainly is used for structuring (or styling, in some cases) a document (or a Web page, if you like).

What do we mean by server-side scripting?

You may already know, but HTML is a client-side language, so the browser translates the HTML code into "bytecode" that the computer can understand, and so the computer translates bytecode into what we can clearly understand, text, for example. Server-side scripting is a little different, a little bit more added to the story. As with PHP, server-side scripting languages have an interpreter inside a machine, that translates the code (in our case, PHP code) to HTML code (that the browser can understand), and then the same process will take place with the browser translating the HTML code to bytecode, and so forth. With server-side scripting languages, you don't need anything adding to your browser or computer, as the interpreter inside the machine that hosts the particular Website does most of the work.

What's the fuss with server-side scripting languages, then?

The thing that makes server-side scripting a must nowadays is because it can generate dynamic Web pages, but what do we mean by dynamic Web pages? Well, imagine you wanted to start a forum, and you used HTML. Okay, you used a form to submit the data and it is sent to your e-mail address, and you have to edit the static Web page every time you want a new post added. That, to me, would be the most annoying job of creating a Website. However, with PHP (or any other server-side scripting language, for that matter), can be completely automated, and you'd not have to edit your file even once! The thing that PHP does, is sends the form data to a different page, saves it in "pre-defined" variables (things that store a value), and using something called a "while loop" that continually loops all the posts saved in the Web page - and that's it! PHP stores the posts in a MySQL database (something that holds data, if you like, like member accounts, etc) and uses that as long-term memory.

But if we're talking about server-side scripting languages, what makes PHP different from the rest? Well, simply put, PHP is probably the best thing that has come into the server-side scripting genre. If you have heard about other scripting languages like Perl or ASP/ASP.NET, you'll come to find that they are extremely hard to learn from. Put it this way, the majority of Web developers that use ASP.NET, for example, are those who have come from a different programming background, like have known VBScript, or other languages that's in relation to ASP.NET, the same with Perl. The difference between PHP and the rest, is PHP is incredibly easy to learn, especially for the newbies towards this industry, and PHP has took several steps to ensure an easy introduction to those newbies to the world of programming. Let's do an example, lets see which is the easiest to understand, out of PHP, VBScript and Perl, by doing a simple "Hello World" program, that outputs text to a Web page:

PHP:

echo "This is some text that'll be shown in a Web page...";

VBScript/ASP.NET:

Response.Write("This is some text that'll be shown in a Web page...");

Perl:

#!/usr/bin/perl

print "content-type: text/html nn";

print "This is some text that'll be shown in a Web page...";

Okay, now I am not going to say things like "well, obviously PHP is the easiest to understand" - as obviously, we all have different preferences, but what I can say is, that they all do the same thing. Which seems the most logical to you? In my opinion, the two most logical ones for me is PHP and VBScript/(ASP.NET).

Now it's up to you which one you want to go ahead with, experiment which one is best for you, after all, we all have dfferent tastes.

Good luck!

Below are a few resources to get started with PHP:

# - w3schools.com

# - php.net

# - mysql.com

Just what is a 301 Redirect?

There seems to be a lot of confusion as to what to do when you move, delete, or want to redirect incoming web traffic from an 'old' web page to a 'new' web page. A 301 redirect is the most efficient method for web page redirection from an old web page to a new web page location. There is also some confusion as to how to handle the complete move or redirection from one web domain to another web domain. According to Google, "If you need to change the URL of a page as it is shown in search engine results, we recommended that you use a server-side 301 redirect instead."

How to Set Up a 301 Redirect

Depending on your web environment, there are several methods to set up a 301 redirect. A 301 redirect is not that hard to implement and it should preserve your search engine rankings for that particular page or web domain.

.htaccess 301 Redirection

The .htaccess file needs to be placed in the root directory of your old website. In this example, we are redirecting incoming web traffic from an old domain to a new domain.

Options +FollowSymLinks

RewriteEngine on

RewriteRule (.*) http://www.newdomain.com/$1 [R=301,L]

The .htaccess file is the most common method used for 301 web site redirection.

PHP 301 Redirection

You would place this code in a file at the old location.

Header( "HTTP/1.1 301 Moved Permanently" );

Header( "Location: http://www.new_location.com" );?>

IIS 301 Redirection

• In Internet Services Manager, you need to right click on the file or folder you wish to redirect
• Select the radio button titled "a redirection to a URL".
• Enter the redirection web page
• Check "The exact URL entered above" and the "A permanent redirection for this resource"
• Click on 'Apply'

That is all there is to it.

There are other methods in addition to set up a 301 redirection which include coding for ASP, ASP.NET, Java, CGI, Cold Fusion and Ruby on Rails. The above are the most common that I've encountered. When set up correctly, a 301 redirect will preserve your search engine rankings when it is necessary to move files around or switch, or consolidate, domain names.

I've done quite a bit of research into web analytics lately, and I have found a couple of things. Google analytics Is a great tool, but it cannot be the only tool an organization relies on. Because it is a purely JavaScript based, it is unable to catch browsers that do not have JavaScript enabled, this includes the search engine robots, some hand held devices, as well as a percent of users that manually turn this off. That being said we need a tool to parse the log files from the server and to give us information about these users, as well as providing us with "on demand" stats where as Google's stats are next day. The server logs also contain a wealth of other information that we are collecting automatically, so we might as well take advantage of it.

I have come to the conclusion that we need to use Google Analytics but we also need a tool that reads the server logs. There are quite a variety of tools that would fill this need. Google recently purchased Urchin who's web analysis product runs Google analytics, costs about $3k and will work with the Google Mini, Urchin also gives the ability to read logs from server software other than IIS (like apache, the software used for open source applications) .

Urchin will be releasing another version shortly, and this will be the first release since the Google buyout. Another option is WebTrends Analytics it costs about $4k. It Like Urchin will read both IIS and Apache logs, and has a web interface for users. The last product is NetTracker, it runs about $4k for the software, and another grand for support. it was recently bought out by Unica. The administration of netTracker is not the smoothest, and the support seems to have declined on quality since the buy out.