oursogo.com

超人氣休閒娛樂論壇,包含品味生活、休閒天地、興趣嗜好、學術藝文、女性頻道、電腦數位、遊戲天堂、影視音樂、宗教綜合、綜合圖片、綜合影片、成人園地...等一百多個討論區,內容包羅萬象,應有盡有。SOGO論壇是您放鬆心情,抒解壓力的好地方。 sogox我們的論壇,sogo,百貨,sogou論壇 ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    oursogo.com
  • Favicon
  • Alexa Rank
    #8358
  • Google Page Rank
    PR 3
  • Ip Address
    50.23.85.172
  • Page Size
    109.4 KB
  • Images
    18 GIF, 75 JPG, 5 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 11 1 0 0 0

Website Meta Analysis



  • Title
    SOGO論壇–我們的論壇,大家的論壇 OURSOGO.COM
  • Meta Keyword
    SOGO,SOGO論壇,論壇,討論區,bbs,sogox我們的論壇,sogox,sogou論壇,sogou,sogo百貨,生活,聊天,休閒,愛情,婚姻,家庭,法律,宗教,興趣,旅遊,時尚,美食,汽車,機車,釣魚,星座,命理,寵物,小說,嗜好,布袋戲,園藝,花卉,軍事,藝術,模型,魔術,百貨,消費,購物,省錢,女性,彩妝,內衣,珠寶,首飾,時裝,美髮,電腦,數位,3c,軟體,硬體,燒錄,網際網路,程式設計,手機,攝影,遊戲,TV GAME,PC GAME,ONLINE GAME,FLASH GAME,投資,財經,股票,基金,外匯,期貨,房地產,信用卡,貸款,壽險,產險,理財,創業,退休,防癌,中醫,養生,抗癌,醫療,保健,學術,藝文,歷史,科學,考試,電影,電視,戲劇,音樂,舞蹈,娛樂
  • Meta Description
    超人氣休閒娛樂論壇,包含品味生活、休閒天地、興趣嗜好、學術藝文、女性頻道、電腦數位、遊戲天堂、影視音樂、宗教綜合、綜合圖片、綜合影片、成人園地...等一百多個討論區,內容包羅萬象,應有盡有。SOGO論壇是您放鬆心情,抒解壓力的好地方。 sogox我們的論壇,sogo,百貨,sogou論壇

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    50.23.85.172
  • Domain Age
    8 Years, 0 Months, 14 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 30 Jul 2013 07:01:13 GMT
  • server: Apache
  • x-powered-by: PHP/5.2.17
  • content-encoding: gzip
  • vary: Accept-Encoding
  • cache-control: max-age=0
  • expires: Tue, 30 Jul 2013 07:01:13 GMT
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States

Domain Name: OURSOGO.COM
Created on: 28-Jul-05
Expires on: 28-Jul-16
Last Updated on: 03-Jul-11

Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Domain servers in listed order:
NS1186.DNS.DYN.COM
NS2131.DNS.DYN.COM
NS3185.DNS.DYN.COM
NS4131.DNS.DYN.COM

DNS Analysis


DNS servers
ns1186.dns.dyn.com [208.76.58.186]
ns2131.dns.dyn.com [208.76.59.131]
ns3185.dns.dyn.com [208.76.60.185]
ns4131.dns.dyn.com [208.76.61.131]


DNS Records

Answer records
oursogo.com SOA
server: ns1.mydyndns.org
email: zone-admin@dyndns.com
serial: 2011060720
refresh: 10800
retry: 1800
expire: 604800
minimum ttl: 1800
86400s
oursogo.com NS  ns3185.dns.dyn.com 86400s
oursogo.com NS  ns1186.dns.dyn.com 86400s
oursogo.com NS  ns4131.dns.dyn.com 86400s
oursogo.com NS  ns2131.dns.dyn.com 86400s
oursogo.com A 50.23.85.172 3600s
oursogo.com MX
preference: 10
exchange: mail.oursogo.com
3600s
oursogo.com TXT v=spf1 a mx ip4:50.23.69.107 ?all 3600s

Authority records

Additional records
mail.oursogo.com A 50.23.85.172 3600s

IP 50.23.85.172 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Dallas
  • Continent Code
    75207
  • Latitude
    214
  • Longitude
    623
  • %rwhois V-1.5:003fff:00 rwhois.softlayer.com (by Network Solutions, Inc. V-1.5.9.5)
    network:Class-Name:network
    network:ID:NETBLK-SOFTLAYER.50.23.64.0/18
    network:Auth-Area:50.23.64.0/18
    network:Network-Name:SOFTLAYER-50.23.64.0
    network:IP-Network:50.23.85.172/30
    network:IP-Network-Block:50.23.85.172-50.23.85.175
    network:Organization;I:Chih-Ping Liu
    network:Street-Address:4849 Alpha Road
    network:City:Dallas
    network:State:TX
    network:Postal-Code:75244
    network:Country-Code:US
    network:Tech-Contact;I:sysadmins@softlayer.com
    network:Abuse-Contact;I:abuse@a-big.com
    network:Admin-Contact;I:IPADM258-ARIN
    network:Created:2011-10-26 08:09:28
    network:Updated:2011-10-26 11:35:26
    network:Updated-By:ipadmin@softlayer.com

    %ok

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 145 Errors
  • 15 Warnings
Ratio Text/Html
  • 0.6768574158236381
