My feed doesn't parse properly, or does it?

[fox]

Since this problem arises from time to time, I decided to make a simple page which shows how tt-rss will process any given feed. It is available here:

https://fakecake.org/myfeedsucks/

This way you can see whether latest tt-rss trunk parser will accept the problematic feed while excluding potential configuration or network-related problems on your end.

Have fun.

[feader]

That's a good idea. Maybe you also could link to this in the FAQ? Not that I believe many will take notice

BTW: Is it possible to have a link to the FAQ in the forum header, next to where the link to the board software FAQ currently resides (or anywhere up there)? I've never seen that on any forum, but if it was there, we would have so much more reasons to yell at people for not reading before asking.

[fox]

I'm sure it's easy to hack phpbb to display whatever but nobody is going to read it anyway

[Latimer]

My feed at http://www.e1.ru/news/rdf/full_img.xml sucks. When I'm trying to test it, the "Here's what we received" text area is rendered empty.

(The feed unironically sucks. I have no idea how to fix their encoding, and I was hoping to see what they actually feed into tt-rss)

e: great idea, thanks!

[fox]

I dunno why is the textarea empty when the feed parses even though encoding is incorrect. Strange.

[fox]

fixed the encoding issues

[Latimer]

Thanks!

[Exagone313]

I have a problem on a feed, they used & instead of &. What can I do instead of contacting the website - I mean in tt-rss?

[morphus]

My feed sucks agrees that my tt-rss feed (http://myreader.dailybrood.com/index.ph ... 76d32358f9) doesn't parse property. Using Tiny Tiny RSS v17.1 (b8f23d6) in a linux x86_64 shared hosted environment, mysql 5.6.35, php 5.6.30, and apache 2.4.25.

I've read instructions on how to show debug info. Just not sure where, when, or how to use 'f D' to enter update.php --debug info.

[fox]

your feed has a broken URL (index.php/public.php wtf is this?) maybe you should fix SELF_URL_PATH, idk

[linoth]

My feed sucks agrees that my tt-rss feed (http://myreader.dailybrood.com/index.ph ... 76d32358f9) doesn't parse property. Using Tiny Tiny RSS v17.1 (b8f23d6) in a linux x86_64 shared hosted environment, mysql 5.6.35, php 5.6.30, and apache 2.4.25.

I've read instructions on how to show debug info. Just not sure where, when, or how to use 'f D' to enter update.php --debug info.

Basic troubleshooting, dude. Open the URL in a browser, what does it load?

Well, looks like a TTRSS login prompt. Yep, that's not a feed, that won't parse.

fox is right, your URL contains an error, http://myreader.dailybrood.com/public.p ... 76d32358f9 (removed index.php) seems to show up just fine. And surprise, TTRSS can parse a feed it generates just fine.

[morphus]

Removing "index.php" in 'SELF-URL_PATH' indeed resolves parsing complaint. Since this is my first tt-rss install I'm fairly certain the installation step which creates config.php updated SELF_URL_PATH in configuration file.

Thanks. On to next issue ... update cron is failing on shared host. Cron e-mail message full text:

"Failed loading /opt/cpanel/ea-php54/root/usr/lib64/php/modules/ioncube_loader_lin_5.4.so: /opt/cpanel/ea-php54/root/usr/lib64/php/modules/ioncube_loader_lin_5.4.so: undefined symbol: execute Zend Guard Loader requires Zend Engine API version 220100525.

The Zend Engine API version 220131226 which is installed, is newer.
Contact Zend Technologies at http://www.zend.com/ for a later version of Zend Guard Loader."

Searched for answer, found snippet where including "zend_loader.disable_licensing=0" in php.ini might work. Testing now.

[fox]

>Removing "index.php" in 'SELF-URL_PATH' indeed resolves parsing complaint. Since this is my first tt-rss install I'm fairly certain the installation step which creates config.php updated SELF_URL_PATH in configuration file.

yeah, no. it didn't put index.php in there.

e: unless you tried to open index.php/install which is something your tragically misconfigured hosting allows for some unknown reason

>Thanks. On to next issue ... update cron is failing on shared host. Cron e-mail message full text:

i'm glad we have this forum as your personal support center where you can just spam unrelated stuff anywhere while ignoring the rules...

oh wait, that's not how this works. well, gonna give you a few weeks off to figure it out.