RSS feed notworking

Hi all hope you can help. I was trying to add my blog to bloglovin but the site could not find my address. When I used their tool to check my RSS feed was correct,i received the message below. My blog address is http://www.lifestyleblogofathirtysomething.com
thanks in advance for your help.

W3C Markup Validation Service

Check the markup (HTML, XHTML, …) of Web documents

Jump To:
Validation Output

Errors found while checking this document as XHTML 1.0 Transitional!

Result:
30 Errors

Address:

Encoding:
utf-8 (detect automatically) utf-8 (Unicode, worldwide) utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2 (Central Europe) iso-8859-3 (Southern Europe) iso-8859-4 (North European) iso-8859-5 (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8 (Hebrew, visual) iso-8859-8-i (Hebrew, logical) iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-11 (Latin/Thai) iso-8859-13 (Latin 7, Baltic Rim) iso-8859-14 (Latin 8, Celtic) iso-8859-15 (Latin 9) iso-8859-16 (Latin 10) us-ascii (basic English) euc-jp (Japanese, Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email) euc-kr (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified) big5 (Chinese, traditional) Big5-HKSCS (Chinese, Hong Kong) tis-620 (Thai) koi8-r (Russian) koi8-u (Ukrainian) iso-ir-111 (Cyrillic KOI-8) macintosh (MacRoman) windows-1250 (Central Europe) windows-1251 (Cyrillic) windows-1252 (Western Europe) windows-1253 (Greek) windows-1254 (Turkish) windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim)

Doctype:
XHTML 1.0 Transitional (detect automatically) HTML5 (experimental) XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01 Frameset HTML 4.01 + RDFa 1.1 HTML 3.2 HTML 2.0 ISO/IEC 15445:2000 (“ISO HTML”) XHTML 1.1 XHTML + RDFa XHTML Basic 1.0 XHTML Basic 1.1 XHTML Mobile Profile 1.2 XHTML-Print 1.0 XHTML 1.1 plus MathML 2.0 XHTML 1.1 plus MathML 2.0 plus SVG 1.1 MathML 2.0 SVG 1.0 SVG 1.1 SVG 1.1 Tiny SVG 1.1 Basic SMIL 1.0 SMIL 2.0

Root Element:
html

Root Namespace:
http://www.w3.org/1999/xhtml

Validators Donation Program LogoThe W3C validators rely on community support for hosting and development.
Donate and help us build better tools for a better web.

Options
Show Source Show Outline List Messages Sequentially Group Error Messages by Type
Validate error pages Verbose Output Clean up Markup with HTML-Tidy

Help on the options is available.

↑ Top

Validation Output: 30 Errors
Error Line 2, Column 64: there is no attribute “prefix” …lns=”http://www.w3.org/1999/xhtml” lang=”en-US” prefix=”og: http://ogp.me/ns#”>

✉

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 13, Column 16: there is no attribute “property” <meta property=”og:locale” content=”en_US”/>

✉

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 66, Column 38: character “;” not allowed in attribute specification list function wpsrload(){ for(var i=0;i<wc;i++){wpsrasync(wu[i]);} }

✉

Error Line 66, Column 38: element “wc” undefined function wpsrload(){ for(var i=0;i<wc;i++){wpsrasync(wu[i]);} }

✉

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 68, Column 9: end tag for “wc” 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 66, Column 35: start tag was here function wpsrload(){ for(var i=0;i<wc;i++){wpsrasync(wu[i]);} }

Error Line 123, Column 370: there is no attribute “allowTransparency” …no” frameborder=”0″ allowTransparency=”true” style=”border:none; overflow:hidd…

✉

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 125, Column 20: there is no attribute “size” <g:plusone size=”medium” href=”http://www.lifestyleblogofathirtysomething.co…

✉

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 125, Column 34: there is no attribute “href” <g:plusone size=”medium” href=”http://www.lifestyleblogofathirtysomething.co…

✉

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 125, Column 143: element “g:plusone” undefined ….com/2013/08/31/stupendous-afternoon-tea-covent-garden-%e2%99%a5/”></g:plusone>

✉

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 178, Column 125: element “g:plusone” undefined …ofathirtysomething.com/2013/08/29/frugal-living-august-%e2%99%a5/”></g:plusone>

✉

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 231, Column 128: element “g:plusone” undefined …thirtysomething.com/2013/08/27/london-notting-hill-carnival-2013/”></g:plusone>

✉

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 284, Column 139: element “g:plusone” undefined …hing.com/2013/08/16/august-glossybox-beauty-box-review-%e2%99%a5/”></g:plusone>

✉

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 337, Column 116: element “g:plusone” undefined …styleblogofathirtysomething.com/2013/08/12/my-statement-eyebrows/”></g:plusone>

