https://legacy.forums.gravityhelp.com/topic/ajax-causing-xml-parsing-error-76 Gravity Support Forums Topic: Ajax Causing XML Parsing Error 76 en-US Sat, 04 Apr 2026 12:21:52 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/ajax-causing-xml-parsing-error-76#post-25236 Tue, 10 May 2011 16:35:18 +0000 Cliff Seal 25236@https://legacy.forums.gravityhelp.com/ <p>You can view a sample feed I set up here with the same post in it: <a href="http://beta.mtbethel.org/category/blog/feed" rel="nofollow">http://beta.mtbethel.org/category/blog/feed</a></p> <p>It's a little hard to reproduce the error and may be due to the way iOS parses the XML, not the way GF writes it. The script tag is obviously written correctly- here's a snippet of just the item element: <a href="http://pastebin.com/imYAMiW2" rel="nofollow">http://pastebin.com/imYAMiW2</a></p> <p>Thanks for your help! I realize this may not be a GF issue, but thought it was worth asking since you guys are helpful. </p> https://legacy.forums.gravityhelp.com/topic/ajax-causing-xml-parsing-error-76#post-25230 Tue, 10 May 2011 16:04:20 +0000 Carl Hancock 25230@https://legacy.forums.gravityhelp.com/ <p>There wouldn't be a close script tag without an open script tag. I'm not sure what content you are pulling in, but something isn't right. Can you point to a link to a page that has this AJAX error? </p> https://legacy.forums.gravityhelp.com/topic/ajax-causing-xml-parsing-error-76#post-25226 Tue, 10 May 2011 15:41:58 +0000 Cliff Seal 25226@https://legacy.forums.gravityhelp.com/ <p>I built an iOS application several months ago in which I'm pulling a category feed, parsing, and displaying. If a Gravity Form (Gravity Forms form?) is embedded in the page with Ajax, I receive an XML parsing error (pasted below). If I disable Ajax, everything works well.</p> <p>I'm glad there's a simple fix, but is there any way to solve this? I enjoy the Ajax feature and would love to be able to use it seamlessly since the same posts are read both in a browser and in an iOS app.</p> <p>W3C Validation errors:<br /> Line 61, Column 1973: end tag for element "script" which is not open</p> <p><code>…gformRedirect();}});});/*]]&gt;*/&lt;/script&gt;]]&gt;&lt;/content:encoded&gt; &lt;wfw:commentRss&gt;h…</code></p> <p>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.</p> <p>If this error occurred in a script section of your document, you should probably read this FAQ entry.</p> <p> Line 61, Column 1974: marked section end not in marked section declaration</p> <p><code>…formRedirect();}});});/*]]&gt;*/&lt;/script&gt;]]&gt;&lt;/content:encoded&gt; &lt;wfw:commentRss&gt;ht…</code> </p>