Has my website crashed?

A lot of the time when clients come to me to design a website, especially those who are not so familiar with the internet and information technology equipment and software, they expect that once the website is up and running on a webhost, it will always be up and running, and they don't want it to ever come down, not even temporarily. Recently I had a couple incidents with one client's website crashing and I've also had incidents with other clients websites being taken down because some fee or the other was not paid to the respective host in a timely fashion.

The reality is websites do crash from time to time and there is nothing a webhost or website designer can do to prevent it from crashing 100% of the time (sometimes it can be avoided, but not all the time). However, there are times when it may not have crashed, but it is just unavailable to you the viewer.

Websites may become unavailable for many reasons:

1. You the individual user have lost your internet connection, or your internet cache needs to be deleted, or your firewall (or the company's firewall) is blocking you from viewing the website or the internet, or that specific website got blocked from your specific computer or the network on which your computer is located;
2. There are so many people looking at your website (or another website that is located on your webhost's server) that the server timed out.
3. You (or someone representing you) may have neglected to pay the webhosting or domain hosting fee on time.
4. The amount and size of the files on your webhost (files required for your website to run) may have maxed out / used up the amount of disk space your webhost has allocated for you.
5. The website or the webserver (your host is using) may be down for maintenance.
6. Your website may be down due to a programming error either on the webserver or on the website.
7. It may be that your website got hacked or blacklisted by an internet monitoring service.

Solutions:

1. The first thing you should do is determine, whether or not you are the only one experiencing this problem. To do this, check http://www.downforeveryoneorjustme.com/google.com, type in the website in the space provided and click the text that says "or just me?". If it says it's just you, then check your internet connection, firewalls, internet cache, etc. or get your computer repairs technician to do that for you.
2. Make sure you are familiar with your webhosting and domain hosting agreement and the features associated with your webhosting account. More specifically, be familiar with the cost of everything, how often you are required to pay, the amount of disk space and the amount of internet traffic your webhost allocated to you. Some webhosts will tell you that the disk space and / or the amount of traffic allocated is unlimited, please note this is not really the case, but, they usually say this, when the amount allocated is so high that it is unlikely you will ever need all of it, whilst others will be more specific. As for the fees, if they are not paid on time, your webhost and / or your domain host will suspend your account. In any of these cases (where the disk space or traffic is maxed out or webhosting or domain hosting fees are not paid), you should contact and consult your webhost to either pay off outstanding fees or to upgrade the account to get more traffic or disk space. 
3. Your website may also go down for maintenance purposes. This may mean anything from a bug being discovered and repaired in the webhost's software, to an upgrade to the webhosting hardware or software, or a major update or upgrade to the website itself. Webhosts and website designers usually try their best to avoid taking down the website while doing these things, but this is not always possible, because sometimes you have to switch things off and then turn them back on again. Talk to your website designer and your webhost about the problem, get both of them to investigate it. If you know your website designer is currently doing some work on the website (for example if you asked them to make some changes) talk to them and determine if they had to take it down for some reason. If, however, this is not the case, go straight to the webhost and enquire.
4. Programming errors can cause websites to go down, but first you have to determine what type of programming error, before you can find a solution:
1. there's something wrong with the code for the website. Unless there were any major recent changes to the website, there should not be anything wrong with the code, except in #3 below. If there was some major changes to the website recently concluded or currently going on, talk to your current website designer, if not, see #3 below.
2. There's a bug on your webhost's software or operating system. If this is the case, you need to report this to your webhost and have them deal with it.
3. Your website might be so old (it may have been up for a very long time) that modern internet protocols may no longer support it. To resolve this you would need to consult your website designer about redesigning it.
5. On occasion websites do get hacked. Your webhost is typically responsible for your website's basic security, and they provide free tools for your website designer to secure your website properly, so you should first have a chat with your webhost about the problem. In addition, there are other security measures you can pay for to add more protection to your website. One example is a secure sockets layer (ssl) certificate and others are website anti virus and anti hacker solutions. Discuss purchasing additional protection with your website designer before buying.
6. My website or domain name got blacklisted. This does not happen very often except when various internet monitoring agencies determine that your website, webhost or domain registrar is responsible (whether intentionally or not) for transmitting spam, phishing, internet viruses and other malicious activity. Usually when this happens, when you attempt to view the website, you will be presented with a page telling you your website has been blacklisted and a link to provide more information. Very often, if it is your website, this may either be the result of someone with an infected computer visiting your website, or it may mean that your website or webhost was hacked. Take a look at the link provided (on the default "this website has been blacklisted) with your website designer and depending on the causes & reasons, your website designer will be able to advise you how to proceed.

You may read more about these issues at: 

http://webupon.com/web-talk/jeremys-q-and-a-why-do-websites-crash/ and http://answers.yahoo.com/question/index?qid=20100505075129AAfOald

Steps to take for website designers can be found here: http://coding.smashingmagazine.com/2010/12/13/what-to-do-when-your-website-goes-down/

How can I be on top of things?

Pay attention to the emails received from your webhost because if they plan any maintenance on your webserver, they typically will inform you about this via email (usually days) before they conduct the maintenance.

What about restoring the website after it has gone down?
Both your webhost and your website designer should be capable of restoring the website for you. They each may have terms and conditions under which they'll agree to restore the website, so discuss it with them.

Changes! New Products and Services Launched!

Dear Readers,
So it has been awhile since I last blogged. I apologize for that, I have been pretty busy trying to get some new products and services on track.

Some of you may or may not know that besides website design, recently I have partnered with a couple companies to provide my customers with the whole website package, from webdesign to webhosting and domain name registration and secure sockets layer (ssl) certificates. Some of these services were advertised on my website over the past few months, but I have only just been able to add the ssl certificates option / service.

For those who may not be aware, I currently offer shared windows and unix hosting, as well as linux virtual private servers and managed private servers. The webhosting and domain name registration both have 30 day money back guarantee's on them, while the ssl certificates have 15 days money back guarantee (you may read more about these services HERE).

Services that I expect to launch early in the new year include:
microsoft exchange
microsoft sharepoint
windows virtual private server
windows managed private server
as well as some more ssl certificates

In addition, I have also been busy designing some new products most of which are for sale at My Zazzle Online Store. These include such things as plates, laptop cases, jugs, mugs, shoes, mousepads, etc.

There are also a few new items at my CafePress Online Stores: Here and Here.

So please feel free to go ahead and check them all out!

I have several more posts in the process of being written, so please come back soon for more information.

Also feel free to ask questions in the comments below!

New Merchandise for Christmas

So lately I've been designing a number of products on both Cafepress and Zazzle, for the upcoming christmas

Greeting Cards & Stationary:

	Product: Greeting Card Available  Single: US$4.50 View / Buy Now Ten (10) Pack: US$15.00 View / Buy Now Twenty (20) Pack: US$25.00 View / Buy Now Manufacturer: CafePress
	Product: Greeting Card Available  Single: US$2.95 View / Buy Now Ten (10) Pack: US$24.5 View / Buy Now Twenty (20) Pack: US$35.00 View / Buy Now Manufacturer: Zazzle *Also has matching stamps
	Product: Greeting Card Available  Single: US$6.00 View / Buy Now Ten (10) Pack: US$24.5 View / Buy Now Twenty (20) Pack: US$35.00 View / Buy Now Manufacturer: CafePress
	Product: Christmas Envelope Available  Single: US$0.80 View / Buy Now Manufacturer: Zazzle
	Product: Christmas Stamp Available  Single Sheet of 20: US$19.55 View / Buy Now 11 sheets of 20: US$17.55 each View / Buy Now 22 sheets of 20: US$16.55 each View / Buy Now Manufacturer: Zazzle
	Product: Caribbean Wall Calendar Available  Single: US$22.25 View / Buy Now Fifty (50) Pack: US$17.80 each View / Buy Now One Hundred (100) Pack: US$15.57 each View / Buy Now Manufacturer: Zazzle
	Product: Hibiscus 2012 Calendar Print Available  Single: US$4.58 View / Buy Now Manufacturer: CafePress

Joomla 1.7, JoomShopping and Core Design Captcha

So I recently started designing a website for a new client using Joomla 1.7 with JoomShopping and Core Design Captcha.

The website is to sell jewelry and much to my surprise, joomla 1.7, with JoomShopping worked pretty much right out of the box. no bugs or errors ... I also installed Akeeba Backup and Xmap.

The only major issues I've come accross so far (not including redesigning the template) have been:
1. the JoomShopping plugin for xmap does not work for joomla 1.7 - I wish it would
2. It was not easy to find a captcha security that would work on the website.

For the first one I have yet to find a solution ... but then again I have not yet been able to take a close look at it.

However, the second one ... the only security captcha I could find that worked with Joomla 1.7 was Core Design Captcha, but although that worked with Joomla 1.7 right out of the box, it did not work with the login / register pages of JoomShopping.

To get it to work with JoomShopping I found this blog post (http://www.webdesigner-profi.de/joomla-webdesign/joomla-shop/forum/posts/11/817.html?lang=en#4) - which essentially requires a hack of the original CDCaptcha - and followed the instructions ... however, when looking at the version of Core Design Captcha for 1.7 I realized there are some important changes to make to some of the code provided in that link. So here's the modified version for Joomla 1.7 with JoomShopping:

1. In edit plugins/system/cdcaptcha.xml, insert the following code:
(Please Note: This code is different from the original hack mentioned in the above link)

(let's say after COM_ZOO field)

2. Create a new php file called cdcaptcha_com_jshopping.php and save it in plugins/system/cdcaptcha/extension/site

3. In the file you just created place the following code:
(Please Note: This code is the same as that mentioned in the above link)

4. In plugins/system/cdcaptcha/language/en-GB/en-GB.plg_system_cdcaptcha.ini and also in administrator/language/en-GB/en-GB.plg_system_cdcaptcha.ini, place the following code:

PLG_SYSTEM_CDCAPTCHA_LABEL_ENABLED_FOR_COM_JSHOPPING="JoomShopping"
PLG_SYSTEM_CDCAPTCHA_PARAM_ENABLED_FOR_COM_JSHOPPING_NO="No"
PLG_SYSTEM_CDCAPTCHA_PARAM_ENABLED_FOR_COM_JSHOPPING_YES="Yes"
PLG_SYSTEM_CDCAPTCHA_DESC_ENABLED_FOR_COM_JSHOPPING=""

5. save all of these files (and upload them to the server if necessary).

com-property customization

ok I'm back with a little information on how to customize / add new fields in the property description / features:

1. go to your_joomla_root_directory>language>en-gb(or what ever language you are using on your website)>en-GB.com_properties.ini and find the first line where it says HIDDE.
2. Note the "Extra" code number ... for example where it says EXTRA40=HIDDE, you would note the EXTRA40 part of it.
3. Then change the word HIDDE that is after that EXTRA40 to what ever you want the field name to be.
4. Save the file.
5. go to your_joomla_root_directory>administrator>language>en-gb(or what ever language you are using on your website)>en-GB.com_properties.ini and find the first line where it says HIDDE.
6. Follow steps 2-4 above.
7. If you are editing these files on your local machine & have to upload them to see the changes, do so now. If you are editing them directly on the server / webhost, skip this step and move on to step 8.
8. If after saving and uploading these files, check your website, both in the front and in the backend. Try adding a new property & look for the new changes / fields. If you see them you are finished customizing, but if you do not see them, move on to step 9.
9. If you do not see the above changes in your form, go to your com-properties component in your joomla backend and note Layout Properties Detail and whether or not you use tabs. Then move on to step 10.
10. your Layout Template Properties Detail template is called by one of the following files:
a) locate in your_joomla_root_directory>components>com_properties>views>templates:
i) for details templates using tabs:
- Default Template = details_tab.php
- Default 1 Template = details_tab1.php
- Default 2 Template = details_tab2.php
- Default 3 Template = details_tab3.php
ii) for details templates not using tabs:
- Default Template = details.php
- Default 1 Template = details1.php
- Default 2 Template = details2.php
- Default 3 Template = details3.php
11. After locating and opening (for editing purposes) the relevant file, locate, in the file, the code that calls the fields that you just added. For example, in the language files above you would have noted the "EXTRA" code ... so in the above details file, find where it says "EXTRA" and the number(s) that goes with that piece of code.
12. If, lets say, you entered your fields at EXTRA40 but in the code in the details file, you can only find EXTRA39, below that piece of code for EXTRA39, make a space (press your enter button on your keyboard) and then copy & paste the code from EXTRA39 into that space. Then change in that copied code, where it says EXTRA39 to EXTRA40.

Install Webmin via terminal

Ok so,
now you may have a problem because although LAMP is installed, webmin is not yet installed.To download and install webmin:

1. In terminal:
a) First download some needed perl related libraries & also (this is for webmin 1.5x) apt-show-versions

sudo apt-get install apt-show-versions perl libnet-ssleay-perl openssl libauthen-pam-perl libpam-runtime libio-pty-perl

b) Then download webmin either by visiting http://www.webmin.com/download.html and downloading the .deb version of the file or via terminal using the following code:

