Possible Reason/Solutions
===========================
Some might have this problem with their fresh Magento Installation or a Custom Magento Store, some have this problem with their exsiting installtion that is running fine for a long time. Sometime, this error is not visible and it just affect and make some Magento feature not working, for example this error just can be seen with Web Developer by tracking Ajax request and response. So here are a few possible reason
- Htaccess file which is located at Magento root folder. It will be this case if you meet Internal Server Error on every page. Try to remove it for testing purpose
If your website was running file for a long time, then it must be a change at Server side, just submit a ticket to Hosting Company.

The reason might be default permission on some hosting. Some hosting doesn’t allow high permission on folder, some need to grant correct permission on running script. For most cases I meet, you need to set permission 755 for index.php at Magento root
- Code Exception. Okay if you are not technical person, then there is no much thing you can do. Here are some ways you can try before need support from Magento Experts
+ Download magento-check.php script in order to validate basic requirement of your hosting
+ Run magento-clean tool to see if it solve your problem
- Custom code/module conflict. OK, so if you have tried all way above and they don’t help. You may want to play around it. Here is my advise

Turn on Developer Mode

If you look in the Magento bootstrap file (index.php) you’ll see lines similar to the following

#Mage::setIsDeveloperMode(true);
#ini_set(‘display_errors’, 1);

Uncomment these. In a production system, you’d never want to have your errors display to the browser, but while developing having an errors and warnings thrown immediately in your face is invaluable.

This way, you will see the actually problem which lead to the Internal Error Server. In almost cases, the reason is that there is an exception throw after output is sent to browser.

Local Server Copy

1. Login into your Local copy of Magento and change configuration > web > unsecured link & sercured link to {{base_url}}
2. This prevents errors with the file paths when you move the server and will be changed back later on.
3. Change the cache settings in the configuration to refresh and save.
4. Open myPHPadmin http://localhost/phpmyadmin/ and select your magento database
5. You are now going to export a copy of the database, also know as a dump. Use the following settings: Leave all the settings as they are but use the “save file as” and use compression none.

Live Server

1. In your control panel for you live server, set up a new mysql database with the same dbname, username, password
2. Unzip the latest version of Magento Commerce onto our root web folder
3. Install a fresh copy of magento using the same database settings
4. After a sucessful install, FTP your media folder and any template files you changed onto the live server, making sure that the file permissions are correct (i.e 777).
5. Delete the var/cache and car/session folder from Live Server
6. Login to the control panelfor for you mysql database (phpmyadmin in my case) and delete all the tables in you new magento database but not the database itself!
7. Import your old magento database using the Import Tab and following the steps.
8. Log into the magneto manager, and now change the {{base_url}} settings to reflect you new domain i.e http://www.webdesignlab.co.uk/magento
9. And finally give the cache settings a refresh.
10. Once complete, check your url and you should see your old site on the new server without any errors.

Installing bind9 and dns utilities

I assume that you already have a working Debian or Ubuntu installation. Lets install the bind9 package and dns utilities from Debian repository.

Configure your Linux system

Add this information to your /etc/hostname

Edit your /etc/hosts

127.0.0.1       localhost.localdomain   localhost
192.168.100.1   main.debian.lan main
# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Edit your /etc/resolv.conf

and add this information.

search debian.local
nameserver 192.168.100.1
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx

This is where Linux looks to find out how it should perform DNS lookups.

Lets create a zone

The zone files (or database files) are the heart of your BIND system. This is where all the information is stored on what hostname goes with what ip address.
Before we create a zone file, lets edit first the local configuration file /etc/bind/named.conf.local.

and the zone file data.

//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";

zone "debian.lan" {
        type master;
        file "db.debian.lan";
};

zone "100.168.192.in-addr.arpa" {
        type master;
        file "db.192.168.100";
};

Lets start creating a zone file in /var/cache/bind/ directory. Create a file called db.debian.lan

And add the following entry

$TTL 604800
@ IN SOA main.debian.lan. admin.debian.lan. (
                2008080101      ;serial
                04800           ;refresh
                86400           ;retry
                2419200         ;expire
                604800          ;negative cache TTL
                )
@       IN      NS      main.debian.lan.
@       IN      A       192.168.100.1
@       IN      MX      10      main.debian.lan.
main    IN      A       192.168.100.1
www     IN      CNAME   main
ubuntu  IN      A       192.168.100.2

