II►Yakaz is the search engine for all local classified ads on the web. Cars, motorbikes, housing, ... : quickly find all classifieds that match your search on the web. ...

yakaz.com
  • Domain Name
    yakaz.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #8550
  • Page Size
    63.7 KB
  • Ip Address
    78.24.131.87
  • Heading
    H1: 1, H2: 8, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 0 JPG, 1 PNG

Website Meta Analysis

  • Title
    Classified ads - Yakaz
  • Meta Keyword
  • Meta Description
    II►Yakaz is the search engine for all local classified ads on the web. Cars, motorbikes, housing, ... : quickly find all classifieds that match your search on the web.

Technical Analysis

  • Webserver
    Yakaz Web Server
  • Ip Address
    78.24.131.87
  • Domain Age
    7 Years, 6 Months, 23 days.
  • Javascript Library
    yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Yakaz Web Server
  • date: Sat, 02 Mar 2013 07:10:57 GMT
  • content-length: 16797
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • age: 170
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for yakaz.com

IP 78.24.131.87 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 78.24.131.87

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 146 Errors
  • 38 Warnings
Ratio Text/Html
  • 0.3196067605288181
Message Error
  • Warning Line 45, Column 89: cannot generate system identifier for general entity "cc"
    ….href = Yakaz.countryUri(cc) + '/results.php?gid=' + placeMarkId + '&cc=' + cc;

    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 "&" (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 æ 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 45, Column 89: general entity "cc" not defined and no default entity
    ….href = Yakaz.countryUri(cc) + '/results.php?gid=' + placeMarkId + '&cc=' + cc;

    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 45, Column 91: reference not terminated by REFC delimiter
    ….href = Yakaz.countryUri(cc) + '/results.php?gid=' + placeMarkId + '&cc=' + cc;

    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.

  • Error Line 45, Column 91: reference to entity "cc" for which no system identifier could be generated
    ….href = Yakaz.countryUri(cc) + '/results.php?gid=' + placeMarkId + '&cc=' + cc;

    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 45, Column 88: entity was defined here
    ….href = Yakaz.countryUri(cc) + '/results.php?gid=' + placeMarkId + '&cc=' + cc;
  • Error Line 59, Column 10: required attribute "type" not specified
      <script>document.write("<div id='nav-bar' class='loggedOut'><ul id=\"loggedIn…

    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 59, Column 62: document type does not allow element "div" here
    …e("<div id='nav-bar' class='loggedOut'><ul id=\"loggedInNav\" style=\"display:…

    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 59, Column 70: an attribute value must be a literal unless it contains only name characters
    …id='nav-bar' class='loggedOut'><ul id=\"loggedInNav\" style=\"display:none;\">…

    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 59, Column 70: character "\" is not allowed in the value of attribute "id"
    …id='nav-bar' class='loggedOut'><ul id=\"loggedInNav\" style=\"display:none;\">…

    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 59, Column 92: an attribute value must be a literal unless it contains only name characters
    …ggedOut'><ul id=\"loggedInNav\" style=\"display:none;\"><span id=\"navTools\">…

    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 59, Column 119: an attribute value must be a literal unless it contains only name characters
    …av\" style=\"display:none;\"><span id=\"navTools\"><span class=\"navToolsWrite…

    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 59, Column 119: character "\" is not allowed in the value of attribute "id"
    …av\" style=\"display:none;\"><span id=\"navTools\"><span class=\"navToolsWrite…

    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 59, Column 131: document type does not allow element "span" here; assuming missing "li" start-tag
    …"display:none;\"><span id=\"navTools\"><span class=\"navToolsWrite\"><a href=\…
  • Error Line 59, Column 144: an attribute value must be a literal unless it contains only name characters
    …;\"><span id=\"navTools\"><span class=\"navToolsWrite\"><a href=\"/results.php…

    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 59, Column 170: an attribute value must be a literal unless it contains only name characters
    …<span class=\"navToolsWrite\"><a href=\"/results.php?postAd=1\" onclick=\"if(Y…

    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 59, Column 204: an attribute value must be a literal unless it contains only name characters
    …ref=\"/results.php?postAd=1\" onclick=\"if(Yakaz.QuickAdBox){Yakaz.QuickAdBox.…

    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 59, Column 271: "false" is not a member of a group specified for any attribute
    …QuickAdBox.writeDefault();return false;}\" class=\"yakazButton orangeBtn tinyB…
  • Error Line 59, Column 282: an attribute value must be a literal unless it contains only name characters
    …writeDefault();return false;}\" class=\"yakazButton orangeBtn tinyBtn\" title=…

    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 59, Column 306: "orangeBtn" is not a member of a group specified for any attribute
    …lse;}\" class=\"yakazButton orangeBtn tinyBtn\" title=\"Write a post\"><span c…
  • Error Line 59, Column 313: "tinyBtn" is not a member of a group specified for any attribute
    … class=\"yakazButton orangeBtn tinyBtn\" title=\"Write a post\"><span class=\"…
  • Error Line 59, Column 322: an attribute value must be a literal unless it contains only name characters
    …yakazButton orangeBtn tinyBtn\" title=\"Write a post\"><span class=\"navBarQui…

    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 59, Column 332: "a" is not a member of a group specified for any attribute
    …n orangeBtn tinyBtn\" title=\"Write a post\"><span class=\"navBarQuickWrite ed…
  • Error Line 59, Column 336: "post" is not a member of a group specified for any attribute
    …angeBtn tinyBtn\" title=\"Write a post\"><span class=\"navBarQuickWrite editWh…
  • Error Line 59, Column 351: an attribute value must be a literal unless it contains only name characters
    …\" title=\"Write a post\"><span class=\"navBarQuickWrite editWhiteIcon de\"></…

    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 59, Column 384: "editWhiteIcon" is not a member of a group specified for any attribute
    …lass=\"navBarQuickWrite editWhiteIcon de\"></span></a></span><span class=\"nav…
  • Error Line 59, Column 386: "de" is not a member of a group specified for any attribute
    …ss=\"navBarQuickWrite editWhiteIcon de\"></span></a></span><span class=\"navTo…
  • Error Line 59, Column 419: an attribute value must be a literal unless it contains only name characters
    …on de\"></span></a></span><span class=\"navToolsBtn\"> <span class=\"navBarArr…

    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 59, Column 448: an attribute value must be a literal unless it contains only name characters
    …an class=\"navToolsBtn\"> <span class=\"navBarArrow\"></span></span> <ul class…

    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 59, Column 489: an attribute value must be a literal unless it contains only name characters
    …avBarArrow\"></span></span> <ul class=\"navSubTools hide\"><li><a id=\"btnSett…

    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 59, Column 507: "hide" is not a member of a group specified for any attribute
    …n></span> <ul class=\"navSubTools hide\"><li><a id=\"btnSettings1\" href=\"htt…
  • Error Line 59, Column 509: document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …</span> <ul class=\"navSubTools hide\"><li><a id=\"btnSettings1\" href=\"https…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 59, Column 520: an attribute value must be a literal unless it contains only name characters
    … class=\"navSubTools hide\"><li><a id=\"btnSettings1\" href=\"https://www.yaka…

    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 59, Column 520: character "\" is not allowed in the value of attribute "id"
    … class=\"navSubTools hide\"><li><a id=\"btnSettings1\" href=\"https://www.yaka…

    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 59, Column 542: an attribute value must be a literal unless it contains only name characters
    …ide\"><li><a id=\"btnSettings1\" href=\"https://www.yakaz.com/account/settings…

    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 59, Column 649: an attribute value must be a literal unless it contains only name characters
    …\">Profile settings</a></li><li><a id=\"btnSettings2\" href=\"https://www.yaka…

    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 59, Column 649: character "\" is not allowed in the value of attribute "id"
    …\">Profile settings</a></li><li><a id=\"btnSettings2\" href=\"https://www.yaka…

    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 59, Column 671: an attribute value must be a literal unless it contains only name characters
    …></li><li><a id=\"btnSettings2\" href=\"https://www.yakaz.com/account/settings…

    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 59, Column 778: an attribute value must be a literal unless it contains only name characters
    …\">Privacy settings</a></li><li><a id=\"btnSignOut\" href=\"/account/signout.p…

    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 59, Column 778: character "\" is not allowed in the value of attribute "id"
    …\">Privacy settings</a></li><li><a id=\"btnSignOut\" href=\"/account/signout.p…

    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 59, Column 798: an attribute value must be a literal unless it contains only name characters
    …/a></li><li><a id=\"btnSignOut\" href=\"/account/signout.php?scheme=http\">Sig…

    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 59, Column 868: end tag for "li" omitted, but OMITTAG NO was specified
    …tp\">Sign out</a></li></ul></span></ul> <ul id=\"notLoggedInNav\"><li><a id=\"…

    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 59, Column 110: start tag was here
    …loggedInNav\" style=\"display:none;\"><span id=\"navTools\"><span class=\"navT…
  • Error Line 59, Column 877: an attribute value must be a literal unless it contains only name characters
    … out</a></li></ul></span></ul> <ul id=\"notLoggedInNav\"><li><a id=\"btnSignUp…

    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 59, Column 877: character "\" is not allowed in the value of attribute "id"
    … out</a></li></ul></span></ul> <ul id=\"notLoggedInNav\"><li><a id=\"btnSignUp…

    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 59, Column 906: an attribute value must be a literal unless it contains only name characters
    …> <ul id=\"notLoggedInNav\"><li><a id=\"btnSignUp\" href=\"https://www.yakaz.c…

    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 59, Column 906: character "\" is not allowed in the value of attribute "id"
    …> <ul id=\"notLoggedInNav\"><li><a id=\"btnSignUp\" href=\"https://www.yakaz.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 59, Column 925: an attribute value must be a literal unless it contains only name characters
    …dInNav\"><li><a id=\"btnSignUp\" href=\"https://www.yakaz.com/account/newaccou…

    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 59, Column 1039: an attribute value must be a literal unless it contains only name characters
    …ooks=1\">Join Yakaz</a></li><li class=\"sep\">|</li><li><a id=\"btnSignIn\" hr…

    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 59, Column 1063: an attribute value must be a literal unless it contains only name characters
    …/li><li class=\"sep\">|</li><li><a id=\"btnSignIn\" href=\"https://www.yakaz.c…

    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 59, Column 1063: character "\" is not allowed in the value of attribute "id"
    …/li><li class=\"sep\">|</li><li><a id=\"btnSignIn\" href=\"https://www.yakaz.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 59, Column 1082: an attribute value must be a literal unless it contains only name characters
    …\">|</li><li><a id=\"btnSignIn\" href=\"https://www.yakaz.com/account/signin.p…

    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 59, Column 1177: an attribute value must be a literal unless it contains only name characters
    …=US&il=en\">Sign in</a></li><li class=\"sep\">|</li><li><form name='il' method…

    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 59, Column 1247: required attribute "action" not specified
    …' method='get' id='languageSelectForm'><span class='titleLang'>Language: </spa…

    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 59, Column 1681: an attribute value must be a literal unless it contains only name characters
    …i</option><option value='en' selected=\"selected\">English</option><option val…

    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 59, Column 1681: character "\" is not allowed in the value of attribute "selected"
    …i</option><option value='en' selected=\"selected\">English</option><option val…

    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 59, Column 1681: value of attribute "selected" cannot be "\"selected\""; must be one of "selected"
    …i</option><option value='en' selected=\"selected\">English</option><option val…

    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 79, Column 88: there is no attribute "autocomplete"
    …hInput" maxlength="2048" autocomplete="off" value="" name="what" spellcheck="f…

    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 79, Column 126: there is no attribute "spellcheck"
    …"off" value="" name="what" spellcheck="false" tabindex="1" placeholder="Search…

    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 79, Column 159: there is no attribute "placeholder"
    …ff" value="" name="what" spellcheck="false" tabindex="1" placeholder="Search"/>

    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 99, Column 106: there is no attribute "href"
    … orageBtn smallBtn switchPeople" href="/neighbors/"  onclick="if(Yakaz.SearchS…

    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 106, Column 8: end tag for "tbody" omitted, but OMITTAG NO was specified
    </table>

    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 74, Column 1: start tag was here
    <tbody>
  • Warning Line 108, Column 53: cannot generate system identifier for general entity "from"
    …"http://us.yakaz.com/results.php?av=1&from=form&cc=US" class="indexAdvSearch" …

    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 108, Column 53: general entity "from" not defined and no default entity
    …"http://us.yakaz.com/results.php?av=1&from=form&cc=US" class="indexAdvSearch" …

    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 108, Column 57: reference not terminated by REFC delimiter
    …p://us.yakaz.com/results.php?av=1&from=form&cc=US" class="indexAdvSearch" titl…

    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 108, Column 57: reference to external entity in attribute value
    …p://us.yakaz.com/results.php?av=1&from=form&cc=US" class="indexAdvSearch" titl…

    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 108, Column 57: reference to entity "from" for which no system identifier could be generated
    …p://us.yakaz.com/results.php?av=1&from=form&cc=US" class="indexAdvSearch" titl…

    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 108, Column 52: entity was defined here
    …="http://us.yakaz.com/results.php?av=1&from=form&cc=US" class="indexAdvSearch"…
  • Warning Line 108, Column 65: reference not terminated by REFC delimiter
    …akaz.com/results.php?av=1&from=form&cc=US" class="indexAdvSearch" title="Searc…

    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 108, Column 65: reference to external entity in attribute value
    …akaz.com/results.php?av=1&from=form&cc=US" class="indexAdvSearch" title="Searc…

    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 108, Column 65: reference to entity "cc" for which no system identifier could be generated
    …akaz.com/results.php?av=1&from=form&cc=US" class="indexAdvSearch" title="Searc…

    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 45, Column 88: entity was defined here
    ….href = Yakaz.countryUri(cc) + '/results.php?gid=' + placeMarkId + '&cc=' + cc;
  • Error Line 121, Column 85: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …a href='http://housing.yakaz.com/'><h2>Housing</h2></a></li><li><a href='http:…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 121, Column 147: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …i><a href='http://cars.yakaz.com/'><h2>Cars</h2></a></li><li><a href='http://m…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 121, Column 213: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ef='http://motorcycles.yakaz.com/'><h2>Motorbikes</h2></a></li><li><a href='ht…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 121, Column 278: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …i><a href='http://jobs.yakaz.com/'><h2>Jobs</h2></a></li><li><a href='http://f…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 121, Column 341: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … href='http://for-sale.yakaz.com/'><h2>For sale</h2></a></li><li><a href='http…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 137, Column 1369: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Independence<\/span> 640…

    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 137, Column 1384: document type does not allow element "span" here
    …ormatted":"<span class=\"placeNameHl\">Independence<\/span> 64052, MO, United …

    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).

  • Warning Line 137, Column 1397: character "<" is the first character of a delimiter but occurred as data
    …pan class=\"placeNameHl\">Independence<\/span> 64052, MO, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 3036: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Marysville<\/span> 43040…

    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.

  • Warning Line 137, Column 3062: character "<" is the first character of a delimiter but occurred as data
    …<span class=\"placeNameHl\">Marysville<\/span> 43040, OH, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 4669: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Hollywood<\/span> 90028,…

    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.

  • Warning Line 137, Column 4694: character "<" is the first character of a delimiter but occurred as data
    …"<span class=\"placeNameHl\">Hollywood<\/span> 90028, CA, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 6276: an attribute value must be a literal unless it contains only name characters
    …tly Used Fresh Water Boats at <a href=\"http:\/\/www.imageboats.com\/\" title=…

    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 137, Column 6316: an attribute value must be a literal unless it contains only name characters
    …http:\/\/www.imageboats.com\/\" title=\"http \/\/imageboats.com\/\" rel=\"nofo…

    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 137, Column 6323: character "\" not allowed in attribute specification list
    …\/www.imageboats.com\/\" title=\"http \/\/imageboats.com\/\" rel=\"nofollow\" …
  • Warning Line 137, Column 6411: character "<" is the first character of a delimiter but occurred as data
    …blank\">http:\/\/www.ImageBoats.com...<\/a>","commentCount":0,"commentList":[]…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 6835: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Henderson<\/span> 89011,…

    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.

  • Warning Line 137, Column 6860: character "<" is the first character of a delimiter but occurred as data
    …"<span class=\"placeNameHl\">Henderson<\/span> 89011, NV, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 8839: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Westminster<\/span> 8003…

    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.

  • Warning Line 137, Column 8866: character "<" is the first character of a delimiter but occurred as data
    …span class=\"placeNameHl\">Westminster<\/span> 80030, CO, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 11432: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Henderson<\/span> 42420,…

    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.

  • Warning Line 137, Column 11457: character "<" is the first character of a delimiter but occurred as data
    …"<span class=\"placeNameHl\">Henderson<\/span> 42420, KY, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 12996: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Chatsworth<\/span> 30705…

    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.

  • Warning Line 137, Column 13022: character "<" is the first character of a delimiter but occurred as data
    …<span class=\"placeNameHl\">Chatsworth<\/span> 30705, GA, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 15700: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Gilmer<\/span> 75644, TX…

    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.

  • Warning Line 137, Column 15722: character "<" is the first character of a delimiter but occurred as data
    …d":"<span class=\"placeNameHl\">Gilmer<\/span> 75644, TX, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 17536: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Medford Lakes<\/span> 08…

    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.

  • Warning Line 137, Column 17565: character "<" is the first character of a delimiter but occurred as data
    …an class=\"placeNameHl\">Medford Lakes<\/span> 08055, NJ, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 20725: an attribute value must be a literal unless it contains only name characters
    … haulers, just to name a few. <a href=\"http:\/\/www.cdlrentaltx.com\/\" title…

    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 137, Column 20766: an attribute value must be a literal unless it contains only name characters
    …ttp:\/\/www.cdlrentaltx.com\/\" title=\"cdl Rental tx - Commercial Drivers Lic…

    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 137, Column 20779: "Rental" is not a member of a group specified for any attribute
    …dlrentaltx.com\/\" title=\"cdl Rental tx - Commercial Drivers License Training…
  • Error Line 137, Column 20782: "tx" is not a member of a group specified for any attribute
    …entaltx.com\/\" title=\"cdl Rental tx - Commercial Drivers License Training We…
  • Error Line 137, Column 20782: "-" is not a member of a group specified for any attribute
    …entaltx.com\/\" title=\"cdl Rental tx - Commercial Drivers License Training We…
  • Error Line 137, Column 20795: "Commercial" is not a member of a group specified for any attribute
    …\" title=\"cdl Rental tx - Commercial Drivers License Training Weatherford, tx…
  • Error Line 137, Column 20803: "Drivers" is not a member of a group specified for any attribute
    …=\"cdl Rental tx - Commercial Drivers License Training Weatherford, tx 76086 c…
  • Error Line 137, Column 20811: "License" is not a member of a group specified for any attribute
    …ental tx - Commercial Drivers License Training Weatherford, tx 76086 cdl, cdl …
  • Error Line 137, Column 20820: "Training" is not a member of a group specified for any attribute
    …- Commercial Drivers License Training Weatherford, tx 76086 cdl, cdl test, cdl…
  • Error Line 137, Column 20831: "Weatherford" is not a member of a group specified for any attribute
    …l Drivers License Training Weatherford, tx 76086 cdl, cdl test, cdl ...\" rel=…
  • Error Line 137, Column 20836: "tx" is not a member of a group specified for any attribute
    …vers License Training Weatherford, tx 76086 cdl, cdl test, cdl ...\" rel=\"nof…
  • Error Line 137, Column 20836: "76086" is not a member of a group specified for any attribute
    …vers License Training Weatherford, tx 76086 cdl, cdl test, cdl ...\" rel=\"nof…
  • Error Line 137, Column 20845: "cdl" is not a member of a group specified for any attribute
    …nse Training Weatherford, tx 76086 cdl, cdl test, cdl ...\" rel=\"nofollow\" t…
  • Error Line 137, Column 20851: "cdl" is not a member of a group specified for any attribute
    …aining Weatherford, tx 76086 cdl, cdl test, cdl ...\" rel=\"nofollow\" target=…
  • Error Line 137, Column 20855: "test" is not a member of a group specified for any attribute
    …ng Weatherford, tx 76086 cdl, cdl test, cdl ...\" rel=\"nofollow\" target=\"_b…
  • Error Line 137, Column 20861: "cdl" is not a member of a group specified for any attribute
    …therford, tx 76086 cdl, cdl test, cdl ...\" rel=\"nofollow\" target=\"_blank\"…
  • Error Line 137, Column 20861: "..." is not a member of a group specified for any attribute
    …therford, tx 76086 cdl, cdl test, cdl ...\" rel=\"nofollow\" target=\"_blank\"…
  • Error Line 137, Column 20871: an attribute value must be a literal unless it contains only name characters
    …tx 76086 cdl, cdl test, cdl ...\" rel=\"nofollow\" target=\"_blank\">http:\/\/…

    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 137, Column 20891: an attribute value must be a literal unless it contains only name characters
    …st, cdl ...\" rel=\"nofollow\" target=\"_blank\">http:\/\/www.cdlrentaltx.com.…

    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 137, Column 20891: character "\" is not allowed in the value of attribute "target"
    …st, cdl ...\" rel=\"nofollow\" target=\"_blank\">http:\/\/www.cdlrentaltx.com.…

    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.

  • Warning Line 137, Column 20933: character "<" is the first character of a delimiter but occurred as data
    …lank\">http:\/\/www.cdlrentaltx.com...<\/a> 817-594-5378","commentCount":0,"co…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 21361: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Weatherford<\/span> 7608…

    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.

  • Warning Line 137, Column 21388: character "<" is the first character of a delimiter but occurred as data
    …span class=\"placeNameHl\">Weatherford<\/span> 76086, TX, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 22896: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Lambertville<\/span> 481…

    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.

  • Warning Line 137, Column 22924: character "<" is the first character of a delimiter but occurred as data
    …pan class=\"placeNameHl\">Lambertville<\/span> 48144, MI, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 24632: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Plainfield<\/span> 60544…

    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.

  • Warning Line 137, Column 24658: character "<" is the first character of a delimiter but occurred as data
    …<span class=\"placeNameHl\">Plainfield<\/span> 60544, IL, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 27755: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Spokane<\/span> 99201, W…

    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.

  • Warning Line 137, Column 27778: character "<" is the first character of a delimiter but occurred as data
    …":"<span class=\"placeNameHl\">Spokane<\/span> 99201, WA, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 29384: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Terry<\/span> 39170, MS,…

    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.

  • Warning Line 137, Column 29405: character "<" is the first character of a delimiter but occurred as data
    …ed":"<span class=\"placeNameHl\">Terry<\/span> 39170, MS, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 32504: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Kerman<\/span> 93630, CA…

    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.

  • Warning Line 137, Column 32526: character "<" is the first character of a delimiter but occurred as data
    …d":"<span class=\"placeNameHl\">Kerman<\/span> 93630, CA, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 34645: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Glendora<\/span> 91740, …

    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.

  • Warning Line 137, Column 34669: character "<" is the first character of a delimiter but occurred as data
    …:"<span class=\"placeNameHl\">Glendora<\/span> 91740, CA, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 137, Column 36428: an attribute value must be a literal unless it contains only name characters
    …"placeMark":{"formatted":"<span class=\"placeNameHl\">Dallas<\/span> 75244, TX…

    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.

  • Warning Line 137, Column 36450: character "<" is the first character of a delimiter but occurred as data
    …d":"<span class=\"placeNameHl\">Dallas<\/span> 75244, TX, United States","bin"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 36416: start tag was here
    …icon":false,"placeMark":{"formatted":"<span class=\"placeNameHl\">Dallas<\/spa…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 34633: start tag was here
    …icon":false,"placeMark":{"formatted":"<span class=\"placeNameHl\">Glendora<\/s…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 32492: start tag was here
    …icon":false,"placeMark":{"formatted":"<span class=\"placeNameHl\">Kerman<\/spa…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 29372: start tag was here
    …icon":false,"placeMark":{"formatted":"<span class=\"placeNameHl\">Terry<\/span…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 27743: start tag was here
    …icon":false,"placeMark":{"formatted":"<span class=\"placeNameHl\">Spokane<\/sp…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 24620: start tag was here
    …_icon":true,"placeMark":{"formatted":"<span class=\"placeNameHl\">Plainfield<\…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 22884: start tag was here
    …_icon":true,"placeMark":{"formatted":"<span class=\"placeNameHl\">Lambertville…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 21349: start tag was here
    …icon":false,"placeMark":{"formatted":"<span class=\"placeNameHl\">Weatherford<…
  • Error Line 138, Column 9: end tag for "a" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 20717: start tag was here
    …d, water haulers, just to name a few. <a href=\"http:\/\/www.cdlrentaltx.com\/…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 17524: start tag was here
    …_icon":true,"placeMark":{"formatted":"<span class=\"placeNameHl\">Medford Lake…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 15688: start tag was here
    …_icon":true,"placeMark":{"formatted":"<span class=\"placeNameHl\">Gilmer<\/spa…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 12984: start tag was here
    …icon":false,"placeMark":{"formatted":"<span class=\"placeNameHl\">Chatsworth<\…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 11420: start tag was here
    …icon":false,"placeMark":{"formatted":"<span class=\"placeNameHl\">Henderson<\/…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 8827: start tag was here
    …icon":false,"placeMark":{"formatted":"<span class=\"placeNameHl\">Westminster<…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 6823: start tag was here
    …icon":false,"placeMark":{"formatted":"<span class=\"placeNameHl\">Henderson<\/…
  • Error Line 138, Column 9: end tag for "a" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 6268: start tag was here
    …More Gently Used Fresh Water Boats at <a href=\"http:\/\/www.imageboats.com\/\…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 4657: start tag was here
    …_icon":true,"placeMark":{"formatted":"<span class=\"placeNameHl\">Hollywood<\/…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 3024: start tag was here
    …_icon":true,"placeMark":{"formatted":"<span class=\"placeNameHl\">Marysville<\…
  • Error Line 138, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
    </script>

    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 137, Column 1357: start tag was here
    …icon":false,"placeMark":{"formatted":"<span class=\"placeNameHl\">Independence…
  • Error Line 145, Column 569: required attribute "alt" not specified
    …/t.1361751897" width="38" height="38"/></span><span class="username de"><span …

    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 156, Column 565: required attribute "alt" not specified
    …ot/size.38x38" width="38" height="38"/></span><span class="username de"><span …

    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 167, Column 572: required attribute "alt" not specified
    …/t.1362203005" width="38" height="38"/></span><span class="username de"><span …

    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 180, Column 57: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …class="indexSignin"><form method="POST" action="https://www.yakaz.com/account/…

    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 187, Column 76: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="submit" class="yakazButton greenBtn smallBtn" value="Sign in">

    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 187, Column 1: start tag was here
    <input type="submit" class="yakazButton greenBtn smallBtn" value="Sign in">
  • Error Line 188, Column 78: end tag for "input" omitted, but OMITTAG NO was specified
    <span><input type="checkbox" checked="checked" id="remember" name="remember">

    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 188, Column 7: start tag was here
    <span><input type="checkbox" checked="checked" id="remember" name="remember">
  • Warning Line 206, Column 61: cannot generate system identifier for general entity "scheme"
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";

    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 206, Column 61: general entity "scheme" not defined and no default entity
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";

    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 206, Column 67: reference not terminated by REFC delimiter
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";

    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.

  • Error Line 206, Column 67: reference to entity "scheme" for which no system identifier could be generated
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";

    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 206, Column 60: entity was defined here
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";
  • Warning Line 206, Column 75: reference not terminated by REFC delimiter
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";

    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.

  • Error Line 206, Column 75: reference to entity "cc" for which no system identifier could be generated
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";

    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 45, Column 88: entity was defined here
    ….href = Yakaz.countryUri(cc) + '/results.php?gid=' + placeMarkId + '&cc=' + cc;
  • Warning Line 206, Column 79: cannot generate system identifier for general entity "il"
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";

    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 206, Column 79: general entity "il" not defined and no default entity
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";

    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 206, Column 81: reference not terminated by REFC delimiter
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";

    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.

  • Error Line 206, Column 81: reference to entity "il" for which no system identifier could be generated
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";

    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 206, Column 78: entity was defined here
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";
  • Error Line 216, Column 71: end tag for "img" omitted, but OMITTAG NO was specified
    <img src="/img/gg-favicon-22.png" alt="Google" height="22" width="22">

    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 216, Column 1: start tag was here
    <img src="/img/gg-favicon-22.png" alt="Google" height="22" width="22">
  • Error Line 220, Column 49: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …class="indexSignup"><form method="POST" action="https://www.yakaz.com/account/…

    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.

  • Warning Line 220, Column 118: reference not terminated by REFC delimiter
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">

    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 220, Column 118: reference to external entity in attribute value
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">

    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 220, Column 118: reference to entity "cc" for which no system identifier could be generated
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">

    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 45, Column 88: entity was defined here
    ….href = Yakaz.countryUri(cc) + '/results.php?gid=' + placeMarkId + '&cc=' + cc;
  • Warning Line 220, Column 124: reference not terminated by REFC delimiter
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">

    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 220, Column 124: reference to external entity in attribute value
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">

    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 220, Column 124: reference to entity "il" for which no system identifier could be generated
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">

    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 206, Column 78: entity was defined here
    …"https://www.yakaz.com/frame/facebookFrame.php?nobg=a&scheme=http&cc=US&il=en";
  • Warning Line 220, Column 128: cannot generate system identifier for general entity "showhooks"
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">

    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 220, Column 128: general entity "showhooks" not defined and no default entity
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">

    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 220, Column 137: reference not terminated by REFC delimiter
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">

    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 220, Column 137: reference to external entity in attribute value
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">

    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 220, Column 137: reference to entity "showhooks" for which no system identifier could be generated
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">

    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 220, Column 127: entity was defined here
    …ps://www.yakaz.com/account/newaccount.php?scheme=http&cc=US&il=en&showhooks=0">
  • Error Line 230, Column 63: end tag for "input" omitted, but OMITTAG NO was specified
      <input id="signupPm" type="hidden" value="" name="signupPm">

    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 230, Column 3: start tag was here
      <input id="signupPm" type="hidden" value="" name="signupPm">
  • Error Line 232, Column 78: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="submit" class="yakazButton blueBtn smallBtn" value="Join Yakaz">

    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 232, Column 1: start tag was here
    <input type="submit" class="yakazButton blueBtn smallBtn" value="Join Yakaz">
  • Error Line 245, Column 482: required attribute "alt" not specified
    …tp://www.yakaz.com/img/b_loading.gif"/></center></div><div id="languageSelecto…

    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 245, Column 828: required attribute "alt" not specified
    …height="32" src="http://www.yakaz.com/img/b_loading.gif"/></center></div></div>

    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>.

Visitor Analysis

Daily Visitor
  • 25.667 visits
Daily Visitor