Find Cheap Airline Tickets and Cheap Flights Here. Whatscheaper is your best source for the cheapest fares around. Low Fares, cheap flights, and great Travel prices are what we stand for! ...

whatscheaper.com
  • Domain Name
    whatscheaper.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #39472
  • Page Size
    62.9 KB
  • Ip Address
    96.45.82.4
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    8 GIF, 1 JPG, 10 PNG

Website Meta Analysis

  • Title
    WhatsCheaper.com - Airline Tickets - Cheap Flights and More!
  • Meta Keyword
    WhatsCheaper.com, airline tickets, flights, cheap flights, plane tickets, flight tickets, low fares, cheap fares
  • Meta Description
    Find Cheap Airline Tickets and Cheap Flights Here. Whatscheaper is your best source for the cheapest fares around. Low Fares, cheap flights, and great Travel prices are what we stand for!

Technical Analysis

  • Webserver
    Microsoft-IIS/5.0
  • Ip Address
    96.45.82.4
  • Domain Age
    7 Years, 5 Months, 18 days.
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from whatscheaper.com.

HTML Analysis

  • server: Microsoft-IIS/5.0
  • date: Thu, 27 Jun 2013 00:39:49 GMT
  • x-powered-by: ASP.NET
  • connection: close
  • cache-control: private, no-cache
  • expires: 0
  • pragma: no-cache
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains by Proxy, Inc.

Domain Name: WHATSCHEAPER.COM

Name Servers:
NS0.DNSMADEEASY.COM
NS1.DNSMADEEASY.COM
NS2.DNSMADEEASY.COM
NS3.DNSMADEEASY.COM

For complete domain details go to:
http://who.godaddy.com/whoischeck.aspx?Domain=WHATSCHEAPER.COM

DNS Analysis


DNS servers
ns1.dnsmadeeasy.com [208.80.124.2]
ns3.dnsmadeeasy.com [208.80.125.2]
ns0.dnsmadeeasy.com [208.94.148.2]
ns2.dnsmadeeasy.com [208.80.126.2]


DNS Records

Answer records
whatscheaper.com NS  ns1.dnsmadeeasy.com 86400s
whatscheaper.com NS  ns3.dnsmadeeasy.com 86400s
whatscheaper.com NS  ns2.dnsmadeeasy.com 86400s
whatscheaper.com NS  ns4.dnsmadeeasy.com 86400s
whatscheaper.com NS  ns0.dnsmadeeasy.com 86400s
whatscheaper.com A 208.94.146.80 1800s
whatscheaper.com A 208.94.146.81 1800s
whatscheaper.com A 208.94.146.71 1800s
whatscheaper.com A 208.94.146.70 1800s
whatscheaper.com MX
preference: 20
exchange: mailstore1.secureserver.net
120s
whatscheaper.com MX
preference: 10
exchange: smtp.secureserver.net
120s
whatscheaper.com MX
preference: 30
exchange: dayanahostmail.whatscheaper.com
120s
whatscheaper.com SOA
server: ns0.dnsmadeeasy.com
email: dns@dnsmadeeasy.com
serial: 2008011083
refresh: 43200
retry: 3600
expire: 1209600
minimum ttl: 180
86400s

Authority records

Additional records
dayanahostmail.whatscheaper.com A 199.241.218.62 1800s

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 152 Errors
  • 24 Warnings
Ratio Text/Html
  • 0.677159362673541