Lets create the reverse DNS zone file called db.192.168.100

and the the following entry.

$TTL 604800
@ IN SOA main.debian.lan. admin.debian.lan. (
                2008080101      ;serial
                604800          ;refresh
                86400           ;retry
                2419200         ;expire
                604800          ;negative cache TTL
                )
@       IN      NS      main.debian.lan.
@       IN      A       192.168.100.1
1       IN      PTR     main.debian.lan.
2       IN      PTR     ubuntu.debian.lan.

The zone files are created, you can check your zone file configurations using these utilities:

Lets edit the file /etc/bind/named.conf.options

forwarders {
                202.78.97.41;
                202.78.97.3;
        };

Uncomment the line forwarders and add your ISP’s DNS server.

Lets restart our DNS server, and test using the tool dig.

You should see the following message

; <<>> DiG 9.3.4 <<>> debian.lan
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54950
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;debian.lan.                    IN      A

;; ANSWER SECTION:
debian.lan.             64800   IN      A       192.168.100.1

;; AUTHORITY SECTION:
debian.lan.             64800   IN      NS      main.debian.lan.

;; ADDITIONAL SECTION:
main.debian.lan.        64800   IN      A       192.168.100.1

;; Query time: 1 msec
;; SERVER: 192.168.100.1#53(192.168.100.1)
;; WHEN: Tue Aug  5 09:33:40 2008
;; MSG SIZE  rcvd: 79

Test your reverse DNS

If you see this message, you have successfully installed the DNS server.

; <<>> DiG 9.3.4 <<>> -x debian.lan
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42510
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;lan.debian.in-addr.arpa.       IN      PTR

;; AUTHORITY SECTION:
in-addr.arpa.		10800	IN	SOA	A.ROOT-SERVERS.NET. dns-ops.ARIN.NET. 2008080416 1800 900 691200 10800

;; Query time: 952 msec
;; SERVER: 192.168.100.1#53(192.168.100.1)
;; WHEN: Tue Aug  5 09:34:25 2008
;; MSG SIZE  rcvd: 108

You can also check your DNS configuration using nslookup and host command.

All computers in the LAN are going to use 192.168.100.1 as a nameserver, this can be set manually by setting statically:

then put this information.

nameserver 192.168.100.1

Have fun!

       www.example.com/?param1=var1&param2=var2&param3=var3

but for search engine freindly url’s I want it to be like

      www.example.com/var1/var2/var3

So here I am sharing small code snippet which works perfectly for my plguin and showing nice url’s.

We need to update the theme function.php file, just add the below code in function.php file and modify variables according to your need.

<?php

add_filter('rewrite_rules_array','wp_insertRewriteRules');
add_filter('query_vars','wp_insertQueryVars');
add_filter('init','flushRules');

// Remember to flush_rules() when adding rules
function flushRules()
{
  global $wp_rewrite;
  $wp_rewrite->flush_rules();
}

// Adding a new rule
function wp_insertRewriteRules($rules)
{
  $newrules = array();
  $newrules['(mytestpage)/([a-zA-Z0-9_\-]*)/([a-zA-Z0-9_\-]*)$'] =
'index.php?pagename=$matches[1]&var1=$matches[2]&var2=$matches[3]';
  $allrules = $newrules + $rules;
  return $allrules;
}

// Adding the variables  so that WP recognizes it
function wp_insertQueryVars($vars)
{
 array_push($vars, 'id');
 array_push($vars, 'var1');
 array_push($vars, 'var2');
 return $vars;
}
?>

To access these variables from plugin file use following code:

 $var1 = $wp_query->query_vars['var1'];
 $var2 = $wp_query->query_vars['var2'];

Now this will solve your plugins search engine friendly issues.

To use it, just include this helper in your controller and Its implementation is very simple:

1. For inline content:

2. For AJAX:

Here’s the helper:

You’ll need to copy the thickbox files to /app/webroot/effects. You can keep it in any folder for that matter, but as our team is following plugins – it’s made that way.

Let’s try hacking the FormHelper and enable AJAX. We’ll use jQuery Form plugin to submit forms via AJAX request (I don’t know any other good plugins for forms).

What we’ll be doing:

