feedburner can't parse feed everyone else can because "content of elements is not well formed" ; feed broken.

33 views
Skip to first unread message

Domain Admin

unread,
Mar 22, 2021, 4:32:20 PM3/22/21
to FeedBurner Help Group
Hello, 

our feed : https://feeds.feedburner.com/OpenCulture stopped sending out its email this weekend.  (The feed is generated on the website as https://www.openculture.com/?feed=narrowemail)

when I go to troublshootize and try to resync the feed, I get this message:

There is an issue that must be addressed with your source feed for the feed "Open Culture"

The URL you entered does not appear to be a valid feed. We encountered the following problem: Error on line 98: The content of elements must consist of well-formed character data or markup.

I am puzzled by this extremely vague error message.  My guess is that it is some sort of encoding  error.   


The lines 97-101 in the feed are:


97. <!-- permalink:https://www.openculture.com/2021/03/three-leonard-cohen-animations.html--></p>

98. <p><a rel="nofollow" href="https://www.openculture.com/2021/03/three-leonard-cohen-animations.html">Three Leonard Cohen Animations</a> is a post from: <a href="https://www.openculture.com">Open Culture</a>. Follow us on <a href="https://www.facebook.com/openculture">Facebook</a>, <a href="https://twitter.com/#!/openculture">Twitter</a>, and <a href="https://plus.google.com/108579751001953501160/posts">Google Plus</a>, or get our <a href="http://www.openculture.com/dailyemail">Daily Email</a>. And don't miss our big collections of <a href="http://www.openculture.com/freeonlinecourses">Free Online Courses</a>, <a href="http://www.openculture.com/freemoviesonline">Free Online Movies</a>, <a href="http://www.openculture.com/free_ebooks">Free eBooks</a>, <a href="http://www.openculture.com/freeaudiobooks">Free Audio Books</a>, <a href="http://www.openculture.com/freelanguagelessons">Free Foreign Language Lessons</a>, and <a href="http://www.openculture.com/free_certificate_courses">MOOCs</a>.</p>

99. ]]></description>

100. <content:encoded><![CDATA[<div class="oc-video-wrapper">


Feedburner is reporting line 98 as having the problem, but i supsect there might be a counting discrepancy and it is either the line 99 or 100 embed that is being triggered.  The feed validates on the w3 validator just fine.


My  question here is : is there a way to give feedburner what it wants, either by changing wordpress wrapping  code OR by changing the document encoding in the header?  Or is this a problem with the feedburner service?


I'm insterested in any and all suggestions!

thanks




Reply all
Reply to author
Forward
0 new messages