wget http://www.webmin.com/download/deb/webmin-current.deb

If you use the former method of downloading the debian package, please copy the download to your home folder or the folder that you are currently in (you can determine which folder that is from terminal, by typing the following code dir)
c) install webmin via terminal by one of the following two options:

sudo dpkg -i webmin-current.deb

or

sudo dpkg --install webmin_1.5xx_all.deb

(where the xx in the webmin package name stands for the webmin version you downloaded).

And that should be it ... it may take a few minutes to do the installation, but, after that you should be ready ... when you see a message something like the following, the installation will be complete:

Webmin install complete. You can now login to https://YourServerNameOrIpAddress:10000/
as root with your root password, or as any user who can use sudo
to run commands as root.

Please note that installing webmin via terminal does not mean you will automatically be able to sign in to webmin using your regular user name and password ... you might initially be required to sign into webmin using root as your user name and set a password for root via terminal ... using the method described in the previous post.

However, once logged in as root, you can add your regular user account to webmin, by:
1. clicking on the "Webmin" link on the top left column and then
2. selecting "Webmin Users"
3. Clicking on the link (on top) titled "Create New User"
4. Enter the user name and where it says password, select, from the drop down menu, change "set to" to "Unix authentication", enter the real name (as identified when you first registered for your server's user account);
5. Next, click on the "Available Webmin Modules" blue bar and from the drop down select the module options you would like this user to have access to, or click the "Select All" option and then click the Create button, down below.

That's it, your new webmin user is now created using your default linux user name and password.

Testing Ubuntu Lamp 11.04 Natty Narwhal Server edition

So several days ago, my development server (that was loading Ubuntu Server 10.10 Maverick Meerkat) began giving problems. It started with suddenly not being able to connect via wireless ... and then, while we were still trying to figure out the solution to that problem, it stopped booting up up. We could not figure out what the problem was, only that possibly there might have been a hardware problem (maybe power supply?). So we changed the power supply and still could not boot up because some of the boot files had become corrupted.

We then decided to try out the 11.04 version which was not yet released, but the release was / is only days away.

We were able to get the server up and running, however, still could not get the wireless working.

Then it crashed again, this time for no discernible reason ... we had just got things up & running & perhaps the only thing in common was server updates had been done and we discovered certain boot files had broken links ... specifically the initrd.img & vmlinuz.img links.

Through this entire process, we learned a few useful tips from a variety of sources (sorry I do not recall exactly who) and I thought I should post them here for reference:


1. Download and install the server version of the operating system ... while going through that process, provide (when asked) the server host name, the user name and password, ... also select what server software you would like installed on the computer (LAMP, Samba, etc.) & make sure to provide a user name and password for mysql also.


2. To get the desktop to install over the server, download the alternate desktop cd version and after booting the server:
type

sudo apt-cdrom add
sudo apt-get update
sudo apt-get install ubuntu-desktop
sudo dpkg-reconfigure xserver-xorg
sudo /etc/init.d/gdm start

3. Installing Additional Server Software
If there is any server software that perhaps you forgot to install initially, you can always install them using one of the following ways:
A. Open terminal (Programs > Accessories > Terminal or with your keyboard, simply type Ctrl+Alt+t); Then type the following commands:
i)To install Apache:
sudo apt-get install apache2
Now to confirm the installation of Apache2 open http://YourIpAddress in your web browser, you will see It Works! default page of Apache.
ii) To install Mysql:

sudo apt-get install mysql-server

At the installation you be will asked to provide a root password for Mysql.
iii)To install php:

sudo apt-get install php5 libapache2-mod-php5

After this installation restart Apache [sudo /etc /init.d/apache2 restart] don’t write brackets.
iv)To install phpmyadmin:

sudo apt-get install phpmyadmin

Two option window will open in installation one for web server reconfigure automatically[select apache2] and second for configure database for phpmyadmin with dbconfig-common [select No].
You will need to copy the apache.conf to /etc/apache2/conf.d/ from /etc/phpmyadmin/ or the page will return a 404 error.
To copy Run-

sudo cp /etc/phpmyadmin/apache.conf /etc/apache2/conf.d

Now you have to restart your apache server

sudo /etc/init.d/apache2 restart

Now open http://YourIpAddresss/phpmyadmin

B. Alternately, you can install LAMP by opening Linux Tasksel
i) If you do not have Linux Tasksel installed already (most server editions do not have to worry about this, so those users can skip to ii) below), in terminal type

sudo apt-get install tasksel

and that command will install the software for you;
ii) to open & use the software, in terminal, type

sudo tasksel

and the software application window will open up for you;
iii) In the Tasksel window select the server software that you would like to install (LAMP for example) and click the space bar to select it;
iv) do the same to add more of the server softwares available. Use your arrow keys to highlight each available software in turn and the space bar to select them for installation;
v) to install everything you've selected, click the enter button on your keyboard;
vi) please remember, during installation, you may be asked to provide user names and passwords, so it would be a good idea to stay close by during this process.