Message Error
  • Error Line 6, Column 46: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="imagetoolbar" content="no">

    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 6, Column 1: start tag was here
    <meta http-equiv="imagetoolbar" content="no">
  • Error Line 27, Column 19: there is no attribute "background"
    <table background="http://static.oursogo.com/image/common/bg_header_big.gif" bo…

    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 31, Column 67: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
        <td height="110" style="width:auto;padding-right:18px;" nowrap>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 34, Column 34: there is no attribute "autocomplete"
    <form method="post" autocomplete="off" id="lsform" action="member.php?mod=loggi…

    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.

  • Warning Line 43, Column 87: cannot generate system identifier for general entity "action"
    …ndow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></t…

    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 43, Column 87: general entity "action" not defined and no default entity
    …ndow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></t…

    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 43, Column 93: reference not terminated by REFC delimiter
    …dow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></td>

    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 43, Column 93: reference to external entity in attribute value
    …dow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></td>

    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 43, Column 93: reference to entity "action" for which no system identifier could be generated
    …dow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></td>

    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 43, Column 86: entity was defined here
    …indow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></…
  • Warning Line 43, Column 100: cannot generate system identifier for general entity "viewlostpw"
    …dow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></td>

    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 43, Column 100: general entity "viewlostpw" not defined and no default entity
    …dow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></td>

    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 43, Column 110: reference not terminated by REFC delimiter
    …dow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></td>

    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 43, Column 110: reference to external entity in attribute value
    …dow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></td>

    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 43, Column 110: reference to entity "viewlostpw" for which no system identifier could be generated
    …dow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></td>

    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 43, Column 99: entity was defined here
    …dow('login', 'member.php?mod=logging&action=login&viewlostpw=1')">找回密碼</a></td>
  • Error Line 47, Column 88: there is no attribute "autocomplete"
    …sword" id="ls_password" class="px vm" autocomplete="off" tabindex="902" /></td>

    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 64, Column 121: required attribute "alt" not specified
    …ogo.com/image/common/sogomenu_left.gif" border="0" width="22" height="29"></td>

    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 64, Column 126: end tag for "img" omitted, but OMITTAG NO was specified
    …ogo.com/image/common/sogomenu_left.gif" border="0" width="22" height="29"></td>

    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 64, Column 20: start tag was here
      		<td width="22"><img src="http://static.oursogo.com/image/common/sogomenu_le…
  • Error Line 65, Column 40: there is no attribute "background"
    … 		<td style="width:auto;" background="http://static.oursogo.com/image/common/…

    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 65, Column 103: duplicate specification of attribute "style"
    …ttp://static.oursogo.com/image/common/sogomenu_bg.gif" style="padding-top:1pt">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 286, Column 122: required attribute "alt" not specified
    …go.com/image/common/sogomenu_right.gif" border="0" width="22" height="29"></td>

    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 286, Column 127: end tag for "img" omitted, but OMITTAG NO was specified
    …go.com/image/common/sogomenu_right.gif" border="0" width="22" height="29"></td>

    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 286, Column 20: start tag was here
      		<td width="22"><img src="http://static.oursogo.com/image/common/sogomenu_ri…
  • Error Line 313, Column 78: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"
    …ge/common/iphone.png" align="absmiddle"><a href="http://oursogo.com/forum.php?…

    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 313, Column 79: required attribute "alt" not specified
    …e/common/iphone.png" align="absmiddle"><a href="http://oursogo.com/forum.php?m…

    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 313, Column 80: end tag for "img" omitted, but OMITTAG NO was specified
    …/common/iphone.png" align="absmiddle"><a href="http://oursogo.com/forum.php?mo…

    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 313, Column 1: start tag was here
    <img src="http://static.oursogo.com/image/common/iphone.png" align="absmiddle">…
  • Error Line 314, Column 83: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"
    …age/common/group.png" align="absmiddle"> <a href="http://oursogo.com/thread-14…

    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 314, Column 84: required attribute "alt" not specified
    …ge/common/group.png" align="absmiddle"> <a href="http://oursogo.com/thread-143…

    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 314, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …e/common/group.png" align="absmiddle"> <a href="http://oursogo.com/thread-1437…

    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 314, Column 7: start tag was here
    &nbsp;<img src="http://static.oursogo.com/image/common/group.png" align="absmid…
  • Error Line 330, Column 129: there is no attribute "hidefocus"
    …ass="showmenu xg1 xs2" onclick="showMenu(this.id)" hidefocus="true">搜尋</a></td>

    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 356, Column 38: document type does not allow element "style" here
    <style id="diy_style" type="text/css"></style>

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

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

  • Error Line 395, Column 149: end tag for "br" omitted, but OMITTAG NO was specified
    …獄酒店:&quot;鐵窗&quot;內盡享奢華 別 ...</a> <br><cite><span title="2013-3-7 03:12:18">半小…

    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 395, Column 145: start tag was here
    …>荷蘭監獄酒店:&quot;鐵窗&quot;內盡享奢華 別 ...</a> <br><cite><span title="2013-3-7 03:12:18…
  • Error Line 405, Column 128: end tag for "br" omitted, but OMITTAG NO was specified
    …post" class="xi2">當兵 就要玩外島!!!</a> <br><cite><span title="2013-3-7 02:25:15">1&…

    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 405, Column 124: start tag was here
    …lastpost" class="xi2">當兵 就要玩外島!!!</a> <br><cite><span title="2013-3-7 02:25:15…
  • Error Line 417, Column 122: end tag for "br" omitted, but OMITTAG NO was specified
    …t#lastpost" class="xi2">她的想法?</a> <br><cite><span title="2013-3-7 04:03:00">3&…

    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 417, Column 118: start tag was here
    …tpost#lastpost" class="xi2">她的想法?</a> <br><cite><span title="2013-3-7 04:03:00…
  • Error Line 427, Column 124: end tag for "br" omitted, but OMITTAG NO was specified
    …lastpost" class="xi2">中年失業的困擾</a> <br><cite><span title="2013-3-7 02:07:46">1&…

    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 427, Column 120: start tag was here
    …ost#lastpost" class="xi2">中年失業的困擾</a> <br><cite><span title="2013-3-7 02:07:46…
  • Error Line 439, Column 133: end tag for "br" omitted, but OMITTAG NO was specified
    … class="xi2">醫師勒令歇業還看診 法辦 ...</a> <br><cite><span title="2013-3-7 00:08:08">3&…

    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 439, Column 129: start tag was here
    …ost" class="xi2">醫師勒令歇業還看診 法辦 ...</a> <br><cite><span title="2013-3-7 00:08:08…
  • Error Line 449, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …ss="xi2">定期性生活 可刺激神經細胞提高腦 ...</a> <br><cite><span title="2013-3-7 01:13:10">2&…

    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 449, Column 133: start tag was here
    … class="xi2">定期性生活 可刺激神經細胞提高腦 ...</a> <br><cite><span title="2013-3-7 01:13:10…
  • Error Line 482, Column 125: end tag for "br" omitted, but OMITTAG NO was specified
    …astpost" class="xi2">在桃園的美食!!</a> <br><cite><span title="2013-3-7 02:04:21">1&…

    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 482, Column 121: start tag was here
    …st#lastpost" class="xi2">在桃園的美食!!</a> <br><cite><span title="2013-3-7 02:04:21…
  • Error Line 492, Column 142: end tag for "br" omitted, but OMITTAG NO was specified
    …i2">&lt;0306 股動錢潮名師解盤&gt; ...</a> <br><cite><span title="2013-3-6 22:18:49">昨天…

    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 492, Column 138: start tag was here
    …s="xi2">&lt;0306 股動錢潮名師解盤&gt; ...</a> <br><cite><span title="2013-3-6 22:18:49…
  • Error Line 502, Column 127: end tag for "br" omitted, but OMITTAG NO was specified
    …tpost" class="xi2">PChome 買香水</a> <br><cite><span title="2013-3-7 02:06:39">1&…

    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 502, Column 123: start tag was here
    …#lastpost" class="xi2">PChome 買香水</a> <br><cite><span title="2013-3-7 02:06:39…
  • Error Line 528, Column 125: end tag for "br" omitted, but OMITTAG NO was specified
    …astpost" class="xi2">102年頭〝香〞</a> <br><cite><span title="2013-3-7 03:27:15">半小…

    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 528, Column 121: start tag was here
    …st#lastpost" class="xi2">102年頭〝香〞</a> <br><cite><span title="2013-3-7 03:27:15…
  • Error Line 538, Column 140: end tag for "br" omitted, but OMITTAG NO was specified
    …"xi2">18種罕見的汽車標志 你有見過嗎 [1 ...</a> <br><cite><span title="2013-3-7 03:35:12">27…

    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 538, Column 136: start tag was here
    …ass="xi2">18種罕見的汽車標志 你有見過嗎 [1 ...</a> <br><cite><span title="2013-3-7 03:35:12…
  • Error Line 548, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …ss="xi2">恐怖娃娃製造商瑪麗蓮·曼斯菲爾德 ...</a> <br><cite><span title="2013-3-7 00:55:38">3&…

    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 548, Column 133: start tag was here
    … class="xi2">恐怖娃娃製造商瑪麗蓮·曼斯菲爾德 ...</a> <br><cite><span title="2013-3-7 00:55:38…
  • Error Line 560, Column 122: end tag for "br" omitted, but OMITTAG NO was specified
    …t#lastpost" class="xi2">水下飛行服</a> <br><cite><span title="2013-3-7 04:02:53">10…

    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 560, Column 118: start tag was here
    …tpost#lastpost" class="xi2">水下飛行服</a> <br><cite><span title="2013-3-7 04:02:53…
  • Error Line 570, Column 125: end tag for "br" omitted, but OMITTAG NO was specified
    …astpost" class="xi2">出門散步遇到鬼王</a> <br><cite><span title="2013-3-7 00:59:49">3&…

    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 570, Column 121: start tag was here
    …st#lastpost" class="xi2">出門散步遇到鬼王</a> <br><cite><span title="2013-3-7 00:59:49…
  • Error Line 580, Column 132: end tag for "br" omitted, but OMITTAG NO was specified
    …" class="xi2">便宜的引閃器 開箱 [13P]</a> <br><cite><span title="2013-3-7 02:57:04">1&…

    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 580, Column 128: start tag was here
    …post" class="xi2">便宜的引閃器 開箱 [13P]</a> <br><cite><span title="2013-3-7 02:57:04…
  • Error Line 592, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …ss="xi2">「大台北」淡水/榕堤大道 淡水最 ...</a> <br><cite><span title="2013-3-7 00:58:36">3&…

    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 592, Column 133: start tag was here
    … class="xi2">「大台北」淡水/榕堤大道 淡水最 ...</a> <br><cite><span title="2013-3-7 00:58:36…
  • Error Line 602, Column 132: end tag for "br" omitted, but OMITTAG NO was specified
    … class="xi2">你們會不會懷疑樂透有作弊 ...</a> <br><cite><span title="2013-3-6 23:43:38">昨天…

    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 602, Column 128: start tag was here
    …ost" class="xi2">你們會不會懷疑樂透有作弊 ...</a> <br><cite><span title="2013-3-6 23:43:38…
  • Error Line 612, Column 135: end tag for "br" omitted, but OMITTAG NO was specified
    …lass="xi2">來一起去看冠軍咖啡師煮咖啡! ...</a> <br><cite><span title="2013-3-6 23:36:00">昨天…

    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 612, Column 131: start tag was here
    …t" class="xi2">來一起去看冠軍咖啡師煮咖啡! ...</a> <br><cite><span title="2013-3-6 23:36:00…
  • Error Line 648, Column 121: end tag for "br" omitted, but OMITTAG NO was specified
    …st#lastpost" class="xi2">心理測驗</a> <br><cite><span title="2013-3-7 03:32:25">半小…

    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 648, Column 117: start tag was here
    …stpost#lastpost" class="xi2">心理測驗</a> <br><cite><span title="2013-3-7 03:32:25…
  • Error Line 658, Column 139: end tag for "br" omitted, but OMITTAG NO was specified
    …="xi2">我在麻理的身體裏 第7話-本物麻理  ...</a> <br><cite><span title="2013-3-7 02:30:11">1&…

    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 658, Column 135: start tag was here
    …lass="xi2">我在麻理的身體裏 第7話-本物麻理  ...</a> <br><cite><span title="2013-3-7 02:30:11…
  • Error Line 668, Column 126: end tag for "br" omitted, but OMITTAG NO was specified
    …stpost" class="xi2">裝甲兵學校營區開放</a> <br><cite><span title="2013-3-7 01:21:57">2&…

    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 668, Column 122: start tag was here
    …t#lastpost" class="xi2">裝甲兵學校營區開放</a> <br><cite><span title="2013-3-7 01:21:57…
  • Error Line 680, Column 134: end tag for "br" omitted, but OMITTAG NO was specified
    …class="xi2">[問題研討] 中華隊加油! ...</a> <br><cite><span title="2013-3-7 02:16:01">1&…

    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 680, Column 130: start tag was here
    …st" class="xi2">[問題研討] 中華隊加油! ...</a> <br><cite><span title="2013-3-7 02:16:01…
  • Error Line 690, Column 127: end tag for "br" omitted, but OMITTAG NO was specified
    …tpost" class="xi2">您認為最經典的出場?</a> <br><cite><span title="2013-3-7 01:13:51">2&…

    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 690, Column 123: start tag was here
    …#lastpost" class="xi2">您認為最經典的出場?</a> <br><cite><span title="2013-3-7 01:13:51…
  • Error Line 700, Column 143: end tag for "br" omitted, but OMITTAG NO was specified
    …2">102/03/17=高雄寵物鳥聚會資訊~~~ ...</a> <br><cite><span title="2013-3-7 03:42:26">20…

    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 700, Column 139: start tag was here
    …="xi2">102/03/17=高雄寵物鳥聚會資訊~~~ ...</a> <br><cite><span title="2013-3-7 03:42:26…
  • Error Line 712, Column 142: end tag for "br" omitted, but OMITTAG NO was specified
    …i2">((11/22更新))我的模型大玩具(持續 ...</a> <br><cite><span title="2013-3-7 01:27:24">2&…

    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 712, Column 138: start tag was here
    …s="xi2">((11/22更新))我的模型大玩具(持續 ...</a> <br><cite><span title="2013-3-7 01:27:24…
  • Error Line 722, Column 127: end tag for "br" omitted, but OMITTAG NO was specified
    …tpost" class="xi2">日本把世界放進盆景了</a> <br><cite><span title="2013-3-7 01:15:19">2&…

    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 722, Column 123: start tag was here
    …#lastpost" class="xi2">日本把世界放進盆景了</a> <br><cite><span title="2013-3-7 01:15:19…
  • Error Line 732, Column 145: end tag for "br" omitted, but OMITTAG NO was specified
    …>2013年 KHS AL-50 CP值超高的登山 ...</a> <br><cite><span title="2013-3-6 16:37:08">昨天…

    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 732, Column 141: start tag was here
    …xi2">2013年 KHS AL-50 CP值超高的登山 ...</a> <br><cite><span title="2013-3-6 16:37:08…
  • Error Line 744, Column 129: end tag for "br" omitted, but OMITTAG NO was specified
    …ost" class="xi2">中華民國  清代刺繡郵票</a> <br><cite><span title="2013-3-6 10:02:25">昨天…

    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 744, Column 125: start tag was here
    …astpost" class="xi2">中華民國  清代刺繡郵票</a> <br><cite><span title="2013-3-6 10:02:25…
  • Error Line 748, Column 40: end tag for element "tr" which is not open
    <td>&nbsp;</td><td>&nbsp;</td></tr></tr>

    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 770, Column 124: end tag for "br" omitted, but OMITTAG NO was specified
    …astpost" class="xi2">票選金庸十大武功</a> <br><cite><span title="2013-3-7 03:11:43">半小…

    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 770, Column 120: start tag was here
    …st#lastpost" class="xi2">票選金庸十大武功</a> <br><cite><span title="2013-3-7 03:11:43…
  • Error Line 780, Column 138: end tag for "br" omitted, but OMITTAG NO was specified
    …s="xi2">[席維亞]遲鈍小甜心(愛乘以無限大 ...</a> <br><cite><span title="2013-3-7 00:52:43">3&…

    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 780, Column 134: start tag was here
    …class="xi2">[席維亞]遲鈍小甜心(愛乘以無限大 ...</a> <br><cite><span title="2013-3-7 00:52:43…
  • Error Line 790, Column 135: end tag for "br" omitted, but OMITTAG NO was specified
    …lass="xi2">老頭子,我要走了,抱抱我吧。 ...</a> <br><cite><span title="2013-3-6 23:37:59">昨天…

    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 790, Column 131: start tag was here
    …t" class="xi2">老頭子,我要走了,抱抱我吧。 ...</a> <br><cite><span title="2013-3-6 23:37:59…
  • Error Line 802, Column 123: end tag for "br" omitted, but OMITTAG NO was specified
    …#lastpost" class="xi2">放.....</a> <br><cite><span title="2013-3-7 01:03:02">3&…

    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 802, Column 119: start tag was here
    …post#lastpost" class="xi2">放.....</a> <br><cite><span title="2013-3-7 01:03:02…
  • Error Line 812, Column 120: end tag for "br" omitted, but OMITTAG NO was specified
    …ost#lastpost" class="xi2">鋸木頭</a> <br><cite><span title="2013-3-6 23:41:58">昨天…

    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 812, Column 116: start tag was here
    …astpost#lastpost" class="xi2">鋸木頭</a> <br><cite><span title="2013-3-6 23:41:58…
  • Error Line 822, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …ss="xi2">台灣民間故事-濁水溪的水為什麼是 ...</a> <br><cite><span title="2013-3-7 01:30:01">2&…

    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 822, Column 133: start tag was here
    … class="xi2">台灣民間故事-濁水溪的水為什麼是 ...</a> <br><cite><span title="2013-3-7 01:30:01…
  • Error Line 834, Column 133: end tag for "br" omitted, but OMITTAG NO was specified
    … class="xi2">大家記得小時候的爆米香嗎 ...</a> <br><cite><span title="2013-3-6 23:48:14">昨天…

    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 834, Column 129: start tag was here
    …ost" class="xi2">大家記得小時候的爆米香嗎 ...</a> <br><cite><span title="2013-3-6 23:48:14…
  • Error Line 844, Column 123: end tag for "br" omitted, but OMITTAG NO was specified
    …#lastpost" class="xi2">熱黑-曾御欽</a> <br><cite><span title="2013-3-7 00:15:34">3&…

    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 844, Column 119: start tag was here
    …post#lastpost" class="xi2">熱黑-曾御欽</a> <br><cite><span title="2013-3-7 00:15:34…
  • Error Line 854, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …s="xi2">請問目前社會上取得何種證照 ~ 最 ...</a> <br><cite><span title="2013-3-7 00:45:50">3&…

    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 854, Column 133: start tag was here
    …class="xi2">請問目前社會上取得何種證照 ~ 最 ...</a> <br><cite><span title="2013-3-7 00:45:50…
  • Error Line 866, Column 136: end tag for "br" omitted, but OMITTAG NO was specified
    …ass="xi2">荔枝好食皮粗粗,龍眼好食核烏烏 ...</a> <br><cite><span title="2013-3-6 14:25:58">昨天…

    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 866, Column 132: start tag was here
    …" class="xi2">荔枝好食皮粗粗,龍眼好食核烏烏 ...</a> <br><cite><span title="2013-3-6 14:25:58…
  • Error Line 876, Column 122: end tag for "br" omitted, but OMITTAG NO was specified
    …t#lastpost" class="xi2">鞋盒大變身</a> <br><cite><span title="2013-3-4 12:40:32">3&…

    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 876, Column 118: start tag was here
    …tpost#lastpost" class="xi2">鞋盒大變身</a> <br><cite><span title="2013-3-4 12:40:32…
  • Error Line 886, Column 124: end tag for "br" omitted, but OMITTAG NO was specified
    …lastpost" class="xi2">銅鑼燒懶人沙發</a> <br><cite><span title="2013-3-7 01:02:06">3&…

    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 886, Column 120: start tag was here
    …ost#lastpost" class="xi2">銅鑼燒懶人沙發</a> <br><cite><span title="2013-3-7 01:02:06…
  • Error Line 897, Column 10: required attribute "type" not specified
    		<script>

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

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

  • Error Line 898, Column 126: required attribute "type" not specified
    …drid_1.js?rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");

    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 898, Column 126: document type does not allow element "script" here
    …drid_1.js?rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");

    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 898, Column 131: delimiter """ invalid: only S separators and TAGC allowed here
    …drid_1.js?rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");
  • Error Line 898, Column 131: end tag for element "sc" which is not open
    …drid_1.js?rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");

    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 900, Column 8: end tag for "script" omitted, but OMITTAG NO was specified
    		</div>

    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 897, Column 3: start tag was here
    		<script>
  • Error Line 918, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …ss="xi2">男友每個月都問我借錢..合理嗎? ...</a> <br><cite><span title="2013-3-7 03:56:42">6&…

    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 918, Column 133: start tag was here
    … class="xi2">男友每個月都問我借錢..合理嗎? ...</a> <br><cite><span title="2013-3-7 03:56:42…
  • Error Line 928, Column 121: end tag for "br" omitted, but OMITTAG NO was specified
    …st#lastpost" class="xi2">單親家庭</a> <br><cite><span title="2013-3-4 23:55:17">3&…

    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 928, Column 117: start tag was here
    …stpost#lastpost" class="xi2">單親家庭</a> <br><cite><span title="2013-3-4 23:55:17…
  • Error Line 938, Column 132: end tag for "br" omitted, but OMITTAG NO was specified
    …" class="xi2">選購嬰兒床該注意的事項 ...</a> <br><cite><span title="2013-3-6 22:34:19">昨天…

    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 938, Column 128: start tag was here
    …post" class="xi2">選購嬰兒床該注意的事項 ...</a> <br><cite><span title="2013-3-6 22:34:19…
  • Error Line 950, Column 119: end tag for "br" omitted, but OMITTAG NO was specified
    …post#lastpost" class="xi2">月子</a> <br><cite><span title="2013-3-7 02:23:44">1&…

    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 950, Column 115: start tag was here
    …lastpost#lastpost" class="xi2">月子</a> <br><cite><span title="2013-3-7 02:23:44…
  • Error Line 960, Column 139: end tag for "br" omitted, but OMITTAG NO was specified
    …="xi2">性感女性(情趣)睡衣1/2[85P] ...</a> <br><cite><span title="2013-3-6 16:39:14">昨天…

    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 960, Column 135: start tag was here
    …lass="xi2">性感女性(情趣)睡衣1/2[85P] ...</a> <br><cite><span title="2013-3-6 16:39:14…
  • Error Line 970, Column 133: end tag for "br" omitted, but OMITTAG NO was specified
    … class="xi2">迷你可愛 婚禮小物分享  ...</a> <br><cite><span title="2013-3-6 10:56:59">昨天…

    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 970, Column 129: start tag was here
    …ost" class="xi2">迷你可愛 婚禮小物分享  ...</a> <br><cite><span title="2013-3-6 10:56:59…
  • Error Line 982, Column 134: end tag for "br" omitted, but OMITTAG NO was specified
    …class="xi2">跳繩法輕鬆享瘦減肥不再乏味 ...</a> <br><cite><span title="2013-3-6 22:51:16">昨天…

    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 982, Column 130: start tag was here
    …st" class="xi2">跳繩法輕鬆享瘦減肥不再乏味 ...</a> <br><cite><span title="2013-3-6 22:51:16…
  • Error Line 992, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …ss="xi2">只想穿超級乾,不想臉上變超級乾! ...</a> <br><cite><span title="2013-3-6 21:21:00">昨天…

    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 992, Column 133: start tag was here
    … class="xi2">只想穿超級乾,不想臉上變超級乾! ...</a> <br><cite><span title="2013-3-6 21:21:00…
  • Error Line 1002, Column 133: end tag for "br" omitted, but OMITTAG NO was specified
    … class="xi2">華妃、甄嬛、惠貴人 手鍊 ...</a> <br><cite><span title="2013-3-5 22:13:19">前天…

    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 1002, Column 129: start tag was here
    …ost" class="xi2">華妃、甄嬛、惠貴人 手鍊 ...</a> <br><cite><span title="2013-3-5 22:13:19…
  • Error Line 1028, Column 143: end tag for "br" omitted, but OMITTAG NO was specified
    …2">NVIDIA顯示卡加速器 (效能提升40%) ...</a> <br><cite><span title="2013-3-7 00:06:58">3&…

    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 1028, Column 139: start tag was here
    …="xi2">NVIDIA顯示卡加速器 (效能提升40%) ...</a> <br><cite><span title="2013-3-7 00:06:58…
  • Error Line 1038, Column 140: end tag for "br" omitted, but OMITTAG NO was specified
    …"xi2">[問題討論] 請問誰有類似Foxy這種 ...</a> <br><cite><span title="2013-3-6 23:56:52">昨天…

    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 1038, Column 136: start tag was here
    …ass="xi2">[問題討論] 請問誰有類似Foxy這種 ...</a> <br><cite><span title="2013-3-6 23:56:52…
  • Error Line 1048, Column 139: end tag for "br" omitted, but OMITTAG NO was specified
    …="xi2">明年預計出國現在辦i5綁1年OK嗎? ...</a> <br><cite><span title="2013-3-6 23:57:39">昨天…

    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 1048, Column 135: start tag was here
    …lass="xi2">明年預計出國現在辦i5綁1年OK嗎? ...</a> <br><cite><span title="2013-3-6 23:57:39…
  • Error Line 1060, Column 139: end tag for "br" omitted, but OMITTAG NO was specified
    …="xi2">安卓用戶專屬一鍵ROOT,完美刷機工 ...</a> <br><cite><span title="2013-3-7 03:02:03">1&…

    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 1060, Column 135: start tag was here
    …lass="xi2">安卓用戶專屬一鍵ROOT,完美刷機工 ...</a> <br><cite><span title="2013-3-7 03:02:03…
  • Error Line 1070, Column 138: end tag for "br" omitted, but OMITTAG NO was specified
    …="xi2">搞笑鈴聲24p 海賊王電話蟲.白目小 ...</a> <br><cite><span title="2013-3-7 01:01:07">3&…

    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 1070, Column 134: start tag was here
    …lass="xi2">搞笑鈴聲24p 海賊王電話蟲.白目小 ...</a> <br><cite><span title="2013-3-7 01:01:07…
  • Error Line 1080, Column 149: end tag for "br" omitted, but OMITTAG NO was specified
    …=======2013年 巡帖線========= ...</a> <br><cite><span title="2013-3-6 19:41:05">昨天…

    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 1080, Column 145: start tag was here
    …>==========2013年 巡帖線========= ...</a> <br><cite><span title="2013-3-6 19:41:05…
  • Error Line 1092, Column 125: end tag for "br" omitted, but OMITTAG NO was specified
    …astpost" class="xi2">請問一下貧果電腦</a> <br><cite><span title="2013-3-6 23:59:19">昨天…

    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 1092, Column 121: start tag was here
    …st#lastpost" class="xi2">請問一下貧果電腦</a> <br><cite><span title="2013-3-6 23:59:19…
  • Error Line 1102, Column 133: end tag for "br" omitted, but OMITTAG NO was specified
    … class="xi2">請問一下便宜的平板怎麼選 ...</a> <br><cite><span title="2013-3-7 02:55:01">1&…

    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 1102, Column 129: start tag was here
    …ost" class="xi2">請問一下便宜的平板怎麼選 ...</a> <br><cite><span title="2013-3-7 02:55:01…
  • Error Line 1112, Column 149: end tag for "br" omitted, but OMITTAG NO was specified
    …=======2013年 巡帖線========= ...</a> <br><cite><span title="2013-3-6 19:42:02">昨天…

    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 1112, Column 145: start tag was here
    …>==========2013年 巡帖線========= ...</a> <br><cite><span title="2013-3-6 19:42:02…
  • Error Line 1124, Column 134: end tag for "br" omitted, but OMITTAG NO was specified
    …class="xi2">蝴蝶大戰機皇,你選哪一邊? ...</a> <br><cite><span title="2013-3-7 02:37:25">1&…

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

  • Info Line 1124, Column 130: start tag was here
    …st" class="xi2">蝴蝶大戰機皇,你選哪一邊? ...</a> <br><cite><span title="2013-3-7 02:37:25…
  • Error Line 1134, Column 136: end tag for "br" omitted, but OMITTAG NO was specified
    …ass="xi2">請教!!如何避免突波影響??? ...</a> <br><cite><span title="2013-3-4 14:09:55">3&…

    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 1134, Column 132: start tag was here
    …" class="xi2">請教!!如何避免突波影響??? ...</a> <br><cite><span title="2013-3-4 14:09:55…
  • Error Line 1138, Column 25: end tag for element "tr" which is not open
    <td>&nbsp;</td></tr></tr>

    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 1160, Column 146: end tag for "br" omitted, but OMITTAG NO was specified
    …紅藍坦克攻堅戰 2 ( Ultimate Army ...</a> <br><cite><span title="2013-3-7 03:42:42">20…

    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 1160, Column 142: start tag was here
    …i2">紅藍坦克攻堅戰 2 ( Ultimate Army ...</a> <br><cite><span title="2013-3-7 03:42:42…
  • Error Line 1170, Column 141: end tag for "br" omitted, but OMITTAG NO was specified
    …i2">[Nokia] 山脊漂移賽車 [自動適屏] ...</a> <br><cite><span title="2013-3-6 23:04:36">昨天…

    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 1170, Column 137: start tag was here
    …s="xi2">[Nokia] 山脊漂移賽車 [自動適屏] ...</a> <br><cite><span title="2013-3-6 23:04:36…
  • Error Line 1180, Column 125: end tag for "br" omitted, but OMITTAG NO was specified
    …astpost" class="xi2">笑死人的網路對嗆</a> <br><cite><span title="2013-3-6 16:53:50">昨天…

    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 1180, Column 121: start tag was here
    …st#lastpost" class="xi2">笑死人的網路對嗆</a> <br><cite><span title="2013-3-6 16:53:50…
  • Error Line 1192, Column 146: end tag for "br" omitted, but OMITTAG NO was specified
    …戰地風雲 Battlefield 全集 [ISO繁 ...</a> <br><cite><span title="2013-3-6 20:46:25">昨天…

    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 1192, Column 142: start tag was here
    …i2">戰地風雲 Battlefield 全集 [ISO繁 ...</a> <br><cite><span title="2013-3-6 20:46:25…
  • Error Line 1202, Column 123: end tag for "br" omitted, but OMITTAG NO was specified
    …#lastpost" class="xi2">魔物獵人3G</a> <br><cite><span title="2013-3-5 07:44:02">前天…

    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 1202, Column 119: start tag was here
    …post#lastpost" class="xi2">魔物獵人3G</a> <br><cite><span title="2013-3-5 07:44:02…
  • Error Line 1212, Column 138: end tag for "br" omitted, but OMITTAG NO was specified
    …s="xi2">大家對FB有正妹加你好友 後面卻發 ...</a> <br><cite><span title="2013-3-6 15:34:04">昨天…

    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 1212, Column 134: start tag was here
    …class="xi2">大家對FB有正妹加你好友 後面卻發 ...</a> <br><cite><span title="2013-3-6 15:34:04…
  • Error Line 1238, Column 121: end tag for "br" omitted, but OMITTAG NO was specified
    …st#lastpost" class="xi2">混混天團</a> <br><cite><span title="2013-3-7 03:09:01">半小…

    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 1238, Column 117: start tag was here
    …stpost#lastpost" class="xi2">混混天團</a> <br><cite><span title="2013-3-7 03:09:01…
  • Error Line 1248, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …ss="xi2">藍心湄虧唐禹哲妝太濃 流汗變奶昔 ...</a> <br><cite><span title="2013-3-6 21:15:32">昨天…

    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 1248, Column 133: start tag was here
    … class="xi2">藍心湄虧唐禹哲妝太濃 流汗變奶昔 ...</a> <br><cite><span title="2013-3-6 21:15:32…
  • Error Line 1258, Column 142: end tag for "br" omitted, but OMITTAG NO was specified
    …i2">[親傳] 清純可愛~【任容萱】 [88P] ...</a> <br><cite><span title="2013-3-7 01:51:04">2&…

    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 1258, Column 138: start tag was here
    …s="xi2">[親傳] 清純可愛~【任容萱】 [88P] ...</a> <br><cite><span title="2013-3-7 01:51:04…
  • Error Line 1270, Column 135: end tag for "br" omitted, but OMITTAG NO was specified
    …lass="xi2">玖壹壹(洋蔥)-癡情的男子漢 ...</a> <br><cite><span title="2013-3-7 01:50:28">2&…

    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 1270, Column 131: start tag was here
    …t" class="xi2">玖壹壹(洋蔥)-癡情的男子漢 ...</a> <br><cite><span title="2013-3-7 01:50:28…
  • Error Line 1280, Column 144: end tag for "br" omitted, but OMITTAG NO was specified
    …">陳淑樺 – 夢醒時份 – sung by LT ...</a> <br><cite><span title="2013-3-5 07:16:43">前天…

    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 1280, Column 140: start tag was here
    …"xi2">陳淑樺 – 夢醒時份 – sung by LT ...</a> <br><cite><span title="2013-3-5 07:16:43…
  • Error Line 1290, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …ss="xi2">不要再問什麼樂器可不可以自學了, ...</a> <br><cite><span title="2013-3-7 02:29:56">1&…

    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 1290, Column 133: start tag was here
    … class="xi2">不要再問什麼樂器可不可以自學了, ...</a> <br><cite><span title="2013-3-7 02:29:56…
  • Error Line 1302, Column 121: end tag for "br" omitted, but OMITTAG NO was specified
    …st#lastpost" class="xi2">不可思議</a> <br><cite><span title="2013-3-3 20:25:31">4&…

    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 1302, Column 117: start tag was here
    …stpost#lastpost" class="xi2">不可思議</a> <br><cite><span title="2013-3-3 20:25:31…
  • Error Line 1306, Column 40: end tag for element "tr" which is not open
    <td>&nbsp;</td><td>&nbsp;</td></tr></tr>

    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 1328, Column 123: end tag for "br" omitted, but OMITTAG NO was specified
    …#lastpost" class="xi2">究竟那一喝?</a> <br><cite><span title="2013-3-7 00:17:38">3&…

    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 1328, Column 119: start tag was here
    …post#lastpost" class="xi2">究竟那一喝?</a> <br><cite><span title="2013-3-7 00:17:38…
  • Error Line 1338, Column 139: end tag for "br" omitted, but OMITTAG NO was specified
    …="xi2">武財神 ─ 關聖帝君  (三界伏魔大 ...</a> <br><cite><span title="2013-3-7 03:51:13">11…

    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 1338, Column 135: start tag was here
    …lass="xi2">武財神 ─ 關聖帝君  (三界伏魔大 ...</a> <br><cite><span title="2013-3-7 03:51:13…
  • Error Line 1348, Column 135: end tag for "br" omitted, but OMITTAG NO was specified
    …lass="xi2">禱告不可像外邦人用許多重複話 ...</a> <br><cite><span title="2013-3-7 00:19:48">3&…

    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 1348, Column 131: start tag was here
    …t" class="xi2">禱告不可像外邦人用許多重複話 ...</a> <br><cite><span title="2013-3-7 00:19:48…
  • Error Line 1360, Column 125: end tag for "br" omitted, but OMITTAG NO was specified
    …astpost" class="xi2">無正當理由的討休</a> <br><cite><span title="2013-3-7 00:21:59">3&…

    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 1360, Column 121: start tag was here
    …st#lastpost" class="xi2">無正當理由的討休</a> <br><cite><span title="2013-3-7 00:21:59…
  • Error Line 1364, Column 40: end tag for element "tr" which is not open
    <td>&nbsp;</td><td>&nbsp;</td></tr></tr>

    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 1372, Column 89: required attribute "alt" not specified
    …ategory_1_img" src="http://static.oursogo.com/image/common/collapsed_no.gif" />

    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 1380, Column 159: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"
    …icon/forum_photo.png" align="absmiddle"> 本區收藏數十萬張精彩美圖,註冊會員才能瀏覽,<a href="http:/…

    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 1380, Column 160: required attribute "alt" not specified
    …con/forum_photo.png" align="absmiddle"> 本區收藏數十萬張精彩美圖,註冊會員才能瀏覽,<a href="http://…

    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 1380, Column 161: end tag for "img" omitted, but OMITTAG NO was specified
    …on/forum_photo.png" align="absmiddle"> 本區收藏數十萬張精彩美圖,註冊會員才能瀏覽,<a href="http://o…

    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 1380, Column 74: start tag was here
    …"font-size: 11pt; padding-top: 15px;"><img src="http://static.oursogo.com/imag…
  • Error Line 1387, Column 90: required attribute "alt" not specified
    …tegory_28_img" src="http://static.oursogo.com/image/common/collapsed_no.gif" />

    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 1395, Column 159: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"
    …icon/forum_video.png" align="absmiddle"> 本區收藏數萬部精彩好片,註冊會員才能瀏覽,<a href="http://…

    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 1395, Column 160: required attribute "alt" not specified
    …con/forum_video.png" align="absmiddle"> 本區收藏數萬部精彩好片,註冊會員才能瀏覽,<a href="http://o…

    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 1395, Column 161: end tag for "img" omitted, but OMITTAG NO was specified
    …on/forum_video.png" align="absmiddle"> 本區收藏數萬部精彩好片,註冊會員才能瀏覽,<a href="http://ou…

    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 1395, Column 74: start tag was here
    …"font-size: 11pt; padding-top: 15px;"><img src="http://static.oursogo.com/imag…
  • Error Line 1422, Column 8: required attribute "type" not specified
    <script>

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

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

  • Warning Line 1423, Column 72: cannot generate system identifier for general entity "rnd"
    …://pop.addeliver.biz/readad.php?wsn=7&rnd=" + Math.random() + Date.parse(new D…

    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 1423, Column 72: general entity "rnd" not defined and no default entity
    …://pop.addeliver.biz/readad.php?wsn=7&rnd=" + Math.random() + Date.parse(new D…

    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 1423, Column 75: reference not terminated by REFC delimiter
    …pop.addeliver.biz/readad.php?wsn=7&rnd=" + Math.random() + Date.parse(new Date…

    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 1423, Column 75: reference to external entity in attribute value
    …pop.addeliver.biz/readad.php?wsn=7&rnd=" + Math.random() + Date.parse(new Date…

    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 1423, Column 75: reference to entity "rnd" for which no system identifier could be generated
    …pop.addeliver.biz/readad.php?wsn=7&rnd=" + Math.random() + Date.parse(new Date…

    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 1423, Column 71: entity was defined here
    …p://pop.addeliver.biz/readad.php?wsn=7&rnd=" + Math.random() + Date.parse(new …
  • Error Line 1423, Column 123: required attribute "type" not specified
    …php?wsn=7&rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");

    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 1423, Column 123: document type does not allow element "script" here
    …php?wsn=7&rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");

    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 1423, Column 128: delimiter """ invalid: only S separators and TAGC allowed here
    …php?wsn=7&rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");
  • Error Line 1423, Column 128: end tag for element "sc" which is not open
    …php?wsn=7&rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");

    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 1425, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 1425, Column 8: document type does not allow element "script" here
    <script>

    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 1427, Column 139: required attribute "type" not specified
    …id + ".js?rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");

    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 1427, Column 139: document type does not allow element "script" here
    …id + ".js?rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");

    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 1427, Column 144: delimiter """ invalid: only S separators and TAGC allowed here
    …id + ".js?rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");
  • Error Line 1427, Column 144: end tag for element "sc" which is not open
    …id + ".js?rnd=" + Math.random() + Date.parse(new Date()) + "'></sc" + "ript>");

    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 1428, Column 16: end tag for "script" omitted, but OMITTAG NO was specified
    </script>	</div>

    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 1425, Column 1: start tag was here
    <script>
  • Error Line 1428, Column 16: end tag for "script" omitted, but OMITTAG NO was specified
    </script>	</div>

    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 1422, Column 1: start tag was here
    <script>
  • Warning Line 1435, Column 32: cannot generate system identifier for general entity "ac"
    <script src="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascri…

    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 1435, Column 32: general entity "ac" not defined and no default entity
    <script src="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascri…

    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 1435, Column 34: reference not terminated by REFC delimiter
    <script src="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascri…

    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 1435, Column 34: reference to external entity in attribute value
    <script src="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascri…

    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 1435, Column 34: reference to entity "ac" for which no system identifier could be generated
    <script src="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascri…

    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 1435, Column 31: entity was defined here
    <script src="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascri…
  • Warning Line 1435, Column 44: cannot generate system identifier for general entity "rand"
    …pt src="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascript">…

    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 1435, Column 44: general entity "rand" not defined and no default entity
    …pt src="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascript">…

    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 1435, Column 48: reference not terminated by REFC delimiter
    …rc="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascript"></sc…

    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 1435, Column 48: reference to external entity in attribute value
    …rc="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascript"></sc…

    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 1435, Column 48: reference to entity "rand" for which no system identifier could be generated
    …rc="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascript"></sc…

    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 1435, Column 43: entity was defined here
    …ipt src="home.php?mod=misc&ac=sendmail&rand=1362600183" type="text/javascript"…
  • Error Line 1440, Column 56: end tag for "br" omitted, but OMITTAG NO was specified
    …lign="center" style="margin: 8px"><br>論壇為非營利自由討論平台,所有個人言論不代表本站立場。文章內容如有涉及侵權,請…

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

  • Info Line 1440, Column 52: start tag was here
    …2" align="center" style="margin: 8px"><br>本論壇為非營利自由討論平台,所有個人言論不代表本站立場。文章內容如有涉及…
  • Error Line 1460, Column 99: required attribute "alt" not specified
    …c="http://static.oursogo.com/image/common/dfix.gif" width="2" height="29"></td>

    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 1460, Column 104: end tag for "img" omitted, but OMITTAG NO was specified
    …c="http://static.oursogo.com/image/common/dfix.gif" width="2" height="29"></td>

    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 1460, Column 19: start tag was here
        <td width="2"><img src="http://static.oursogo.com/image/common/dfix.gif" wi…
  • Error Line 1465, Column 101: required attribute "alt" not specified
    …"http://static.oursogo.com/image/common/ddlink.gif" width="2" height="21"></td>

    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 1465, Column 106: end tag for "img" omitted, but OMITTAG NO was specified
    …"http://static.oursogo.com/image/common/ddlink.gif" width="2" height="21"></td>

    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 1465, Column 19: start tag was here
        <td width="2"><img src="http://static.oursogo.com/image/common/ddlink.gif" …
  • Error Line 1466, Column 122: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …om/image/common/ddlink.gif" align="center" valign="middle" class="copy" nowrap>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 1476, Column 13: end tag for "body" 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 26, Column 1: start tag was here
    <body id="nv_forum" class="pg_index" onkeydown="if(event.keyCode==27) return fa…
  • Error Line 1476, Column 13: end tag for "html" 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 2, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml">

Visitor Analysis

Daily Visitor
  • 10.617 visits

In Page Analysis