Latest Hindi Movies Online Free, Bollywood Movies, Hindi Movies Dubbed In Hindi A big collection of Bollywood Movies online for free ...

join4movies.com
  • Domain Name
    join4movies.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #17325
  • Page Size
    60.9 KB
  • Ip Address
    188.165.254.204
  • Heading
    H1: 0, H2: 20, H3: 3, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 1 JPG, 1 PNG

Website Meta Analysis

  • Title
    Watch Hindi movies from latest to old online in High quality for free
  • Meta Keyword
    watch hindi movies online,online,watch online hindi movies,hindi movies free,latest hindi movies,latest hindi movies online,online latest movies,hindi online movie,online movies for free,hindi movies online high quality,high quality hindi movies,old movies online,old hindi movies online,bollywood movies online,watch bollywood mvoies online,watch india movies online,india movies online,online bollywood movies,hindi movie 2013,2013 movies online,join4movie,join4movies
  • Meta Description
    Latest Hindi Movies Online Free, Bollywood Movies, Hindi Movies Dubbed In Hindi A big collection of Bollywood Movies online for free

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    188.165.254.204
  • Domain Age
    3 Years, 3 Months, 15 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Wed, 09 Oct 2013 16:54:42 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • cache-control: no-cache, must-revalidate, max-age=0
  • pragma: no-cache
  • expires: Wed, 02 Oct 2013 16:45:53 GMT
  • x-pingback: http://www.join4movies.com/xmlrpc.php
  • last-modified: Wed, 09 Oct 2013 16:54:42 GMT
  • x-powered-by: PleskLin
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: join4movies.com
Registrar: Name.com LLC

Expiration Date: 2014-07-12 15:47:49
Creation Date: 2010-07-12 15:47:49

Name Servers:
ns.kimsufi.com
ks215350.kimsufi.com

REGISTRANT CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +33.14252740657
Fax: +33.14259744730
Email Address: email

ADMINISTRATIVE CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +33.14252740657
Fax: +33.14259744730
Email Address: email

TECHNICAL CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +33.14252740657
Fax: +33.14259744730
Email Address: email

BILLING CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +33.14252740657
Fax: +33.14259744730
Email Address: email

DNS Analysis


DNS servers
ns.kimsufi.com [213.186.33.199]
ks215350.kimsufi.com [188.165.254.204]


DNS Records

Answer records
join4movies.com MX
preference: 10
exchange: mail.join4movies.com
86400s
join4movies.com TXT v=spf1 +a +mx -all 86400s
join4movies.com A 188.165.254.204 86400s
join4movies.com SOA
server: ns.kimsufi.com
email: arsh_dkay@yahoo.com
serial: 2012082303
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
86400s
join4movies.com NS  ks215350.kimsufi.com 86400s
join4movies.com NS  ns.kimsufi.com 86400s

Authority records

Additional records
mail.join4movies.com A 188.165.254.204 86400s
ks215350.kimsufi.com A 188.165.254.204 86400s

IP 188.165.254.204 Analysis

  • Country Code
    FR
  • Country Code3
    FRA
  • Country Name
    France
  • City
    EU
  • Continent Code
    46° North
  • Latitude
    2.
  • Longitude
  • No whois ip data for 188.165.254.204

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 142 Errors
  • 14 Warnings
Ratio Text/Html
  • 0.8016363198844951
