RSS errors: "XML Parsing Error..." Mantis 1.0.0rc3

Get help from other users here.

Moderators: Developer, Contributor

Post Reply
oreo_masta
Posts: 1
Joined: 20 Jan 2006, 18:10
Location: Minnesota, US
Contact:

RSS errors: "XML Parsing Error..." Mantis 1.0.0rc3

Post by oreo_masta »

Hello,

First and foremost thank you for the Bugtracker! It's great! I love its layout. I am having a problem with the Yoper Linux bugtacker: http://www.yoper.com/bugtracker/main_page.php

All of our news feeds, both the news_rss.php and issues_rss.php are having problems. I have been trying to focus on getting news_rss.php sorted first. Our error is:
XML Parsing Error: xml processing instruction not at start of external entity
Location: http://www.yoper.com/bugtracker/news_rs ... oject_id=1 [^]
Line Number 2, Column 1:

<?xml version="1.0" encoding="windows-1252"?>
I've seen this error several times in your bugtracker (as I've done some homework) but never saw any solid solutions. This is the best bug I could find: http://bugs.mantisbt.org/view.php?id=5512 Additionally, the feed does not work in my RSS aggregator either.

That didn't say too much. I've also visited: http://www.futureware.biz/blog/index.ph ... &tb=1&pb=1 and could not find much in the way of troubleshooting.

As I understand our version (1.0.0rc3) is beyond where the fix was implemented but we're still getting errors. I took a look at news_rss.php, issues_rss.php, and class.RSSBuilder.inc.php and couldn't see anything that stuck out. Admittedly, I'm not the greatest php guy on the face of the earth, but I took a look at the files nonetheless. Does anyone have any ideas on what could help us out with news_rss.php?
Narcissus
Developer
Posts: 338
Joined: 17 Feb 2005, 09:45

Post by Narcissus »

It looks like for some reason there's whitespace showing up before the output begins. This generally occurs when a file (either configuration or code) has been edited and saved with whitespace outside of the <?php and ?> tags.

Normally when this happens in the Mantis config file, the error shows up as a 'headers already sent' error, so I'm wondering if maybe there is another file that you have edited and added whitespace to?

That whitespace can be just a newline after the closing ?> PHP tag, too.

But that's what I'd look for: rogue whitespace (maybe with the help of a decent differ).
Post Reply