✉

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 390, Column 132: element “g:plusone” undefined …tysomething.com/2013/08/05/my-frugally-up-cycled-table-%e2%99%a5/”></g:plusone>

✉

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 443, Column 129: element “g:plusone” undefined …hirtysomething.com/2013/08/02/my-sanctuary-in-pictures-%e2%99%a5/”></g:plusone>

✉

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 496, Column 123: element “g:plusone” undefined …ogofathirtysomething.com/2013/07/31/month-of-july-buys-%e2%99%a5/”></g:plusone>

✉

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 549, Column 136: element “g:plusone” undefined …mething.com/2013/07/27/fantasy-cake-perfect-for-summer-%e2%99%a5/”></g:plusone>

✉

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 602, Column 137: element “g:plusone” undefined …ething.com/2013/07/25/july-glossybox-beauty-box-review-%e2%99%a5/”></g:plusone>

✉

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 646, Column 74: ID “s” already defined …xt” class=”search” value=”Type KeyWord” name=”s” id=”s” title=”Type KeyWord” />

✉

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

Info Line 84, Column 74: ID “s” first defined here …xt” class=”search” value=”Type KeyWord” name=”s” id=”s” title=”Type KeyWord” />

Error Line 667, Column 190: document type does not allow element “link” here …itor-counter/styles/css/default.css’ /><div id=’mvcwid’ style=’font-size:2; te…

✉

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 668, Column 105: end tag for “img” omitted, but OMITTAG NO was specified …ter/styles/image/glass/0.gif’ alt=’0′><img src=’http://demo.balimechanicweb.ne…

✉

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 21: start tag was here <div id=”mvccount”><img src=’http://demo.balimechanicweb.net/counter/styles/im…

Error Line 668, Column 189: end tag for “img” omitted, but OMITTAG NO was specified …ter/styles/image/glass/0.gif’ alt=’0′><img src=’http://demo.balimechanicweb.ne…

✉

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 105: start tag was here …ter/styles/image/glass/0.gif’ alt=’0′><img src=’http://demo.balimechanicweb.ne…

Error Line 668, Column 273: end tag for “img” omitted, but OMITTAG NO was specified …ter/styles/image/glass/1.gif’ alt=’1′><img src=’http://demo.balimechanicweb.ne…

✉

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 189: start tag was here …ter/styles/image/glass/0.gif’ alt=’0′><img src=’http://demo.balimechanicweb.ne…

Error Line 668, Column 357: end tag for “img” omitted, but OMITTAG NO was specified …ter/styles/image/glass/1.gif’ alt=’1′><img src=’http://demo.balimechanicweb.ne…

✉

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 273: start tag was here …ter/styles/image/glass/1.gif’ alt=’1′><img src=’http://demo.balimechanicweb.ne…

Error Line 668, Column 441: end tag for “img” omitted, but OMITTAG NO was specified …ter/styles/image/glass/3.gif’ alt=’3′><img src=’http://demo.balimechanicweb.ne…

✉

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 357: start tag was here …ter/styles/image/glass/1.gif’ alt=’1′><img src=’http://demo.balimechanicweb.ne…

Error Line 668, Column 530: end tag for “img” omitted, but OMITTAG NO was specified …ttp://demo.balimechanicweb.net/counter/styles/image/glass/4.gif’ alt=’4′></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 668, Column 441: start tag was here …ter/styles/image/glass/3.gif’ alt=’3′><img src=’http://demo.balimechanicweb.ne…

Error Line 671, Column 241: required attribute “alt” not specified …ns/mechanic-visitor-counter/counter/mvctotal.png’> Total Visit : 1134</td></tr>

✉

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 671, Column 242: end tag for “img” omitted, but OMITTAG NO was specified …ns/mechanic-visitor-counter/counter/mvctotal.png’> Total Visit : 1134</td></tr>

✉

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 671, Column 119: start tag was here …nt-size:2; text-align:Center;color:;’><img src=’http://www.lifestyleblogofathi…

Error Line 672, Column 230: required attribute “alt” not specified …mechanic-visitor-counter/counter/mvctotalhits.png’> Total Hits : 2071</td></tr>

✉

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 672, Column 231: end tag for “img” omitted, but OMITTAG NO was specified …mechanic-visitor-counter/counter/mvctotalhits.png’> Total Hits : 2071</td></tr>

✉

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 672, Column 104: start tag was here …nt-size:2; text-align:Center;color:;’><img src=’http://www.lifestyleblogofathi…

↑ Top
Home
About…
News
Docs
Help & FAQ
Feedback
Contribute

W3COpen-Source

I heart Validator logo

This service runs the W3C Markup Validator, v1.3.

Copyright © 1994-2012 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.