Page 2 of 2

Re: Feed problems with 1.7.9, both still work fine on 1.7.8

Posted: 16 May 2013, 02:20
by mx2
If the good folks at typepad have made a mistake we should let them know because they have fucked up all their customers.

In any event, it's working now with 1.7.9 - I'll report if I notice any other breakage. Thanks for the quick fix - much appreciated!

Re: Feed problems with 1.7.9, both still work fine on 1.7.8

Posted: 16 May 2013, 02:49
by gbcox
dxbi wrote:Just noticed that feeds from Gitlab broke in pretty much the same way but while the dick feed appears to be working, this feed still has no markup: http://www.stunet.tu-freiberg.de/~eckho ... board.atom


Yeah, I checked your feed and the typepad mentioned above: http://everything.typepad.com/blog/atom.xml

Both are having formatting issues... MoP appears to be fixed now, however...

Re: Feed problems with 1.7.9, both still work fine on 1.7.8

Posted: 16 May 2013, 09:14
by fox
Ah, I'll check for the type then.

Edit: update to the above patch:

https://github.com/gothfox/Tiny-Tiny-RS ... 13cf1a0614

Re: Feed problems with 1.7.9, both still work fine on 1.7.8

Posted: 16 May 2013, 10:13
by phz
dxbi wrote:
fox wrote:It is technically valid, it's just the content is in unexpected format. Like posted above, usually it is escaped and wrapped in a CDATA section.


If I understand the RFC correctly, type=xhtml is expected not to be escaped: http://tools.ietf.org/html/rfc4287#section-3.1.1

My early assertion that it was "invalid by a large margin" was actually wrong by the very link I posted to the specification in that post. Multi-level tag markup is valid in descriptions, as long as it's interpretable as XML (most prevalently: has correctly closed tags), which valid XHTML should be. Why RSS is seldom used this way (from what I've seen) I guess is that a single markup error in the XHTML would bork the entire XML tree for the feed.

HTML on the other hand has an implicit way to specify its DOM, where closing (and many starting) tags are not needed in many cases. Throwing perfectly valid HTML into an RSS feed unescaped would most likely crash and burn, since it wouldn't be valid XML any longer.

(Actually, thinking about it I must say that the "unescaped XHTML" way makes more sense than escaping HTML, declaring it as text and then let feed readers unescape and interpret it as HTML anyway. I guess this is one of the reasons some people cry when they think about RSS.)

Re: Feed problems with 1.7.9, both still work fine on 1.7.8

Posted: 16 May 2013, 10:23
by gbcox
I think you've nailed it...
I've gone through several random typepad blogs and looked at their entries and everything is matching
the posts perfectly. In fact, some things are being dropped by GR and Newsblur, but are
reproduced fine by ttrss.

Re: Feed problems with 1.7.9, both still work fine on 1.7.8

Posted: 26 May 2013, 17:29
by wanjas
fox wrote:Here's an experimental fix. I'm seeing a lot of cocks right now, so it seems that it is working.

https://github.com/gothfox/Tiny-Tiny-RS ... fe40ec0c01

Report if it breaks other feeds or whatnot.


Thanks, it seams working good for me. Other atom feeds with escaped content still work correct.

Re: Feed problems with 1.7.9, both still work fine on 1.7.8

Posted: 04 Jun 2013, 14:30
by Filin
i have the same issue with few feed, and fix for atom 0.3 did not helped.
could you please take a look and clarify what is wrong?
here is feed urls:
http://0day.kiev.ua/rss.php - in 1.7.9 feed is marked as unsupported
http://lostfilm.tv/rssdd.xml - in 1.7.9 feed is marked as unsupported
http://4pda.info/rss.xml - in 1.7.9 feed is marked as unsupported

All these feed where working normally in 1.7.8

Thank you in advance

Re: Feed problems with 1.7.9, both still work fine on 1.7.8

Posted: 04 Jun 2013, 15:25
by fox
Check on trunk first, report if anything is still broken.

Re: Feed problems with 1.7.9, both still work fine on 1.7.8

Posted: 04 Jun 2013, 22:57
by Filin
just checked on version from trunk. here are errors for the feeds
4PDA.INFO - Все для Pocket PC(http://4pda.info/rss.xml): LibXML error 32 at line 1 (column 42): Unsupported encoding windows-1251
LostFilm.TV(http://lostfilm.tv/rssdd.xml): LibXML error 32 at line 1 (column 42): Unsupported encoding windows-1251
0day - Cофт и Видео в UA-IX(http://0day.kiev.ua/rss.php): LibXML error 32 at line 1 (column 42): Unsupported encoding windows-1251

Re: Feed problems with 1.7.9, both still work fine on 1.7.8

Posted: 04 Jun 2013, 23:29
by fox
Most probably your php (or the platform php is running on) has incomplete and/or otherwise broken support for iconv, there's nothing I can do about it.

4pda feed works fine for me on trunk.

Re: Feed problems with 1.7.9, both still work fine on 1.7.8

Posted: 05 Jun 2013, 00:01
by Filin
fox wrote:Most probably your php (or the platform php is running on) has incomplete and/or otherwise broken support for iconv, there's nothing I can do about it.

4pda feed works fine for me on trunk.

it's running on a synology nas. thank you for a quick answer, i'll check php configuration