4. Setting root password (just incase you can not sign in to your webmin account using your regular user name and password):
Launch the Terminal by going to Applications > Accessories > Terminal
Type or copy and paste the following command

sudo passwd root

Enter your user password
Enter the password you wish to use for the root user.
Enter the password one more time.
To test out the changes you can switch to the root user and try login in.

su

Enter your new root password.
You will now notice that it says root@YourSystemName.
You could also enter the following command:

whoami

Now to logout as the root user use the exit command

exit

You can easily change the password at any time for root by just following these steps again.

I'm back!

Today I'm going to document my experiences in designing a website with joomla 1.5.2 & phoca gallery.

I know I promised more blogs on the previous website I designed and have not yet posted them (due to time constraints), but I thought I should document this before I go much further.

Let me be honest, this is my first time working with phocagallery and so far it is one joomla extension that I have had no problems with whatsoever.

My major issue has been getting rid of the Powered by text at the bottom of the page on the front end. Now, don't get me wrong, I have no problem with giving credit where it is due, but, as a designer, who often uses multiple components and modules on websites, it looks untidy (to say the least) to have "powered by" or "designed by" text all over the place on the front end of the website.

Anyways, so on to the methods I discovered to remove this from the front end (without removing it completely.

for my work I used Joomla 1.5.2 with Phocagallery 2.7.5

to remove the powered by text, I basically edited two files:

1. Root Folder>components>com_phocagallery>views>categories>view.html.php
2. Root Folder>administrator>components>com_phocagallery>libraries>phocagallery>render>renderfront.php

In the first one I located the following code:
$tmpl['phoac'] = '

Power'.'ed by Phoc'.'a Gal'.'lery

';

now highlight, cut and replace that code with this:

//$tmpl['phoac'] = '

Power'.'ed by Phoc'.'a Gal'.'lery

';

then click save.

This will remove the powered by text from the main categories page, but not the other pages

to remove the powered by text from other pages go to the second file and locate the following code:

function getString() {
return '<'.'d'.'i'.'v'.' '.'s'.'t'.'y'.'l'.'e'.'='.'"'.'t'.'e'.'x'.'t'.'-'.'a'.'l'.'i'.'g'.'n'.':'.' '.'c'.'e'.'n'.'t'.'e'.'r'.';'.' '.'c'.'o'.'l'.'o'.'r'.':'.' '.'r'.'g'.'b'.'('.'2'.'1'.'1'.','.' '.'2'.'1'.'1'.','.' '.'2'.'1'.'1'.')'.';'.'"'.'>'.'P'.'o'.'w'.'e'.'r'.'e'.'d'.' '.'b'.'y'.' '.'<'.'a'.' '.'h'.'r'.'e'.'f'.'='.'"'.'h'.'t'.'t'.'p'.':'.'/'.'/'.'w'.'w'.'w'.'.'.'p'.'h'.'o'.'c'.'a'.'.'.'c'.'z'.'"'.' '.'s'.'t'.'y'.'l'.'e'.'='.'"'.'t'.'e'.'x'.'t'.'-'.'d'.'e'.'c'.'o'.'r'.'a'.'t'.'i'.'o'.'n'.':'.' '.'n'.'o'.'n'.'e'.';'.'"'.' '.'t'.'a'.'r'.'g'.'e'.'t'.'='.'"'.'_'.'b'.'l'.'a'.'n'.'k'.'"'.' '.'t'.'i'.'t'.'l'.'e'.'='.'"'.'P'.'h'.'o'.'c'.'a'.'.'.'c'.'z'.'"'.'>'.'P'.'h'.'o'.'c'.'a'.'<'.'/'.'a'.'>'.' '.'<'.'a'.' '.'h'.'r'.'e'.'f'.'='.'"'.'h'.'t'.'t'.'p'.':'.'/'.'/'.'w'.'w'.'w'.'.'.'p'.'h'.'o'.'c'.'a'.'.'.'c'.'z'.'/'.'p'.'h'.'o'.'c'.'a'.'g'.'a'.'l'.'l'.'e'.'r'.'y'.'"'.' '.'s'.'t'.'y'.'l'.'e'.'='.'"'.'t'.'e'.'x'.'t'.'-'.'d'.'e'.'c'.'o'.'r'.'a'.'t'.'i'.'o'.'n'.':'.' '.'n'.'o'.'n'.'e'.';'.'"'.' '.'t'.'a'.'r'.'g'.'e'.'t'.'='.'"'.'_'.'b'.'l'.'a'.'n'.'k'.'"'.' '.'t'.'i'.'t'.'l'.'e'.'='.'"'.'P'.'h'.'o'.'c'.'a'.' '.'G'.'a'.'l'.'l'.'e'.'r'.'y'.'"'.'>'.'G'.'a'.'l'.'l'.'e'.'r'.'y'.'<'.'/'.'a'.'>'.'<'.'/'.'d'.'i'.'v'.'>';
}

Replace it with the following:
function getString() {
//return '<'.'d'.'i'.'v'.' '.'s'.'t'.'y'.'l'.'e'.'='.'"'.'t'.'e'.'x'.'t'.'-'.'a'.'l'.'i'.'g'.'n'.':'.' '.'c'.'e'.'n'.'t'.'e'.'r'.';'.' '.'c'.'o'.'l'.'o'.'r'.':'.' '.'r'.'g'.'b'.'('.'2'.'1'.'1'.','.' '.'2'.'1'.'1'.','.' '.'2'.'1'.'1'.')'.';'.'"'.'>'.'P'.'o'.'w'.'e'.'r'.'e'.'d'.' '.'b'.'y'.' '.'<'.'a'.' '.'h'.'r'.'e'.'f'.'='.'"'.'h'.'t'.'t'.'p'.':'.'/'.'/'.'w'.'w'.'w'.'.'.'p'.'h'.'o'.'c'.'a'.'.'.'c'.'z'.'"'.' '.'s'.'t'.'y'.'l'.'e'.'='.'"'.'t'.'e'.'x'.'t'.'-'.'d'.'e'.'c'.'o'.'r'.'a'.'t'.'i'.'o'.'n'.':'.' '.'n'.'o'.'n'.'e'.';'.'"'.' '.'t'.'a'.'r'.'g'.'e'.'t'.'='.'"'.'_'.'b'.'l'.'a'.'n'.'k'.'"'.' '.'t'.'i'.'t'.'l'.'e'.'='.'"'.'P'.'h'.'o'.'c'.'a'.'.'.'c'.'z'.'"'.'>'.'P'.'h'.'o'.'c'.'a'.'<'.'/'.'a'.'>'.' '.'<'.'a'.' '.'h'.'r'.'e'.'f'.'='.'"'.'h'.'t'.'t'.'p'.':'.'/'.'/'.'w'.'w'.'w'.'.'.'p'.'h'.'o'.'c'.'a'.'.'.'c'.'z'.'/'.'p'.'h'.'o'.'c'.'a'.'g'.'a'.'l'.'l'.'e'.'r'.'y'.'"'.' '.'s'.'t'.'y'.'l'.'e'.'='.'"'.'t'.'e'.'x'.'t'.'-'.'d'.'e'.'c'.'o'.'r'.'a'.'t'.'i'.'o'.'n'.':'.' '.'n'.'o'.'n'.'e'.';'.'"'.' '.'t'.'a'.'r'.'g'.'e'.'t'.'='.'"'.'_'.'b'.'l'.'a'.'n'.'k'.'"'.' '.'t'.'i'.'t'.'l'.'e'.'='.'"'.'P'.'h'.'o'.'c'.'a'.' '.'G'.'a'.'l'.'l'.'e'.'r'.'y'.'"'.'>'.'G'.'a'.'l'.'l'.'e'.'r'.'y'.'<'.'/'.'a'.'>'.'<'.'/'.'d'.'i'.'v'.'>';
}

This last one will remove all other traces of the powered by text on the front end of your website, without actually removing the code itself.