Message Error
  • Error Line 12, Column 79: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="stylesheet" media="all" type="text/css" href="style/jsblocker.css">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 12, Column 1: start tag was here
    <link rel="stylesheet" media="all" type="text/css" href="style/jsblocker.css">
  • Error Line 54, Column 71: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="stylesheet" href="stylesheets/jslider.css" type="text/css">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 54, Column 1: start tag was here
    <link rel="stylesheet" href="stylesheets/jslider.css" type="text/css">
  • Error Line 55, Column 76: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="stylesheet" href="stylesheets/jslider.blue.css" type="text/css">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 55, Column 1: start tag was here
    <link rel="stylesheet" href="stylesheets/jslider.blue.css" type="text/css">
  • Error Line 71, Column 30: required attribute "type" not specified
    <script language="javascript">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 81, Column 49: required attribute "type" not specified
    <script language="javascript" src="js/cities.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 123, Column 30: required attribute "type" not specified
    <script language="javascript">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 132, Column 73: document type does not allow element "select" here
    …='exp_month' class='dropdown dpwidth1'><option value='-'>-</option> <option va…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 149, Column 37: ID "exp_month" already defined
    		str="<select name='exp_month' id='exp_month' class='dropdown dpwidth1'><optio…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 132, Column 37: ID "exp_month" first defined here
    		str="<select name='exp_month' id='exp_month' class='dropdown dpwidth1'><optio…
  • Error Line 149, Column 73: document type does not allow element "select" here
    …='exp_month' class='dropdown dpwidth1'><option value='-'>-</option><option val…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 180, Column 30: required attribute "type" not specified
    <script language="javascript">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 197, Column 51: required attribute "type" not specified
    <script language="javascript" src="js/calendar.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 198, Column 158: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lute; TOP: 311px; HEIGHT: 217px" name=calendar src="js/calendar_builder2.html"…
  • Error Line 198, Column 211: there is no attribute "frameBorder"
    …e=calendar src="js/calendar_builder2.html" frameBorder=0 scrolling=no></iframe>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 198, Column 211: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=calendar src="js/calendar_builder2.html" frameBorder=0 scrolling=no></iframe>
  • Error Line 198, Column 223: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=calendar src="js/calendar_builder2.html" frameBorder=0 scrolling=no></iframe>
  • Error Line 198, Column 225: document type does not allow element "iframe" here; assuming missing "object" start-tag
    …e=calendar src="js/calendar_builder2.html" frameBorder=0 scrolling=no></iframe>
  • Error Line 204, Column 59: document type does not allow element "link" here
    	<link rel="canonical" href="http://www.whatscheaper.com"/>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 207, Column 30: required attribute "type" not specified
    <script language="javascript"> 

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 213, Column 26: document type does not allow element "span" here
    		text.innerHTML = "<span>Open</span>";

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 217, Column 26: document type does not allow element "span" here
    		text.innerHTML = "<span>Hide</span>";

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 236, Column 29: document type does not allow element "br" here
    			//newdiv.innerHTML = '<br><div id='+divIdName+' class="hotel_wid_txt">TO: <i…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 236, Column 30: end tag for "br" omitted, but OMITTAG NO was specified
    			//newdiv.innerHTML = '<br><div id='+divIdName+' class="hotel_wid_txt">TO: <i…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 236, Column 26: start tag was here
    			//newdiv.innerHTML = '<br><div id='+divIdName+' class="hotel_wid_txt">TO: <i…
  • Error Line 236, Column 39: character "+" is not allowed in the value of attribute "id"
    			//newdiv.innerHTML = '<br><div id='+divIdName+' class="hotel_wid_txt">TO: <i…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 236, Column 73: document type does not allow element "div" here
    …id='+divIdName+' class="hotel_wid_txt">TO: <input type="text" name="departure_…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 236, Column 140: character "'" is not allowed in the value of attribute "id"
    …"departure_city[]" id="departure_city_'+num+'" size="10" onKeyUp="countme(this…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 236, Column 167: there is no attribute "onKeyUp"
    …rture_city_'+num+'" size="10" onKeyUp="countme(this.value,\'departure_city_'+n…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 236, Column 230: there is no attribute "autocomplete"
    …arture_city_'+num+'\');" autocomplete="off" />FROM: <input type="text" name="a…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 236, Column 302: character "'" is not allowed in the value of attribute "id"
    …ame="arrival_city[]" id="arrival_city_'+num+'" size="10" value="" onKeyUp="cou…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 236, Column 461: character "'" is not allowed in the value of attribute "id"
    …nput type="text" name="fdt[]" id="fdt_'+num+'" size="10"  onclick="dispCalenda…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 236, Column 656: character "'" is not allowed in the value of attribute "id"
    …nput type="text" name="tdt[]" id="tdt_'+num+'"  size="10" onclick="dispCalenda…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 236, Column 846: character "'" is not allowed in the value of attribute "id"
    …E: <select name="fltype[]" id="fltype_'+num+'"><option value="R">Round Trip</o…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 236, Column 1012: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ration:none;font-weight:bold" onclick=removePopupSignupElement("'+divIdName+'"…
  • Error Line 236, Column 1036: an attribute value must be a literal unless it contains only name characters
    …t:bold" onclick=removePopupSignupElement("'+divIdName+'") >[Remove]</a></div>';

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 238, Column 33: character "+" is not allowed in the value of attribute "id"
    			newdiv.innerHTML = '<div id='+divIdName+' class="hotel_wid_txt"><div class="…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 238, Column 33: ID "+divIdName+" already defined
    			newdiv.innerHTML = '<div id='+divIdName+' class="hotel_wid_txt"><div class="…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 236, Column 39: ID "+divIdName+" first defined here
    			//newdiv.innerHTML = '<br><div id='+divIdName+' class="hotel_wid_txt">TO: <i…
  • Error Line 238, Column 67: document type does not allow element "div" here
    …id='+divIdName+' class="hotel_wid_txt"><div class="add_pan left_pad_0"><div cl…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 238, Column 214: character "'" is not allowed in the value of attribute "id"
    …"departure_city[]" id="departure_city_'+num+'" onKeyUp="countme(this.value,\'d…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 238, Column 199: ID "departure_city_'+num+'" already defined
    …g"><input name="departure_city[]" id="departure_city_'+num+'" onKeyUp="countme…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 236, Column 125: ID "departure_city_'+num+'" first defined here
    …pe="text" name="departure_city[]" id="departure_city_'+num+'" size="10" onKeyU…
  • Error Line 238, Column 458: character "'" is not allowed in the value of attribute "id"
    …ame="arrival_city[]" id="arrival_city_'+num+'" size="10" value="" onKeyUp="cou…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 238, Column 445: ID "arrival_city_'+num+'" already defined
    …type="text" name="arrival_city[]" id="arrival_city_'+num+'" size="10" value=""…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 236, Column 289: ID "arrival_city_'+num+'" first defined here
    …type="text" name="arrival_city[]" id="arrival_city_'+num+'" size="10" value=""…
  • Error Line 238, Column 709: character "'" is not allowed in the value of attribute "id"
    …nput type="text" name="fdt[]" id="fdt_'+num+'" onclick="dispCalendar(\'fdt_'+n…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 238, Column 705: ID "fdt_'+num+'" already defined
    …"><input type="text" name="fdt[]" id="fdt_'+num+'" onclick="dispCalendar(\'fdt…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 236, Column 457: ID "fdt_'+num+'" first defined here
    …: <input type="text" name="fdt[]" id="fdt_'+num+'" size="10"  onclick="dispCal…
  • Error Line 238, Column 987: character "'" is not allowed in the value of attribute "id"
    …nput type="text" name="tdt[]" id="tdt_'+num+'"  size="10" onclick="dispCalenda…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 238, Column 983: ID "tdt_'+num+'" already defined
    …"><input type="text" name="tdt[]" id="tdt_'+num+'"  size="10" onclick="dispCal…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 236, Column 652: ID "tdt_'+num+'" first defined here
    …E <input type="text" name="tdt[]" id="tdt_'+num+'"  size="10" onclick="dispCal…
  • Error Line 238, Column 1270: character "'" is not allowed in the value of attribute "id"
    …g"><select name="fltype[]" id="fltype_'+num+'"><option value="R">Round Trip</o…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 238, Column 1263: ID "fltype_'+num+'" already defined
    …input_bg"><select name="fltype[]" id="fltype_'+num+'"><option value="R">Round …

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 236, Column 839: ID "fltype_'+num+'" first defined here
    …RIP TYPE: <select name="fltype[]" id="fltype_'+num+'"><option value="R">Round …
  • Error Line 238, Column 1518: character "'" is not allowed in the value of attribute "id"
    …t" name="passengers[]" id="passengers_'+num+'"  size="10" /></div></div><div c…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 238, Column 1730: character "'" is not allowed in the value of attribute "id"
    …e="text" name="infants[]" id="infants_'+num+'"  size="10" /></div></div><br />…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 238, Column 1896: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ration:none;font-weight:bold" onclick=removePopupSignupElement("'+divIdName+'"…
  • Error Line 238, Column 1920: an attribute value must be a literal unless it contains only name characters
    …bold" onclick=removePopupSignupElement("'+divIdName+'")>[Remove]</a></div></di…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 258, Column 58: document type does not allow element "link" here
    <link rel="canonical" href="http://www.whatscheaper.com"/>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 259, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 198, Column 1: start tag was here
    <iframe id="calendar" style="DISPLAY: block; Z-INDEX: 100; LEFT: 64px; VISIBILI…
  • Error Line 273, Column 72: there is no attribute "fb:like:layout"
    …is_button_facebook_like" fb:like:layout="button_count" style="width:90px;"></a>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 280, Column 56: element "g:plusone" undefined
            <div style="float:right; width:auto"><g:plusone></g:plusone></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 365, Column 137: there is no attribute "allowtransparency"
    …nheight="0" marginwidth="30" frameborder="0" allowtransparency="true"></iframe>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 375, Column 7: required attribute "type" not specified
    <style>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 375, Column 7: document type does not allow element "style" here
    <style>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 383, Column 10: syntax of attribute value does not conform to declared value
    	<li id="" class="menutxt"><a href="http://www.whatscheaper.com/flight.php?uid=…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 384, Column 10: syntax of attribute value does not conform to declared value
    	<li id="" class="menutxt"><a href="http://www.whatscheaper.com/hotel.php?uid=5…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 385, Column 10: syntax of attribute value does not conform to declared value
    	<li id="" class="menutxt"><a href="http://www.whatscheaper.com/vacationpackage…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 385, Column 96: cannot generate system identifier for general entity "uid"
    …er.com/vacationpackage.php?ctype=QUg=&uid=511fbcc370e56">Vacation packages</a>…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 385, Column 96: general entity "uid" not defined and no default entity
    …er.com/vacationpackage.php?ctype=QUg=&uid=511fbcc370e56">Vacation packages</a>…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 385, Column 99: reference not terminated by REFC delimiter
    …com/vacationpackage.php?ctype=QUg=&uid=511fbcc370e56">Vacation packages</a></l…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 385, Column 99: reference to external entity in attribute value
    …com/vacationpackage.php?ctype=QUg=&uid=511fbcc370e56">Vacation packages</a></l…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 385, Column 99: reference to entity "uid" for which no system identifier could be generated
    …com/vacationpackage.php?ctype=QUg=&uid=511fbcc370e56">Vacation packages</a></l…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 385, Column 95: entity was defined here
    …per.com/vacationpackage.php?ctype=QUg=&uid=511fbcc370e56">Vacation packages</a…
  • Error Line 387, Column 10: syntax of attribute value does not conform to declared value
    	<li id="" class="menutxt">

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 388, Column 106: cannot generate system identifier for general entity "referrerId"
    …MerchandisingPage?DD=TRIPRESERVATIONS&referrerId=None&referrerId2=None&referre…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 388, Column 106: general entity "referrerId" not defined and no default entity
    …MerchandisingPage?DD=TRIPRESERVATIONS&referrerId=None&referrerId2=None&referre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 388, Column 116: reference not terminated by REFC delimiter
    …ingPage?DD=TRIPRESERVATIONS&referrerId=None&referrerId2=None&referrerId3=None&…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 388, Column 116: reference to external entity in attribute value
    …ingPage?DD=TRIPRESERVATIONS&referrerId=None&referrerId2=None&referrerId3=None&…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 388, Column 116: reference to entity "referrerId" for which no system identifier could be generated
    …ingPage?DD=TRIPRESERVATIONS&referrerId=None&referrerId2=None&referrerId3=None&…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 388, Column 105: entity was defined here
    …PMerchandisingPage?DD=TRIPRESERVATIONS&referrerId=None&referrerId2=None&referr…
  • Warning Line 388, Column 122: cannot generate system identifier for general entity "referrerId2"
    …e?DD=TRIPRESERVATIONS&referrerId=None&referrerId2=None&referrerId3=None&headTe…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 388, Column 122: general entity "referrerId2" not defined and no default entity
    …e?DD=TRIPRESERVATIONS&referrerId=None&referrerId2=None&referrerId3=None&headTe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 388, Column 133: reference not terminated by REFC delimiter
    …SERVATIONS&referrerId=None&referrerId2=None&referrerId3=None&headTemplate=Trip…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 388, Column 133: reference to external entity in attribute value
    …SERVATIONS&referrerId=None&referrerId2=None&referrerId3=None&headTemplate=Trip…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 388, Column 133: reference to entity "referrerId2" for which no system identifier could be generated
    …SERVATIONS&referrerId=None&referrerId2=None&referrerId3=None&headTemplate=Trip…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 388, Column 121: entity was defined here
    …ge?DD=TRIPRESERVATIONS&referrerId=None&referrerId2=None&referrerId3=None&headT…
  • Warning Line 388, Column 139: cannot generate system identifier for general entity "referrerId3"
    …IONS&referrerId=None&referrerId2=None&referrerId3=None&headTemplate=Tripreserv…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 388, Column 139: general entity "referrerId3" not defined and no default entity
    …IONS&referrerId=None&referrerId2=None&referrerId3=None&headTemplate=Tripreserv…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 388, Column 150: reference not terminated by REFC delimiter
    …erId=None&referrerId2=None&referrerId3=None&headTemplate=TripreservationsHead&…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 388, Column 150: reference to external entity in attribute value
    …erId=None&referrerId2=None&referrerId3=None&headTemplate=TripreservationsHead&…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 388, Column 150: reference to entity "referrerId3" for which no system identifier could be generated
    …erId=None&referrerId2=None&referrerId3=None&headTemplate=TripreservationsHead&…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 388, Column 138: entity was defined here
    …TIONS&referrerId=None&referrerId2=None&referrerId3=None&headTemplate=Tripreser…
  • Warning Line 388, Column 156: cannot generate system identifier for general entity "headTemplate"
    …one&referrerId2=None&referrerId3=None&headTemplate=TripreservationsHead&bodyTe…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 388, Column 156: general entity "headTemplate" not defined and no default entity
    …one&referrerId2=None&referrerId3=None&headTemplate=TripreservationsHead&bodyTe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 388, Column 168: reference not terminated by REFC delimiter
    …Id2=None&referrerId3=None&headTemplate=TripreservationsHead&bodyTemplate=Tripr…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 388, Column 168: reference to external entity in attribute value
    …Id2=None&referrerId3=None&headTemplate=TripreservationsHead&bodyTemplate=Tripr…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 388, Column 168: reference to entity "headTemplate" for which no system identifier could be generated
    …Id2=None&referrerId3=None&headTemplate=TripreservationsHead&bodyTemplate=Tripr…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 388, Column 155: entity was defined here
    …None&referrerId2=None&referrerId3=None&headTemplate=TripreservationsHead&bodyT…
  • Warning Line 388, Column 190: cannot generate system identifier for general entity "bodyTemplate"
    …one&headTemplate=TripreservationsHead&bodyTemplate=TripreservationsBody&isShow…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 388, Column 190: general entity "bodyTemplate" not defined and no default entity
    …one&headTemplate=TripreservationsHead&bodyTemplate=TripreservationsBody&isShow…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 388, Column 202: reference not terminated by REFC delimiter
    …late=TripreservationsHead&bodyTemplate=TripreservationsBody&isShowFramework=tr…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 388, Column 202: reference to external entity in attribute value
    …late=TripreservationsHead&bodyTemplate=TripreservationsBody&isShowFramework=tr…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 388, Column 202: reference to entity "bodyTemplate" for which no system identifier could be generated
    …late=TripreservationsHead&bodyTemplate=TripreservationsBody&isShowFramework=tr…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 388, Column 189: entity was defined here
    …None&headTemplate=TripreservationsHead&bodyTemplate=TripreservationsBody&isSho…
  • Warning Line 388, Column 224: cannot generate system identifier for general entity "isShowFramework"
    …ead&bodyTemplate=TripreservationsBody&isShowFramework=true&wt.mc_id=Tripreserv…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 388, Column 224: general entity "isShowFramework" not defined and no default entity
    …ead&bodyTemplate=TripreservationsBody&isShowFramework=true&wt.mc_id=Tripreserv…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 388, Column 239: reference not terminated by REFC delimiter
    …e=TripreservationsBody&isShowFramework=true&wt.mc_id=Tripreservations_PL_FN_De…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 388, Column 239: reference to external entity in attribute value
    …e=TripreservationsBody&isShowFramework=true&wt.mc_id=Tripreservations_PL_FN_De…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 388, Column 239: reference to entity "isShowFramework" for which no system identifier could be generated
    …e=TripreservationsBody&isShowFramework=true&wt.mc_id=Tripreservations_PL_FN_De…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 388, Column 223: entity was defined here
    …Head&bodyTemplate=TripreservationsBody&isShowFramework=true&wt.mc_id=Tripreser…
  • Warning Line 388, Column 245: cannot generate system identifier for general entity "wt.mc_id"
    …reservationsBody&isShowFramework=true&wt.mc_id=Tripreservations_PL_FN_Deals_tx…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 388, Column 245: general entity "wt.mc_id" not defined and no default entity
    …reservationsBody&isShowFramework=true&wt.mc_id=Tripreservations_PL_FN_Deals_tx…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 388, Column 253: reference not terminated by REFC delimiter
    …ionsBody&isShowFramework=true&wt.mc_id=Tripreservations_PL_FN_Deals_txt_021610…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 388, Column 253: reference to external entity in attribute value
    …ionsBody&isShowFramework=true&wt.mc_id=Tripreservations_PL_FN_Deals_txt_021610…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 388, Column 253: reference to entity "wt.mc_id" for which no system identifier could be generated
    …ionsBody&isShowFramework=true&wt.mc_id=Tripreservations_PL_FN_Deals_txt_021610…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 388, Column 244: entity was defined here
    …preservationsBody&isShowFramework=true&wt.mc_id=Tripreservations_PL_FN_Deals_t…
  • Error Line 389, Column 10: syntax of attribute value does not conform to declared value
    	<li id="" class="menutxt"><a href="http://www.whatscheaper.com/destinationguid…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 403, Column 75: end tag for "input" omitted, but OMITTAG NO was specified
    				<input type="hidden" name="log_id" value="0vsq1ii2mile93qo1jgdojt0f0">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 403, Column 5: start tag was here
    				<input type="hidden" name="log_id" value="0vsq1ii2mile93qo1jgdojt0f0">
  • Error Line 404, Column 69: end tag for "input" omitted, but OMITTAG NO was specified
    			<input name="siteid" id="siteid" type="hidden" value="WCF-None" >

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 404, Column 4: start tag was here
    			<input name="siteid" id="siteid" type="hidden" value="WCF-None" >
  • Error Line 406, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    			<input name="gkw" type="hidden" value="None" >

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 406, Column 4: start tag was here
    			<input name="gkw" type="hidden" value="None" >
  • Error Line 408, Column 54: end tag for "input" omitted, but OMITTAG NO was specified
    			<input name="gkwtype" type="hidden" value="None" >

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 408, Column 4: start tag was here
    			<input name="gkwtype" type="hidden" value="None" >
  • Error Line 415, Column 133: there is no attribute "onClick"
    …ype" id="bkflight" checked="checked" value="flight" onClick="callflightfrm()"/>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 457, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ss="radiobtn" id="fltype" onClick="roundtripfrm()" value="R"  checked=checked/>
  • Error Line 460, Column 60: ID "fltype" already defined
    …pe" type="radio" class="radiobtn" id="fltype" onClick="onewayfrm()" value="O" …

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 457, Column 72: ID "fltype" first defined here
    …pe" type="radio" class="radiobtn" id="fltype" onClick="roundtripfrm()" value="…
  • Error Line 476, Column 58: there is no attribute "onClick"
    …ript:void(0)" class="linktxt" onClick="javascript:popUp_personal_info('airport…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 487, Column 100: syntax of attribute value does not conform to declared value
    …datefields field2" id="fdt" readonly="" style="background:url(images/test.jpg)…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 487, Column 100: value of attribute "readonly" cannot be ""; must be one of "readonly"
    …datefields field2" id="fdt" readonly="" style="background:url(images/test.jpg)…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 496, Column 97: syntax of attribute value does not conform to declared value
    …datefields field2" id="tdt" readonly="" style="background:url(images/test.jpg)…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 496, Column 97: value of attribute "readonly" cannot be ""; must be one of "readonly"
    …datefields field2" id="tdt" readonly="" style="background:url(images/test.jpg)…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 531, Column 193: there is no attribute "onClick"
    …-left: 3px; margin-top: 2px;" onClick="dispCalendar('fdt0','fdt0','fdt0','',fa…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 565, Column 27: ID "cusValSeg_From1" already defined
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 529, Column 27: ID "cusValSeg_From1" first defined here
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…
  • Error Line 567, Column 52: ID "imgCal1" already defined
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 531, Column 52: ID "imgCal1" first defined here
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…
  • Error Line 568, Column 27: ID "rfvDate1" already defined
                    <span id="rfvDate1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 532, Column 27: ID "rfvDate1" first defined here
                    <span id="rfvDate1" style="color:Red;display:none;"></span>
  • Error Line 569, Column 27: ID "cvDOB1" already defined
                    <span id="cvDOB1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 533, Column 27: ID "cvDOB1" first defined here
                    <span id="cvDOB1" style="color:Red;display:none;"></span>
  • Error Line 605, Column 27: ID "cusValSeg_From1" already defined
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 529, Column 27: ID "cusValSeg_From1" first defined here
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…
  • Error Line 607, Column 52: ID "imgCal1" already defined
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 531, Column 52: ID "imgCal1" first defined here
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…
  • Error Line 608, Column 27: ID "rfvDate1" already defined
                    <span id="rfvDate1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 532, Column 27: ID "rfvDate1" first defined here
                    <span id="rfvDate1" style="color:Red;display:none;"></span>
  • Error Line 609, Column 27: ID "cvDOB1" already defined
                    <span id="cvDOB1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 533, Column 27: ID "cvDOB1" first defined here
                    <span id="cvDOB1" style="color:Red;display:none;"></span>
  • Error Line 648, Column 27: ID "cusValSeg_From1" already defined
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 529, Column 27: ID "cusValSeg_From1" first defined here
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…
  • Error Line 650, Column 52: ID "imgCal1" already defined
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 531, Column 52: ID "imgCal1" first defined here
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…
  • Error Line 651, Column 27: ID "rfvDate1" already defined
                    <span id="rfvDate1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 532, Column 27: ID "rfvDate1" first defined here
                    <span id="rfvDate1" style="color:Red;display:none;"></span>
  • Error Line 652, Column 27: ID "cvDOB1" already defined
                    <span id="cvDOB1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 533, Column 27: ID "cvDOB1" first defined here
                    <span id="cvDOB1" style="color:Red;display:none;"></span>
  • Error Line 691, Column 27: ID "cusValSeg_From1" already defined
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 529, Column 27: ID "cusValSeg_From1" first defined here
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…
  • Error Line 693, Column 52: ID "imgCal1" already defined
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 531, Column 52: ID "imgCal1" first defined here
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…
  • Error Line 694, Column 27: ID "rfvDate1" already defined
                    <span id="rfvDate1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 532, Column 27: ID "rfvDate1" first defined here
                    <span id="rfvDate1" style="color:Red;display:none;"></span>
  • Error Line 695, Column 27: ID "cvDOB1" already defined
                    <span id="cvDOB1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 533, Column 27: ID "cvDOB1" first defined here
                    <span id="cvDOB1" style="color:Red;display:none;"></span>
  • Error Line 734, Column 27: ID "cusValSeg_From1" already defined
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 529, Column 27: ID "cusValSeg_From1" first defined here
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…
  • Error Line 736, Column 52: ID "imgCal1" already defined
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 531, Column 52: ID "imgCal1" first defined here
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…
  • Error Line 737, Column 27: ID "rfvDate1" already defined
                    <span id="rfvDate1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 532, Column 27: ID "rfvDate1" first defined here
                    <span id="rfvDate1" style="color:Red;display:none;"></span>
  • Error Line 738, Column 27: ID "cvDOB1" already defined
                    <span id="cvDOB1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 533, Column 27: ID "cvDOB1" first defined here
                    <span id="cvDOB1" style="color:Red;display:none;"></span>
  • Error Line 777, Column 27: ID "cusValSeg_From1" already defined
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 529, Column 27: ID "cusValSeg_From1" first defined here
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…
  • Error Line 779, Column 52: ID "imgCal1" already defined
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 531, Column 52: ID "imgCal1" first defined here
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…
  • Error Line 780, Column 27: ID "rfvDate1" already defined
                    <span id="rfvDate1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 532, Column 27: ID "rfvDate1" first defined here
                    <span id="rfvDate1" style="color:Red;display:none;"></span>
  • Error Line 781, Column 27: ID "cvDOB1" already defined
                    <span id="cvDOB1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 533, Column 27: ID "cvDOB1" first defined here
                    <span id="cvDOB1" style="color:Red;display:none;"></span>
  • Error Line 820, Column 27: ID "cusValSeg_From1" already defined
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 529, Column 27: ID "cusValSeg_From1" first defined here
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…
  • Error Line 822, Column 52: ID "imgCal1" already defined
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 531, Column 52: ID "imgCal1" first defined here
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…
  • Error Line 823, Column 27: ID "rfvDate1" already defined
                    <span id="rfvDate1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 532, Column 27: ID "rfvDate1" first defined here
                    <span id="rfvDate1" style="color:Red;display:none;"></span>
  • Error Line 824, Column 27: ID "cvDOB1" already defined
                    <span id="cvDOB1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 533, Column 27: ID "cvDOB1" first defined here
                    <span id="cvDOB1" style="color:Red;display:none;"></span>
  • Error Line 863, Column 27: ID "cusValSeg_From1" already defined
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 529, Column 27: ID "cusValSeg_From1" first defined here
                    <span id="cusValSeg_From1" style="color:Red;display:none;"></sp…
  • Error Line 865, Column 52: ID "imgCal1" already defined
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 531, Column 52: ID "imgCal1" first defined here
    …   <img src="images/calendar.png" id="imgCal1" height="18" alt="Click here for…
  • Error Line 866, Column 27: ID "rfvDate1" already defined
                    <span id="rfvDate1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 532, Column 27: ID "rfvDate1" first defined here
                    <span id="rfvDate1" style="color:Red;display:none;"></span>
  • Error Line 867, Column 27: ID "cvDOB1" already defined
                    <span id="cvDOB1" style="color:Red;display:none;"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 533, Column 27: ID "cvDOB1" first defined here
                    <span id="cvDOB1" style="color:Red;display:none;"></span>
  • Error Line 895, Column 148: there is no attribute "onChange"
    …class="dropdown dpwidth_test" tabindex="50" onChange="set_total_passengers();">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 985, Column 43: ID "infants" already defined
    		<input type="hidden" name="infants" id="infants" value="" />

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 956, Column 70: ID "infants" first defined here
    …"radiotxt radiotxt3" style="width:75px;" id="infants">Infants&nbsp;(0-1):</div>
  • Error Line 1008, Column 64: value of attribute "id" invalid: "1" cannot start a name
    …<input type="checkbox" name="adv" id="182" onClick="popUp_info('BookingBuddy',…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1022, Column 64: value of attribute "id" invalid: "1" cannot start a name
    …<input type="checkbox" name="adv" id="196" onClick="popUp_info('TripAdvisor','…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1036, Column 64: value of attribute "id" invalid: "1" cannot start a name
    …<input type="checkbox" name="adv" id="156" onClick="popUp_info('Priceline','ht…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1050, Column 64: value of attribute "id" invalid: "2" cannot start a name
    …<input type="checkbox" name="adv" id="220" onClick="popUp_info('AtTravelDeals'…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1069, Column 16: there is no attribute "type"
        	<img type="image" src="images/lowestfares.gif" tabindex="54" onClick="retu…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1069, Column 62: there is no attribute "tabindex"
    …src="images/lowestfares.gif" tabindex="54" onClick="return validateFlightFrm(H…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1069, Column 137: required attribute "alt" not specified
    …ex="54" onClick="return validateFlightFrm(Http.Cache.GetNoCache,'divresult')"/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1103, Column 52: required attribute "alt" not specified
    	<img src="images//rightside-image.jpg" border="0"/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1113, Column 85: end tag for "br" omitted, but OMITTAG NO was specified
    …ootmid">5348 Vegas Dr #767, Las Vegas NV 89108 / Ph: 1-888-474-1232<br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1113, Column 81: start tag was here
    …ootmid">5348 Vegas Dr #767, Las Vegas NV 89108 / Ph: 1-888-474-1232<br><br><br>
  • Error Line 1113, Column 89: end tag for "br" omitted, but OMITTAG NO was specified
    …ootmid">5348 Vegas Dr #767, Las Vegas NV 89108 / Ph: 1-888-474-1232<br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1113, Column 85: start tag was here
    …ootmid">5348 Vegas Dr #767, Las Vegas NV 89108 / Ph: 1-888-474-1232<br><br><br>
  • Error Line 1113, Column 93: end tag for "br" omitted, but OMITTAG NO was specified
    …ootmid">5348 Vegas Dr #767, Las Vegas NV 89108 / Ph: 1-888-474-1232<br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1113, Column 89: start tag was here
    …ootmid">5348 Vegas Dr #767, Las Vegas NV 89108 / Ph: 1-888-474-1232<br><br><br>
  • Error Line 1124, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1124, Column 1: start tag was here
    <br><br><br>
  • Error Line 1124, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1124, Column 5: start tag was here
    <br><br><br>
  • Error Line 1124, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1124, Column 9: start tag was here
    <br><br><br>
  • Error Line 1125, Column 13: an attribute value must be a literal unless it contains only name characters
    <font color=#A9A9A9>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1126, Column 70: end tag for "br" omitted, but OMITTAG NO was specified
    Copyright &copy; 2009-2012 Whatscheaper.com. All rights reserved.<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1126, Column 66: start tag was here
    Copyright &copy; 2009-2012 Whatscheaper.com. All rights reserved.<br>
  • Error Line 1127, Column 70: end tag for "br" omitted, but OMITTAG NO was specified
    Trip Reservations Online, D/B/A Whatscheaper.com - CST 1001990-10<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1127, Column 66: start tag was here
    Trip Reservations Online, D/B/A Whatscheaper.com - CST 1001990-10<br>
  • Error Line 1152, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br><br><br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1152, Column 1: start tag was here
    <br><br><br><br><br><br><br>
  • Error Line 1152, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br><br><br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1152, Column 5: start tag was here
    <br><br><br><br><br><br><br>
  • Error Line 1152, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br><br><br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1152, Column 9: start tag was here
    <br><br><br><br><br><br><br>
  • Error Line 1152, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br><br><br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1152, Column 13: start tag was here
    <br><br><br><br><br><br><br>
  • Error Line 1152, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br><br><br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1152, Column 17: start tag was here
    <br><br><br><br><br><br><br>
  • Error Line 1152, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br><br><br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1152, Column 21: start tag was here
    <br><br><br><br><br><br><br>
  • Error Line 1152, Column 29: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br><br><br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1152, Column 25: start tag was here
    <br><br><br><br><br><br><br>
  • Error Line 1153, Column 152: end tag for "br" omitted, but OMITTAG NO was specified
    …="0" marginwidth="0" frameborder="0" allowtransparency="true"></iframe><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1153, Column 148: start tag was here
    …="0" marginwidth="0" frameborder="0" allowtransparency="true"></iframe><br><br>
  • Error Line 1153, Column 156: end tag for "br" omitted, but OMITTAG NO was specified
    …="0" marginwidth="0" frameborder="0" allowtransparency="true"></iframe><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1153, Column 152: start tag was here
    …="0" marginwidth="0" frameborder="0" allowtransparency="true"></iframe><br><br>

Visitor Analysis

Daily Visitor
  • 5.250 visits
Daily Visitor