INSERT INTO table (
id,
term,
order
) VALUES ” . join(‘,’, $values) . ” ON DUPLICATE KEY UPDATE order = VALUES(order);

Any help on this would be great. I plan to use this very soon.

100 => ‘Continue’,
101 => ‘Switching Protocols’,
102 => ‘Processing’,

200 => ‘OK’,
201 => ‘Created’,
202 => ‘Accepted’,
203 => ‘Non-Authoritative Information’,
204 => ‘No Content’,
205 => ‘Reset Content’,
206 => ‘Partial Content’,
207 => ‘Multi-Status’,
226 => ‘IM Used’,

300 => ‘Multiple Choices’,
301 => ‘Moved Permanently’,
302 => ‘Found’,
303 => ‘See Other’,
304 => ‘Not Modified’,
305 => ‘Use Proxy’,
306 => ‘Reserved’,
307 => ‘Temporary Redirect’,

400 => ‘Bad Request’,
401 => ‘Unauthorized’,
402 => ‘Payment Required’,
403 => ‘Forbidden’,
404 => ‘Not Found’,
405 => ‘Method Not Allowed’,
406 => ‘Not Acceptable’,
407 => ‘Proxy Authentication Required’,
408 => ‘Request Timeout’,
409 => ‘Conflict’,
410 => ‘Gone’,
411 => ‘Length Required’,
412 => ‘Precondition Failed’,
413 => ‘Request Entity Too Large’,
414 => ‘Request-URI Too Long’,
415 => ‘Unsupported Media Type’,
416 => ‘Requested Range Not Satisfiable’,
417 => ‘Expectation Failed’,
422 => ‘Unprocessable Entity’,
423 => ‘Locked’,
424 => ‘Failed Dependency’,
426 => ‘Upgrade Required’,

500 => ‘Internal Server Error’,
501 => ‘Not Implemented’,
502 => ‘Bad Gateway’,
503 => ‘Service Unavailable’,
504 => ‘Gateway Timeout’,
505 => ‘HTTP Version Not Supported’,
506 => ‘Variant Also Negotiates’,
507 => ‘Insufficient Storage’,
510 => ‘Not Extended’

Web Server Status Codes/Messages

The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes are defined below. The Status Message is intended to give a short textual description of the Status-Code.

• 1xx: Informational – Request received, continuing process
• 2xx: Success – The action was successfully received, understood, and accepted
• 3xx: Redirection – Further action must be taken in order to complete the request
• 4xx: Client Error – The request contains bad syntax or cannot be fulfilled
• 5xx: Server Error – The server failed to fulfill an apparently valid request

Informational 1xx

This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions.

100 Continue

The client may continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed.

101 Switching Protocols

The server understands and is willing to comply with the client’s request, via the Upgrade message header field (section 14.41), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response’s Upgrade header field immediately after the empty line, which terminates the 101 response.

The protocol should only be switched when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol may be advantageous when delivering resources that use such features.

Successful 2xx

All response codes that start with 2xx indicates that the request was successfully received, understood, and accepted.

200 OK

The request has succeeded.

201 Created

The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URL for the resource given by a Location header field. The origin server MUST create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server should respond with 202 (Accepted) response instead.

202 Accepted

The request has been accepted for processing, but the processing has not been completed. The request MAY or MAY NOT eventually be acted upon, as it MAY be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this.

The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent’s connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request’s current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled.

203 Non-Authoritative Information

The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource MAY result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).

204 No Content

The server has fulfilled the request but there is no new information to send back. If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent’s active document view. The response MAY include new metainformation in the form of entity-headers, which SHOULD apply to the document currently in the user agent’s active view.

205 Reset Content

The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.

206 Partial Content

The server has fulfilled the partial GET request for the resource. The request must have included a Range header field (section 14.36) indicating the desired range. The response MUST include either a Content-Range header field (section 14.17) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields for each part. If multipart/byteranges is not used, the Content-Length header field in the response MUST match the actual number of OCTETs transmitted in the message-body.

A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.

Redirection 3xx

This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. The action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A user agent SHOULD NOT automatically redirect a request more than 5 times, since such redirections usually indicate an infinite loop.

300 Multiple Choices

The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.

Unless it was a HEAD request, the response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice may be performed automatically. However, this specification does not define any standard for such automatic selection.

If the server has a preferred choice of representation, it SHOULD include the specific URL for that representation in the Location field; user agents MAY use the Location field value for automatic redirection. This response is cachable unless indicated otherwise.

301 Moved Permanently

The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD be done using one of the returned URIs. Clients with link editing capabilities SHOULD automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cachable unless indicated otherwise.