Converting a normal form like below one, to make it call AJAX(using jQuery lib) and alert us when form posted:

1. Extend your FormHelper to something like AjaxFormHelper (Now normally I don’t extend core helpers like this, but use a similar method similar to this (comment by grigri): http://cakebaker.42dh.com/2008/10/18/dont-abuse-the-apphelper-to-extend-the-core-helpers/#comment-110708 ) and overwrite create() method like this:

I’m not that good in explaining code flow, but you might have noted 3 get variables appended to our form action URL above. These variables are: ‘ajax’,'flash_only’ ,’js’ and serves their own purpose that I’ll tell in next steps.

2. Now we enable the AJAX in our form (CakePHP’s $options array is so good that you can overwrite and modify almost many methods easily):

This will show a JS alert after form has been submitted successfully.

This will show an inline message after form has been submitted successfully.

Note that ajax=true parameter we sent in create() method. This will tell helper to load this form via AJAX.

3. Now your form will be AJAX ready (if you’ve included this AjaxFormHelper properly). But because our controller function was made to process normal POST function, and flash message on success – we’ll have to change that behavior. This is what a normal JerksController::add() method should look like:

We don’t need full action content from views/jerks/add.ctp to appear in response when AJAX is called. We can make this work traditional way by checking if it’s an AJAX request in controller method itself and do needful, but I wouldn’t want to modify all my controller functions to enable AJAX, so here’s what I’ve come up with.

Remember the 3 GET variables above?

‘ajax’ => This one will determine if a given HTTP request is an AJAX request.

‘flash_only’ => This will tell if rendering should happen or not. Flash only means, after controller function is executed, do not render, just show flash message.

‘js’ => This is used for alert type, if this is not set, show inline alert. If set true, helper must show JS alert() on form success.

Inside your AppController::beforeFilter(), add this code:

Do not blame me for using GET variables, I found many issues with ‘named’ so I’m relying on normal GET variables.

Now you’ll need to edit ajax.ctp layout file.

This should be self explanatory, even though this code definitely needs some refactoring. We’re basically manipulating those 3 GET variables according to our need. In process, we’re also checking validation errors occurred in form.

I have not used it under the production environment yet, so I’d really like to hear any pitfalls (if any) using this approach. Thanks for reading.

Wow, what a mess.  Sad part is that we still see people doing it today and the unfortunate thing is that web solution visionaries end up with unsatisfactory and unmanageable web applications.   We of course refuse to take on any such project.

So, this article is aimed towards developers looking for a framework, developers with no direction yet looking for some, and the web visionaries who just are not sure what direction they should head when looking for a developer.

First off, Loadsys uses CakePHP.  I’m not going to get into technicals here, but CakePHP is a rapid application development framework that provides “rules” if you will for a developer to follow to keep a web application structured.  It comes with a suite of utilities and helpers that make things that seemed difficult or frustrating before, a breeze.

Cake offers the following benefits

• Rapid development framework that will speed up development time for a developer that is experienced with the framework
• Well-structured code (most of the time)
• Programming logic separate from design
• Less new developer “Getting Familiar” time
• Built-in utilities and helpers (no wheel re-inventing)
• Large and enthusiastic developer base

A web application needs a framework and in our opinion it should be a well-established one like CakePHP.   Now, please consider what I’m saying.  I said “Like” CakePHP.  We realize there are other frameworks out there.  Some achieve the same result as CakePHP.  For example, there is Ruby on Rails, who’s concept was created by 37 signals.  There are other frameworks out there as well.  These are all good and put developers in the right direction of structured coding.

I’m stuck between choosing Ruby On Rails and CakePHP, which one is better?

We have had this question asked by multiple clients.  There are times when we are competing for bid between us and a Ruby developer.  Whenever I get asked this question, I’m very honest.  I say, “There is not really a difference”.  Maybe this isn’t good for business, but in actuality there isn’t.  Maybe Ruby has some tools that Cake doesn’t have, or vice versa.  But at the end of the day, I’m sure that the client would have a well-structured web application in both scenarios.  Whether it is Ruby on Rails or CakePHP.

The web development realm has evolved into some smart people doing some amazing things.  They do this by learning from mistakes.  I’m hoping this article puts a young developer or even a person drawing up plans for a new web application to follow the movement towards well-architected web applications