Xibo CMS 1.8.7 Custom - RSS Ticker Problem

hhan · March 13, 2018, 4:17pm

Hello,

The tickers
http://www.tagesschau.de/xml/tagesschau-meldungen/
and
http://www.tagesschau.de/xml/rss2

will not work in version 1.8.7 anymore. Everything was OK in version 1.8.5.

3255 839aa7d 2018-03-13 17:12 WEB GET ERROR / playlist / widget / resource / 45/62 Unable to get feed: XML parsing error
3254 43e6dab 2018-03-13 17:12 XMDS POST ERROR FR Sports Park - UG Bowling Alley GetResource Unable to get feed: XML parsing error
3253 9f3791a 2018-03-13 17:12 WEB GET ERROR / playlist / widget / resource / 45/62 Unable to get feed: XML parsing error
3252 f95c355 2018-03-13 17:12 WEB GET ERROR / playlist / widget / resource / 45/62 Unable to get feed: XML parsing error
3251 42a5023 2018-03-13 17:12 WEB GET ERROR / playlist / widget / resource / 45/62 Unable to get feed: XML parsing error
3250 2b7f779 2018-03-13 17:12 WEB GET ERROR / playlist / widget / resource / 19/26 Incompatible content type: text / html; charset = utf-8
3249 bf51c3c 2018-03-13 17:11 WEB GET ERROR / playlist / widget / resource / 19/26 Incompatible content type: text / html; charset = utf-8
3248 9882cef 2018-03-13 17:11 WEB GET ERROR / playlist / widget / resource / 19/26 Incompatible content type: text / html; charset = utf-8

Best regards

Hubert

alex · March 14, 2018, 8:51am

In 1.8.6, we started to check the Ticker URLs were sane types, as users started putting MPEG video streams and audio stream URLs in there, and the CMS would happily download those over and over and never complete.

It looks like one of your feeds send a mime type of text/html rather than text/xml or similar as we would expect.

If you have control over the source server, you could correct that, or you can adjust the CMS code to accept text/html as a valid type for tickers. You’d need to do that in two places:

github.com

xibosignage/xibo-cms/blob/develop/lib/Widget/Ticker.php#L824


$this->getLog()->debug('Cache Miss, getting RSS items');


// Lock this cache item (120 seconds)
$cache->lock(120);


try {
    // Create a Guzzle Client to get the Feed XML
    $client = new Client();
    $response = $client->get($feedUrl, $this->getConfig()->getGuzzleProxy([
        'headers' => [
            'Accept' => 'application/rss+xml, application/rdf+xml;q=0.8, application/atom+xml;q=0.6, application/xml;q=0.4, text/xml;q=0.4'
        ],
        'timeout' => 20 // wait no more than 20 seconds: https://github.com/xibosignage/xibo/issues/1401
    ]));


    // Pull out the content type
    $contentType = $response->getHeaderLine('Content-Type');


    $this->getLog()->debug('Feed returned content-type ' . $contentType);


    // https://github.com/xibosignage/xibo/issues/1401

and

github.com

xibosignage/xibo-cms/blob/develop/lib/Widget/Ticker.php#L835


    ],
    'timeout' => 20 // wait no more than 20 seconds: https://github.com/xibosignage/xibo/issues/1401
]));


// Pull out the content type
$contentType = $response->getHeaderLine('Content-Type');


$this->getLog()->debug('Feed returned content-type ' . $contentType);


// https://github.com/xibosignage/xibo/issues/1401
if (stripos($contentType, 'rss') === false && stripos($contentType, 'xml') === false) {
    // The content type isn't compatible
    $this->getLog()->error('Incompatible content type: ' . $contentType);
    return false;
}


// Get the body, etc
$result = explode('charset=', $contentType);
$document['encoding'] = isset($result[1]) ? $result[1] : '';
$document['xml'] = $response->getBody()->getContents();

The other feed parsing error will need to be looked at in more detail as the feed looks OK generally.

Peter · March 14, 2018, 10:15am

As Alex has mentioned the first feed fails due to the content type.
We have decided to add support for text/html feeds - https://github.com/xibosignage/xibo/issues/1452
it will be added to the next release.

As for the second feed, it’s application/xml and it did work without any problems for me.

Could you please let us know if the issue with that second feed persists for you?
If so, could you export your layout with that feed, so I can look at the same thing as you?
(send it over private message please)

mwalz · March 27, 2018, 9:34am

We are having exactly the same problem with feed #2 (http://www.tagesschau.de/xml/rss2) here in our company after migrating from Xibo 1.8.2 to 1.8.7. It’s very annoying, please help!

Regards,
Matthias

levynger · May 18, 2018, 1:23am

Same Problem here, in 1.8.9 - parsing error on RSS Feed
http://www.ynet.co.il/Integration/StoryRss3254.xml

used to work in 1.8.3 and 1.8.1.

Peter · May 18, 2018, 8:52am

This one seems to work for me in 1.8.9, it’s application/xml I believe I’d expect it to work in earlier versions as well, but upgrade to 1.8.9 could be a good idea.

That is also reporting application/xml, it should work in 1.8.9.

That being said I did get Unable to get feed: XML parsing error on this feed, however after I saved it to my local /userscripts folder, renamed it and put the local url in my ticker it was able to parse it.

I also removed the line from it <?xml version="1.0" encoding="WINDOWS-1255"?> ( I mean the encoding)

As such I’d say that it is either that line I mentioned or more likely something in the server that hosts the feed that makes it unavailable for Xibo.

levynger · May 18, 2018, 9:44am

The very same. Link rss (ynetnews) works find on 1. 8.3 and 1.8.1 testing env i have…
The recent changes seems to break something…

levynger · February 7, 2019, 10:48am

Getting back again, this time on another RSS feed on CMS 1.8.9, still getting XML Parsing error
the feed type is ok -
Content-Type →text/xml; charset=Windows-1251

https://www.securitylab.ru/_services/export/rss/news/

does any RSS with Encoding attributes will fail to parse ?