If the new URI is a location, its URL SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).

If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

Note: When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously change it into a GET request.

302 Moved Temporarily

The requested resource resides temporarily under a different URI. Since the redirection may be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cachable if indicated by a Cache-Control or Expires header field.

If the new URI is a location, its URL SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).

If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

Note: When automatically redirecting a POST request after receiving a 302 status code, some existing HTTP/1.0 user agents will erroneously change it into a GET request.

303 See Other

The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response is not cachable, but the response to the second (redirected) request MAY be cachable.

If the new URI is a location, its URL SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).

304 Not Modified

If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The response MUST NOT contain a message-body.

The response MUST include the following header fields:

• Date
• ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request
• Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same variant

If the conditional GET used a strong cache validator, the response SHOULD NOT include other entity-headers.

Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.

If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional.

If a cache uses a received 304 response to update a cache entry, the cache MUST update the entry to reflect any new field values given in the response.

The 304 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.

305 Use Proxy

The requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URL of the proxy. The recipient is expected to repeat the request via the proxy.

Client Error 4xx

The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method.

User agents SHOULD display any included entity to the user.

Note: If the client is sending data, a server implementation using TCP should be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes the input connection. If the client continues sending data to the server after the close, the server’s TCP stack will send a reset packet to the client, which may erase the client’s unacknowledged input buffers before they can be read and interpreted by the HTTP application.

400 Bad Request

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

401 Unauthorized

The request requires user authentication. The response MUST include a WWW-Authenticate header field containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field. If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity MAY include relevant diagnostic information.

402 Payment Required

This code is reserved for future use.

403 Forbidden

The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.

404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

405 Method Not Allowed

The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.

406 Not Acceptable

The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice may be performed automatically. However, this specification does not define any standard for such automatic selection.

Note: HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept headers sent in the request. In some cases, this may even be preferable to sending a 406 response. User agents are encouraged to inspect the headers of an incoming response to determine if it is acceptable. If the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions.

407 Proxy Authentication Required

This code is similar to 401 (Unauthorized), but indicates that the client MUST first authenticate itself with the proxy. The proxy MUST return a Proxy-Authenticate header field containing a challenge applicable to the proxy for the requested resource. The client MAY repeat the request with a suitable Proxy-Authorization header field.

408 Request Timeout

The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.

409 Conflict

The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response body SHOULD include enough information for the user to recognize the source of the conflict. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that may not be possible and is not required.

Conflicts are most likely to occur in response to a PUT request. If versioning is being used and the entity being PUT includes changes to a resource which conflict with those made by an earlier (third-party) request, the server MAY use the 409 response to indicate that it can’t complete the request. In this case, the response entity SHOULD contain a list of the differences between the two versions in a format defined by the response Content-Type.

410 Gone

The requested resource is no longer available at the server and no forwarding address is known. This condition SHOULD be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. This response is cachable unless indicated otherwise.

The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server’s site. It is not necessary to mark all permanently unavailable resources as “gone” or to keep the mark for any length of time — that is left to the discretion of the server owner.

411 Length Required

The server refuses to accept the request without a defined Content- Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.

412 Precondition Failed

The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.

413 Request Entity Too Large

The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing the request.

If the condition is temporary, the server SHOULD include a Retry-After header field to indicate that it is temporary and after what time the client may try again.

414 Request-URI Too Long

