search

jparyani / Tiny-Tiny-RSS

A PHP and Ajax feed reader
http://tt-rss.org/
GNU General Public License v2.0
10 stars 6 forks source link

Exception: TypeError, reply.headlines is undefined #19

Open timshannon opened 7 years ago

timshannon commented 7 years ago

I've started getting the error below when going into my tiny tiny rss grain.

EXCEPTION: Exception: TypeError, reply.headlines is undefined
Function: headlines_callback2()
Location: :371  e93d3bc166b811fdb96f2c7f9bba592f.townsourced.com:129:1
    format_exception_error https://e93d3bc166b811fdb96f2c7f9bba592f.townsourced.com/:129:1
    exception_error https://e93d3bc166b811fdb96f2c7f9bba592f.townsourced.com/:120:346
    headlines_callback2 https://e93d3bc166b811fdb96f2c7f9bba592f.townsourced.com/:388:22
    viewfeed/_viewfeed_timeout</<.onComplete https://e93d3bc166b811fdb96f2c7f9bba592f.townsourced.com/:330:232
    Ajax.Request<.respondToReadyState https://e93d3bc166b811fdb96f2c7f9bba592f.townsourced.com/lib/prototype.js:1617:8
    Ajax.Request<.onStateChange https://e93d3bc166b811fdb96f2c7f9bba592f.townsourced.com/lib/prototype.js:1547:7
    bind/<

An unhandled exception modal pops up, then tiny tiny rss resets and gets stuck in a startup loop, continually throwing the error above.

Also, It looks like it then tries to post the error to the backend, but that fails with an error code 6, which from my reading on the tiny tiny rss forums means an issue with the CSRF token.

I'm on firefox 51.0.1 on Ubuntu 16.10. The error goes away, and tiny tiny rss works fine if I start up tiny tiny rss in a private window, or in a clean firefox session. This leads me to believe it's something stored locally that's causing the issue.

I've tried disabling all firefox addons, but that didn't help. I've tried clearing all localstorage but that didn't help either.

It wasn't until I cleared all my cookies for my entire sandstorm domain that I was able to get tiny tiny rss to work again.

I'm not entirely sure what caused the issue, but clearing cookies fixed it for now. It's probably a downstream issue, but that community is a bit toxic, so I thought posting here with a temp work around might be useful to others.

I'll add more detail if I can figure out how to replicate this issue.