Cannot read property ''toString'' of undefined

[stalker145]

Been getting a few of these tonight. Using TT-RSS (currently v15.7) for a few years on RPi running Minibian.

It's not a show-stopper, but it's there...

message

Exception: TypeError: Cannot read property ''toString'' of undefined
Function: unpackVisibleHeadlines()The error will be reported to the configured log destination.
stack_trace

TypeError: Cannot read property ''toString'' of undefined
at htmlspecialchars_decode (http://rss.pcsdtech.com/:297:14)
at http://rss.pcsdtech.com/:472:113
at http://rss.pcsdtech.com/lib/prototype.j ... 910:827:18
at Array.forEach (native)
at Array.each (http://rss.pcsdtech.com/lib/prototype.j ... 910:826:12)
at unpackVisibleHeadlines (http://rss.pcsdtech.com/:471:132)
at headlines_scroll_handler (http://rss.pcsdtech.com/:473:72)
at HTMLDivElement.onscroll (http://rss.pcsdtech.com/:1:1)
source_ip

107.12.147.233
misc_data

{"params":"browserName=Netscape&browserVersion=5.0%20(X11%3B%20Linux%20x86_64)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F54.0.2840.71%20Safari%2F537.36&browserPlatform=Linux%20x86_64&browserCookies=true&ttrssVersion=15.7%20(58a44ec)&initParams=%7B%22on_catchup_show_next_feed%22%3A0%2C%22hide_read_feeds%22%3A1%2C%22enable_feed_cats%22%3A1%2C%22feeds_sort_by_unread%22%3A0%2C%22confirm_feed_catchup%22%3A1%2C%22cdm_auto_catchup%22%3A1%2C%22fresh_article_max_age%22%3A24%2C%22hide_read_shows_special%22%3A1%2C%22combined_display_mode%22%3A1%2C%22icons_url%22%3A%22feed-icons%22%2C%22cookie_lifetime%22%3A86400%2C%22default_view_mode%22%3A%22adaptive%22%2C%22default_view_limit%22%3A30%2C%22default_view_order_by%22%3A%22date_reverse%22%2C%22bw_limit%22%3A0%2C%22label_base_index%22%3A-1024%2C%22theme%22%3A%22reeder.css%22%2C%22plugins%22%3A%22Auth_Internal%2C%20Note%2C%20Af_Comics%2C%20Af_RedditImgur%2C%20Af_Youtube_Embed%2C%20Facebook%2C%20MailTo%2C%20Mark_Button%2C%20OwnCloud%2C%20pushbullet%2C%20Share%2C%20Tweet%2C%20VideoFrames%22%2C%22php_platform%22%3A%22Linux%22%2C%22php_version%22%3A%225.4.45-0%2Bdeb7u5%22%2C%22sanity_checksum%22%3A%22e667f30199dfb16647b718705efc0294f76dc365%22%2C%22max_feed_id%22%3A42%2C%22num_feeds%22%3A27%2C%22hotkeys%22%3A%5B%5B%22c%22%2C%22a%22%2C%22f%22%2C%22g%22%5D%2C%5B%5D%5D%2C%22csrf_token%22%3A%22tn7jid5812b9b9bb536%22%2C%22widescreen%22%3A0%2C%22simple_update%22%3Afalse%2C%22last_article_id%22%3A-1%2C%22cdm_expanded%22%3Atrue%2C%22dep_ts%22%3A1445826909%2C%22reload_on_ts_change%22%3Atrue%7D"}
Your report has been saved. You use the following link to refer to this problem: http://tt-rss.org/report.php?view=c614b ... 4656b38802.

[sleeper_service]

let's see, what is the usual response to someone running ancient software and complaining... *ponder*

[fox]

if you didn't change anything op then it's kinda unlikely it just suddenly broke

[stalker145]

if you didn't change anything op then it's kinda unlikely it just suddenly broke

While I would normally agree with you, as I am not a programmer, I still have to wonder why this would suddenly happen. Many years of running your software with no errors and only updating the OS...

Stupid question: Is it possible that an error such as this could be caused by really shitty internet service? Ours has been dropping the connection a lot lately (mostly the router losing touch with DNS servers) and this error only started last night.

let's see, what is the usual response to someone running ancient software and complaining... *ponder*

I think the answer lies in your methodology for running a site: If it ain't broke, fix it until it is.

As I'm the only user for this server, I prefer to K.I.S.S. and only update when absolutely required. I will, however, try your well articulated suggestion.

:*

[sleeper_service]

let's see, what is the usual response to someone running ancient software and complaining... *ponder*

I think the answer lies in your methodology for running a site: If it ain't broke, fix it until it is.

As I'm the only user for this server, I prefer to K.I.S.S. and only update when absolutely required. I will, however, try your well articulated suggestion.

since I'm in an uncharacteristicly good and generous mood at the moment, I'll respond to your stupid comment.

first, my 'methodology' for running a site is the same as my methodology for running the large and expensive servers that I maintain in my day job... make them work, make them as reliable as I can, and eliminate problems.

if your crap wasn't broken already, it's unlikely you'd be here posting about your broken old crap.

strangely enough, the world of computers isn't set in stone, things DO change, and in case you haven't noticed it, there world around you continues to change also. perhaps your old code isn't going to work with something that changed in a feed, in addition, there are bugs in the code you've got, bugs that have been *fixed* in later code, perhaps a change in a feed tickled one of those to life.

in any event, the *point* of my original comment was, that when you're running old shit, the first thing you're going to be told when you complain about it not working is "upgrade to the current one" because I promise you, fox isn't going to go back to whatever way old version you've got and try and figure out if there's a bug in that.

not that any rational thinking person would believe something so ridiculous anyway.

and only updating the OS...

on the other hand, maybe YOU broke something.

I forget, Fox, should "RPi running Minibian." be in the unsupported category?

[fox]

so, shitty network + shitty server hardware (if you can even call it that), a great combination i'm sure

in any case op i dunno what your actual issue here is. shit worked and now doesn't, i guess. what do you want me to do about it? login on your toy server raspberry pi and investigate why something i wrote a year ago doesn't work right all of a sudden? does this sound like something people would do for you for free? im at a loss, really

e: my well articulated suggestion would be getting a decent server, installing a decent supported OS on it (like debian or centos), and running latest tt-rss git. i'm not sure if it helps but there it is, my suggestion. oh, and, also get yourself a decent network connection to said server.

[stalker145]

perhaps your old code isn't going to work with something that changed in a feed, in addition, there are bugs in the code you've got, bugs that have been *fixed* in later code, perhaps a change in a feed tickled one of those to life.

Now this is a well thought out theory that I can get behind. As things have worked so well for so long with fox's software, I guess I've grown complacent with the updating of that software... oops. I'll give that a shot.

in any event, the *point* of my original comment was, that when you're running old shit, the first thing you're going to be told when you complain about it not working is "upgrade to the current one" because I promise you, fox isn't going to go back to whatever way old version you've got and try and figure out if there's a bug in that.

Funny enough, I have no desire for fox to delve into his archives and try to figure out some random problem. A nod in a direction suffices for me and, kindly enough, you've given that. As for old hardware, it seems that not everyone can have the shinys that you are, obviously, used to. Some people even prefer to make do with less. If that means something stops working down the road because my specs are too low, that's ok, I'll move on. However, the only specs I've seen for running TT-RSS refer to softwares (PHP5.4 ot later - check, and an accelerator recommended - check) with only a few people asking about absurdly low hardware specs.

my well articulated suggestion would be getting a decent server, installing a decent supported OS on it (like debian or centos), and running latest tt-rss git. i'm not sure if it helps but there it is, my suggestion. oh, and, also get yourself a decent network connection to said server.

I can understand your lack of understanding when it comes to supported Operating Systems as no one can be a master of everything in this computer age. Minibian is, actually, Debian-based, only stripped of the cruft that many people like to use to clog their overpowered servers.

And if I could get a decent ISP in this armpit town, I definitely would.

So, thanks, guys, for your kind words and remember: I still love you.

:*

[sleeper_service]

in any event, the *point* of my original comment was, that when you're running old shit, the first thing you're going to be told when you complain about it not working is "upgrade to the current one" because I promise you, fox isn't going to go back to whatever way old version you've got and try and figure out if there's a bug in that.

... As for old hardware, it seems that not everyone can have the shinys that you are, obviously, used to. Some people even prefer to make do with less. If that means something stops working down the road because my specs are too low, that's ok, I'll move on.

if you squint REAL HARD at what I actually wrote, you might note that I didn't say, or even imply, a single thing about your hardware choice. just your ancient version of software. don't ASSume.

I just traded up from my 8 year old thinkpad to a five year old thinkpad, only because my previous one developed weird video issues (which someone on the thinkpad forum suggested was bad video ram). again, don't ASSume, something you're doing way too much of.

[stalker145]

Good news for me!

I tried the recommendations given here and updated to the 16.8 release of TT-RSS and Jessie for Minibian - away from the "ancient" wares that I was using. I haven't had an issue since. Thanks for the suggestions, guys.

I would have said something yesterday, but as you may (or may not) know, it was kinda difficult getting to this domain. I guess everyone runs into problems every once in a while, huh?

[fox]

yeah we had a bit of a network outage at work yesterday

[sleeper_service]

I would have said something yesterday, but as you may (or may not) know, it was kinda difficult getting to this domain. I guess everyone runs into problems every once in a while, huh?

are you just naturally a douchebag, or do you have to work at it?

[stalker145]

yeah we had a bit of a network outage at work yesterday

I'm glad to see you got it fixed. I really do love your work, fox.

are you just naturally a douchebag, or do you have to work at it?

Actually, it comes very naturally... once someone gets under my skin. I rarely start out a conversation with douchiness.

But, hey, sleeper_service, it's been a fun time. Just remember: I still love you :*