Message Error
  • Error Line 17, Column 41: there is no attribute "target"
    … href="http://www.histats.com" target="_blank" title="free web site hit counte…

    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 17, Column 84: document type does not allow element "a" here; assuming missing "object" start-tag
    …t="_blank" title="free web site hit counter" ><script  type="text/javascript" >
  • Error Line 21, Column 59: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …ttp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/…

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

  • Warning Line 21, Column 112: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?1174819&101" alt="free web site hit counter" bo…

    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 21, Column 157: there is no attribute "border"
    …m/0.gif?1174819&101" alt="free web site hit counter" border="0"></a></noscript>

    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 21, Column 164: end tag for "img" omitted, but OMITTAG NO was specified
    …m/0.gif?1174819&101" alt="free web site hit counter" border="0"></a></noscript>

    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 21, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/0…
  • Error Line 23, Column 57: document type does not allow element "link" here
    <link rel="dns-prefetch" href="//connect.facebook.net" />

    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 39, Column 173: document type does not allow element "link" here
    …ns/facebook/static/css/style.min.css?ver=1.1.10' type='text/css' media='all' />

    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 40, Column 185: document type does not allow element "link" here
    …ge-navigation/zmg_page_navigation.css?ver=3.3.1' type='text/css' media='all' />

    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 44, Column 194: document type does not allow element "meta" here
    …ee in four parts. Last stop to watch hindi movies for free in high quality " />

    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 45, Column 439: document type does not allow element "meta" here
    …ies,hindi movies 2012,latest indian movies,hindi movies,online hindi movies" />

    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 46, Column 59: document type does not allow element "link" here
    <link rel="canonical" href="http://www.join4movies.com/" />

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

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

  • Error Line 50, Column 17: there is no attribute "property"
    	<meta property="og:title" content="Online Hindi Movie Watch Free | join4movies…

    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 50, Column 87: document type does not allow element "meta" here
    …roperty="og:title" content="Online Hindi Movie Watch Free | join4movies.com" />

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

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

  • Error Line 51, Column 43: document type does not allow element "meta" here
    	<meta property="og:type" content="blog" />

    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 52, Column 64: document type does not allow element "meta" here
    	<meta property="og:url" content="http://www.join4movies.com" />

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

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

  • Error Line 53, Column 40: document type does not allow element "meta" here
    	<meta property="og:image" content="" />

    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 54, Column 91: document type does not allow element "meta" here
    …rty="og:site_name" content="Online Hindi Movie Watch Free | join4movies.com" />

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

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

  • Error Line 56, Column 178: document type does not allow element "meta" here
    …ree in four parts. Last stop to watch hindi movies for free in high quality" />

    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 58, Column 454: document type does not allow element "style" here
    … ]]> */</script><style type="text/css">.youtube_sc{background-color:#000;color…

    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 58, Column 1172: document type does not allow element "meta" here
    …rty="og:site_name" content="Online Hindi Movie Watch Free | join4movies.com" />

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

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

  • Error Line 59, Column 45: document type does not allow element "meta" here
    <meta property="og:type" content="website" />

    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 60, Column 45: document type does not allow element "meta" here
    <meta property="og:locale" content="en_US" />

    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 61, Column 55: document type does not allow element "meta" here
    <meta property="fb:app_id" content="274853205955340" />

    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 62, Column 86: document type does not allow element "meta" here
    …roperty="og:title" content="Online Hindi Movie Watch Free | join4movies.com" />

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

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

  • Error Line 63, Column 200: document type does not allow element "meta" here
    …ree in four parts. Last stop to watch hindi movies for free in high quality" />

    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 64, Column 63: document type does not allow element "meta" here
    <meta property="og:url" content="http://www.join4movies.com" />

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

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

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

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

  • Info Line 17, Column 1: start tag was here
    <a href="http://www.histats.com" target="_blank" title="free web site hit count…
  • Error Line 69, Column 7: element "right" undefined
    <right>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 75, Column 80: required attribute "alt" not specified
    …tp://join4movies.com"><img src="http://www.join4movies.com/logo.png"></img></a>

    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 79, Column 21: there is no attribute "FRAMEBORDER"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www…

    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 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www…
  • Error Line 79, Column 35: there is no attribute "MARGINWIDTH"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www…

    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 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www…
  • Error Line 79, Column 50: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…

    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 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 79, Column 62: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/7…

    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 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/7…
  • Error Line 79, Column 69: there is no attribute "src"
    …DTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/728x901.…

    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 120: there is no attribute "width"
    …"http://www.join4movies.com/ads/728x901.php" width="728" height="90" ></IFRAME>

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

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

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

  • Error Line 79, Column 133: there is no attribute "height"
    …"http://www.join4movies.com/ads/728x901.php" width="728" height="90" ></IFRAME>

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

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

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

  • Error Line 79, Column 138: element "IFRAME" undefined
    …"http://www.join4movies.com/ads/728x901.php" width="728" height="90" ></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 113, Column 89: document type does not allow element "form" here; assuming missing "li" start-tag
    …" action="http://www.join4movies.com/"><p><input class="text_input" type="text…
  • Error Line 114, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    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 113, Column 1: start tag was here
    <form method="get" class="search_form_image_button" action="http://www.join4mov…
  • Error Line 115, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www…
  • Error Line 115, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www…
  • Error Line 115, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 115, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/7…
  • Error Line 115, Column 138: element "IFRAME" undefined
    …"http://www.join4movies.com/ads/728x901.php" width="728" height="90" ></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 120, Column 9: end tag for element "center" which is not open
    </center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 392, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 392, Column 106: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 392, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 392, Column 133: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/3…
  • Error Line 392, Column 212: element "IFRAME" undefined
    …tp://www.join4movies.com/ads/300x2501.html" width="300" height="250" ></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 394, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www…
  • Error Line 394, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www…
  • Error Line 394, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 394, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/3…
  • Error Line 394, Column 141: element "IFRAME" undefined
    …ww.join4movies.com/ads/300x2501.html" width="300" height="250" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 467, Column 109: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 467, Column 123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 467, Column 138: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 467, Column 150: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/1…
  • Error Line 467, Column 229: element "IFRAME" undefined
    …ww.join4movies.com/ads/160x6001.html" width="160" height="600" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 468, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 468, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 468, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 468, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/3…
  • Error Line 468, Column 219: element "IFRAME" undefined
    …ww.join4movies.com/ads/300x2501.html" width="300" height="250" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 562, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 562, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 562, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 562, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/3…
  • Error Line 562, Column 219: element "IFRAME" undefined
    …ww.join4movies.com/ads/300x2501.html" width="300" height="250" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 563, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 563, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 563, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 563, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/1…
  • Error Line 563, Column 219: element "IFRAME" undefined
    …ww.join4movies.com/ads/160x6001.html" width="160" height="600" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 564, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 564, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 564, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 564, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/3…
  • Error Line 564, Column 219: element "IFRAME" undefined
    …ww.join4movies.com/ads/300x2501.html" width="300" height="250" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 566, Column 31: there is no attribute "data-href"
    <div class="g-plus" data-href="//plus.google.com/110645361765294980202?rel=publ…

    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 576, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 576, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 576, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 576, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/3…
  • Error Line 576, Column 219: element "IFRAME" undefined
    …ww.join4movies.com/ads/300x2501.html" width="300" height="250" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 582, Column 8: element "center" undefined
    <center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 590, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 590, Column 106: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 590, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 590, Column 133: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/1…
  • Error Line 590, Column 212: element "IFRAME" undefined
    …ww.join4movies.com/ads/160x6001.html" width="160" height="600" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 591, Column 125: there is no attribute "src"
    …		<div class="textwidget"><iframe src="http://www.facebook.com/plugins/likebox…

    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 591, Column 341: there is no attribute "scrolling"
    …eader=false&amp;height=255" scrolling="no" frameborder="0" style="border:none;…

    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 591, Column 358: there is no attribute "frameborder"
    …eight=255" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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 591, Column 368: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:200…

    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 591, Column 445: there is no attribute "allowTransparency"
    …overflow:hidden; width:200px; height:255px;" allowTransparency="true"></iframe>

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

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

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

  • Error Line 591, Column 451: element "iframe" undefined
    …overflow:hidden; width:200px; height:255px;" allowTransparency="true"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 595, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 595, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 595, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 595, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/1…
  • Error Line 595, Column 219: element "IFRAME" undefined
    …ww.join4movies.com/ads/160x6001.html" width="160" height="600" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 596, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 596, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 596, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 596, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/1…
  • Error Line 596, Column 219: element "IFRAME" undefined
    …ww.join4movies.com/ads/160x6001.html" width="160" height="600" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 597, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 597, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 597, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 597, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/1…
  • Error Line 597, Column 219: element "IFRAME" undefined
    …ww.join4movies.com/ads/160x6001.html" width="160" height="600" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 623, Column 139: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 623, Column 153: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 623, Column 168: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 623, Column 180: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/1…
  • Error Line 623, Column 259: element "IFRAME" undefined
    …ww.join4movies.com/ads/160x6001.html" width="160" height="600" ></IFRAME></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 638, Column 10: element "center" undefined
    		<center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 654, Column 41: element "center" undefined
    …iv style='padding-bottom:3px;'><center><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MAR…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 654, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tom:3px;'><center><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 654, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ter><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http:…
  • Error Line 654, Column 91: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movi…
  • Error Line 654, Column 103: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO src="http://www.join4movies.com/ads/7…
  • Error Line 654, Column 180: element "IFRAME" undefined
    …http://www.join4movies.com/ads/728x901.html" width="728" height="90" ></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 663, Column 44: document type does not allow element "span" here
    …		jQuery('.description').before('<span><!--INFOLINKS_OFF--></span>');jQuery('.…

    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 663, Column 110: document type does not allow element "span" here
    …');jQuery('.description').after('<span><!--INFOLINKS_ON--></span>');jQuery('#h…

    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 663, Column 174: document type does not allow element "span" here
    …>');jQuery('#headerimg').before('<span><!--INFOLINKS_OFF--></span>');jQuery('#…

    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 663, Column 238: document type does not allow element "span" here
    …n>');jQuery('#headerimg').after('<span><!--INFOLINKS_ON--></span>');jQuery('h1…

    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 663, Column 294: document type does not allow element "span" here
    …-></span>');jQuery('h1').before('<span><!--INFOLINKS_OFF--></span>');jQuery('h…

    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 663, Column 350: document type does not allow element "span" here
    …--></span>');jQuery('h1').after('<span><!--INFOLINKS_ON--></span>');jQuery('h1…

    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 663, Column 406: document type does not allow element "span" here
    …-></span>');jQuery('h1').before('<span><!--INFOLINKS_OFF--></span>');jQuery('h…

    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 663, Column 462: document type does not allow element "span" here
    …OLINKS_OFF--></span>');jQuery('h1').after('<span><!--INFOLINKS_ON--></span>');	

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

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

  • Warning Line 675, Column 86: character "&" is the first character of a delimiter but occurred as data
    …];_gaq.push(function(){if(FB_WP.queue && FB_WP.queue.add){FB_WP.queue.add(func…

    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.
  • Warning Line 675, Column 87: character "&" is the first character of a delimiter but occurred as data
    …;_gaq.push(function(){if(FB_WP.queue && FB_WP.queue.add){FB_WP.queue.add(funct…

    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.

Visitor Analysis

Daily Visitor
  • 7.233 visits