The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a URL “black hole” of redirection (e.g., a redirected URL prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI.

415 Unsupported Media Type

The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.

Server Error 5xx

Response status codes beginning with the digit “5″ indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. User agents SHOULD display any included entity to the user. These response codes are applicable to any request method.

500 Internal Server Error

The server encountered an unexpected condition, which prevented it from fulfilling the request.

501 Not Implemented

The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.

502 Bad Gateway

The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.

503 Service Unavailable

The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.

504 Gateway Timeout

The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server it accessed in attempting to complete the request.

505 HTTP Version Not Supported

The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client other than with this error message. The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server.

I do not necessarily agree with or use all of these, but use this as a reference with some guidelines.
Don’t include them ‘just for the sake of it’, but if they are relevant – add them.

HIGHLY IMPORTANT ONES

Title

The Title Tag should contain no more than 70 characters (although 100 characters may be indexed depending on the engine).

<title>TitleTitleTitle</title>

Description

OK, its not exactly a META Tag, but the Description Tag can have up to 150 characters (although, 200 – 250 characters may be indexed and only a smaller portion of this amount be displayed). Also used in the browser top bar, tabs, and in the taskbar.

<meta NAME="Description" CONTENT="DescriptionDescription">

Keywords

In the Keyword tag use specific descriptive ‘words’ or ‘phrases’ to match the content on your site. You can use up to 200 characters with each word (or phrase) separated with a comma(,).

<meta NAME="Keywords" CONTENT="KeywordsKeywords">

MEDIUM IMPORTANCE – USE IF REQUIRED

Robots

The values ALL and NONE set all directives on or off: [ALL=INDEX,FOLLOW] and [NONE=NOINDEX,NOFOLLOW].

<meta NAME="Robots" CONTENT="INDEX,FOLLOW">

MS Tags

Do you want Microsoft products to automatically generate smart tags on your web pages. No? Then add this!

<meta NAME="MSSmartTagsPreventParsing" CONTENT="TRUE">

IE6 Image Toolbar

I found this one to prevent the image options toolbar popping up in IE6 over the images.

<meta http-equiv="imagetoolbar" CONTENT="no">

Expires

Use “never” unless your site will expire. (Eg. Tue, 18 Apr 2006 14:57:09 GMT | Note: Requires RFC1123 date format.

<meta HTTP-EQUIV="Expires" CONTENT="ExpiresExpires">

Cache Control

Cache control level. None / Public / Private / no-Cache / no-Store

<meta HTTP-EQUIV="CACHE-CONTROL" CONTENT="PUBLIC">

No Cache

This directive indicates cached information should not be used and instead requests should be forwarded to the origin server.

<meta HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">

Copyright

Who is the Owner of the site? or the Company Name

<meta NAME="Copyright" CONTENT="CopyrightCopyright">

Designer

The webmasters name

<meta NAME="Designer" CONTENT="DesignerDesigner">

Revisit-After

Tell the search engines how often this page updates. (Eg. 21 days | Note: Most search engines do not support this Meta Tag)

<meta NAME="Revisit-After" CONTENT="Revisit-AfterRevisit-After">

LOW IMPORTANCE

Publisher

Owner, Webmaster, Company Name, etc..

<meta NAME="Publisher" CONTENT="PublisherPublisher">

Author

The Author Tag is for the person who wrote the material for the site. Usually the client.

<meta NAME="author" CONTENT="AuthorAuthor">

Subject

The Subject Tag is for what your site is about. Business, music, hobby, cars. You can use up to 100 characters.

<meta NAME="subject" CONTENT="SubjectSubject">

Classification

The Classification tag is similar to description but more in detail.

<meta NAME="Classification" CONTENT="ClassificationClassification">

Geography

Where are you located? Insert your full address?

<meta NAME="Geography" CONTENT="GeographyGeography">

Language

Is your site in English, Spanish, French…..?

<meta NAME="Language" CONTENT="LanguageLanguage">

City

Your City

<meta NAME="city" CONTENT="CityCity";>

Country

Your Country

<meta NAME="country" CONTENT="CountryCountry">

Distribution

Use [Global] unless it is a [Local] only site.

<meta NAME="distribution" CONTENT="Global">

SPECIAL USE

Redirect / Refresh

Used to redirect browsers to another page, or refresh the current page.
’0′ is the number of milliseconds, so use ’3000′ for a 3 second redirect.

<http-EQUIV="refresh" content="0; url=homepage.htm" >

All tags, attributes and values must be written in lowercase.

Right: <a href=”www.kilroyjames.co.uk” >
Wrong: <A HREF=”www.kilroyjames.co.uk” >

All attribute values must be within quotes

Right: <a href=”www.kilroyjames.co.uk” >
Wrong: <a href=www.kilroyjames.co.uk >

All tags must be properly nested

Right: <em>this emphasis just keeps getting <strong>stronger and stronger</strong></em>
Wrong: <em>this emphasis just keeps getting <strong>stronger and stronger</em></strong>

All XHTML documents must carry a DOCTYPE definition

The DOCTYPE is an intimidating looking piece of code that must appear at the start of every XHTML document, it tells the browser how to render the document.

Rules for the DOCTYPE tag:

* It must be the first tag in the document
* The DOCTYPE is not actually part of the XHTML document so don’t add a closing slash
* It should point to a valid definition file called a DTD that tells the browser how to read the document
* You must write the DOCTYPE tag correctly otherwise your document will explode (into little pieces of HTML called “tag soup”) and be unvalidatable.

There are three types of valid XHTML 1.0 document: Strict, Transitional, and Frameset. If you can get your document to validate with “Strict” then do so, however some legacy tags and attributes aren’t allowed in Strict so you can use “Transitional” instead.

Note also that using a Transitional DTD takes most browsers out of “Standards” mode. It is much trickier to get your web pages to look consistent across different browsers when the browsers are not in Standards mode. I’m not going to explain the minutae of the DOCTYPE tag as it gets deeper and more complicated, just know that for best results you should use one of the following, preferably the first one (Strict):

<!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd”>

<!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN”
“http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”>

The HTML tag must contain an XMLNS attribute

You don’t need to understand the “XML namespace” attribute, except to know that it is required in all XHTML documents. Here is an example of how to write it:

<html xmlns=”http://www.w3.org/1999/xhtml”>

Documents must be properly formed with HTML, HEAD, TITLE and BODY tags

In HTML it is possible to write a webpage that contains none of the above tags; in XHTML it is not. The above tags must be included and they must be nested and ordered correctly, as follows (the DOCTYPE has been omitted):

<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title></title>
</head>

<body>
<p>
See how the TITLE must be placed in the document HEAD – the TITLE is considered
to be a “required child” element of the HEAD.
Notice that the HEAD must also appear before the document BODY.
Notice also how both the HEAD and the BODY must be contained
within the HTML tag. Again, HEAD and BODY are “required child”
elements of the HTML tag. Finally, notice that this text is
written within a <p>paragraph</p> tag; in XHTML you may
not write text directly in the BODY tag without using a suitable
container tag, such as <p> or <div>.
</p>
</body>
</html>

All tags must be closed, even single tags

Wrong:

<p>Mary had a little lamb
<p>It’s fleece was white as snow

Right:

<p>Mary had a little lamb</p>
<p>It’s fleece was white as snow</p>

In XHTML even single tags have to be closed – absolutely NO tag may be left open.

Wrong:<p>Mary had a little lamb <br>It’s fleece was white as snow</p>

Right: <p> Mary had a little lamb <br/> It’s fleece was white as snow</p>

Attribute minimisation isn’t allowed

In HTML, attributes can be strung together almost like they were keywords, ie. <dl compact>, this is called attribute minimisation. In XHTML that is not allowed, attributes and values must be excplicit, ie.

<dl compact=”compact”>

ID and NAME attributes

In HTML it was legal to use ID and NAME attributes interchangeably. In XHTML the NAME attribute is formally deprecated and cannot be used. In all cases where you would think to use a NAME attribute you must now use ID instead. e.g.

Correct HTML: <input type=”submit” name=”s” value=” Search ” >

Correct XHTML:<input type=”submit” id=”s” value=” Search ” />

STYLE is all in your HEAD

XHTML does not allow STYLE or SCRIPT declarations within the body of a document they must be placed in the document HEAD instead.

$_SERVER['REQUEST_URI']

It return the URL in to access the page which is executing the script. If you need to type http://www.example.com/product.php?id=5 to access the page then $_SERVER['REQUEST_URI'] returns “/product.php?id=5.

$_SERVER['DOCUMENT_ROOT']

Returns the root directory of the server which is specified in the configuration file of server. This variable usually returns the path like “/usr/yoursite/www” in Linux and “D:/xamps/xampp/htdocs” in windows.

$_SERVER['HTTP_HOST']

Returns the host’s name as found in the http header. This variable usually returns the path like “example.com” when the you find “http://example.com” in browser’s address-bar and return “www.example.com” when you see http://www.example.com in the address-bar. This is quite useful when you’ve to preserve session while making online payment using PHP since session stored for “http://example.com” is not same as for the “http://www.example.com”.

$_SERVER['HTTP_USER_AGENT']

Returns the user agent’s (browser) detail accessing the web page. We can use strpos($_SERVER["HTTP_USER_AGENT"],”MSIE”) to detect Microsoft Internet explorer or you can use strpos($_SERVER["HTTP_USER_AGENT"],”Firefox”) to detect firefox browser in PHP.

$_SERVER['PHP_SELF']

Returns the file-name of the currently executing script. Let’s suppose that you’re accessing the URL http://www.example.com/product.php?id=5 then $_SERVER['PHP_SELF'] returns “/product.php” in your script.

$_SERVER['QUERY_STRING']

Returns the query string if query string is used to access the script currently executing. Query strings are those string which is available after “?” sign.if you use $_SERVER['QUERY_STRING'] in the script executing the following URL “http://www.example.com/index.php?id=5&amp;page=product” then it returns “id=5&amp;page=product” in your script.

$_SERVER['REMOTE_ADDR']

Returns the IP address of remote machine accessing the current page. But you can’t relie on $_SERVER['REMOTE_ADDR'] to get the real IP address of client’s machine.

$_SERVER['SCRIPT_FILENAME']

Returns the absolute path of the file which is currently executing. It returns path like “var/example.com/www/product.php” in Linux and path like “D:/xampp/xampp/htdocs/test/example.php” in windows.

Myth 1: All Meta Tags Are Of Equal Importance

Some Meta tags are useful while others are not. Search engines are relying more and more about what is on the website than what the tags are telling them. The description tag is used by some (but not all) search engines. The same goes for the keyword tag, which is hardly used by any search engines. I will not improve your ranking and it could actually cause you ranking to go down. In my opinion, the only tags you should use are the robot tag and the description tags.

Myth 2: You must submit Your Site to Search Engines regularly

Submit your site once, that’s enough. The engines will come back and re-visit of their own accord. You can sometimes speed up the process of getting your site indexed by linking it to a high traffic site. The search engines will find the URL to your site and index it automatically.

Myth 3: SEO is Expensive

Actually, SEO is probably the most cost effective form of online marketing. Organic SEO is cheaper to set up and maintain than a PPC campaign or banner advertising. With PPC and banner advertising, you pay for clicks or impressions. With SEO, all clicks are Free. You simply pay for the set up and monitoring of your site’s pages.

Myth 4: PPC Is More Effective Than Natural SEO

In the short term this is true. Pay Per Click (PPC) can bring good returns if done properly. In the long term it is not more effective because organic listings are preferred to PPC listings by a ratio of 5 to 1 to PPC. People trust organic searches to return relevant results. People also know that the ads to the right of the page are sponsored ads. They have long ago figured out that anyone can bid on any term they want, as many often do, without even a hint of relevance. So, long term SEO structuring can indeed be more effective than PPC, especially when considering the preferences of search traffic. A top 5 ranking may take some time to get, but once you are there (and provided you can maintain it), you will get better results than from a PPC ad.

Myth 5: Employing an SEO specialist is cheaper

The problem with employing someone is that they are paid hourly or by monthly salary. Most SEO firms charge per website or project. It doesn’t matter how long it takes us, you pay a one tíme charge. When you hire a firm, it’s like having a team of SEO experts on your payroll. Paying a flat rate saves you money and speeds up the time it takes to complete a job. Additionally, most SEO firms have specialists who write, submit, redesign sites, post pages, etc… Hiring one person who can do all these things competently is highly unlikely.

Myth 6: I can only optimize my homepage for key terms

You can and should optimize every page on your site. Each page should have its own key terms, with no more than three phrases per page, preferably only one key phrase per page.

Myth 7: All I need to do is write content with the correct keyword density and my site will rank well

Wrong…especially if you want to rank on Google. You will need off-site SEO as well as on-site SEO. Keyword density may work on MSN (for now), but it will take more than that to rank well for all search engines.

Myth 8: I shouldn’t aim for the most competitive keywords and phrases

If the keywords you are competing for are very competitive, should you optimize your site for them? Of Course! I would optimize for some high, medium and low competitive key terms. Cover all your bases. The worst case is that you won’t rank well for the high competitive key terms and that’s ok. You can always work to improve them. Don’t shy away from top key terms just because they are competitive. You may never know how close you could rank for them unless you try.

Myth 9: Only use companies that give you a guarantee

Guarantees would be nice if they were worth the paper they are printed on. In fact, most guarantees from SEO firms have the same stipulation in them. This stipulation usually states that as long as they get one of your key phrases to the top of any major search engines, they have fulfilled their end of the agreement. This is irrelevant to the competition of the term. In other words…it’s easy to be number one for terms no one is competing for. Don’t be deceived by high rankings listed on SEO sites as they can be misleading.

Myth 10: Professional SEO requires a long expensive commitment

It certainly shouldn’t. Don’t lock yourself into a year contract with any company unless you already have an established, favourable business relationship. SEO, in most cases, should be performed on a month to month basis with a mutual understanding of the objectives and relative timetable. Often, both the long and short term maintenance contracts that many firms insist on including with each job are unnecessary. As an example…If you have a new site optimized, especially right after an update, you may not see results for three months. Why pay for maintenance in the interim time?
Additionally, you may not be happy with the results of an SEO firm or even the level of service. A long term contract may only ensure that you receive a full year of bad service. So, don’t lock yourself in with a year contract, at least until you are comfortable with whom you are dealing with.

php_cheat_sheet

regular_expressions_cheat_sheet

mysql_cheat_sheet

mod_rewrite_cheat_sheet

Jquery-Cheat-Sheet-1.2

javascript_cheat_sheet

html-cheat-sheet

Google_Cheat_Sheet

xhtmlcheatsheet

xhtmlcheatsheet

HTML5_Cheat_Sheet