Charles F. Munat wrote:
> Damn. Sometimes I'm a bit dense. I just realized that I created my own
> Menu snippet, overriding the default one. A simple copy and paste fixed
> things.
>
> Just so I'm clear, the XML error is because the tag
> appeared in the output, and the tag appeared in the ou
Damn. Sometimes I'm a bit dense. I just realized that I created my own
Menu snippet, overriding the default one. A simple copy and paste fixed
things.
Just so I'm clear, the XML error is because the tag
appeared in the output, and the tag appeared in the output because the
"group" function t
If the error is occurring in the browser, it's because the
is not getting processed.
So, what's the page source (the stuff that's getting delivered to the
browser)?
Charles F. Munat wrote:
> I'm still not clear on what causes this type of error:
>
> XML Parsing Error: prefix not bound to a n
