webpage widget problem

  • 1
  • Problem
  • Updated 3 years ago
  • Solved
I have a web page that runs Javascript to render the HTML and refresh the data every minute. It's been running unchanged for at least a year without issues. Last week all of a sudden it stops refreshing after a few minutes. I'm getting the same behavior on a Windows and Chromebox player. I can't reproduce the problem running directly in a Chrome browser. Has there been a recent update to the player or Chrome that I need to account for? Any advice on how to troubleshoot this is appreciated. 
Photo of Ben Davis

Ben Davis

  • 256 Points 250 badge 2x thumb

Posted 3 years ago

  • 1
Photo of Ashleigh

Ashleigh

  • 3,740 Points 3k badge 2x thumb
Hi Ben,

Our web page widget now allows you to set a refresh interval in the configuration, so there's no need to render Javascript. Under the "Data Refresh Interval" field, select 1 minute from the dropdown.

Let me know if this resolves your issue, I'm unsure as to why your script would suddenly stop working. Have you added any additional elements to your presentation in the past week?

Thanks

Ashleigh
Photo of Ben Davis

Ben Davis

  • 256 Points 250 badge 2x thumb
No changes to the presentation. I also tried the by Content by URL with the same results. I'll try using the Widget refresh in place of and see if that helps.
Photo of Ben Davis

Ben Davis

  • 256 Points 250 badge 2x thumb
I disabled my Javascript refresh and set the widget Data Refresh Interval. After about a 1/2 hr it stops refreshing.

While I was waiting, I updated Chrome on my own system to the latest one (48.0.2564.97) and now it does the same thing. It's looking like a Chrome update problem. 
Photo of Grover Fan

Grover Fan

  • 202 Points 100 badge 2x thumb
Hi Ben,

I'm also having the same problem with players on 48.0.2564.92 (ChromeOS). Players with the older versions (47.x) continue to refresh without issues. I'm currently using the simple META refresh tag in the head and thought that was the problem.

You mentioned that you're using javascript to manage refreshes -- assuming it's the "location.reload()" function.  If that's broken too, I won't bother testing it on my pages.
Photo of Ben Davis

Ben Davis

  • 256 Points 250 badge 2x thumb
My Javascript runs setInterval() to call a function that get data from web service. Then jQuery transforms that into HTML. 
Photo of Grover Fan

Grover Fan

  • 202 Points 100 badge 2x thumb
As of 5:00PM PST today (2/1/16) my pages are refreshing again as normal.  Was there a fix that was pushed to the Web Page Widget that fixed this? If so THANK YOU RISE!!  

I'll keep an eye on this ... and also considering locking down the browser version to a known-good channel.
Photo of Ben Davis

Ben Davis

  • 256 Points 250 badge 2x thumb
I downgraded Chrome to 47 on my Windows player and everything is back to normal. On my other Chromebox player I discovered there was a meta refresh tag in the page. When that fired, all javascript would stop running. I removed the refresh and now I'm back in business. Or at least until the next Chrome update. 
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb
Ben, 

Just to confirm, yours is fixed on Chrome 47, do I have that right? If you upgrade to Chrome 48, do you still see the issue you were seeing originally?
Photo of Ben Davis

Ben Davis

  • 256 Points 250 badge 2x thumb
Yes that is correct. I removed the refresh and now it's working in Chrome 48. 
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb
Thanks for that confirmation Ben!
Photo of Grover Fan

Grover Fan

  • 202 Points 100 badge 2x thumb
Sooo... looks like the issue appears randomly. I set my refresh rate to 5 seconds (for testing) and the video fails to load about 6 out of 10 times.

In any case, I did revert one of my test boxes back to Chrome 47 and the problem no longer exists. But unfortunately, I have all the Chromeboxes set to auto-update the browser ... and by now, all the nodes have been updated.

Would there be conflicting JS instances between the Web Page Widget and target pages that Chrome 48 is borking at?
Photo of Grover Fan

Grover Fan

  • 202 Points 100 badge 2x thumb
Thanks Blake.  Unfortunately the widget points to a page on an internal server:

http://preview.risevision.com/?type=presentation&id=731d93b6-6a02-4910-85be-8335ddfd1928&sho...

Not sure if you can get any useful information from it.  The page in question has the following javascript function that servers as a refresh:

<body onload="javascript:setTimeout(function(){ location.reload();},1800000);">

I've removed the function and am leveraging the "Refresh" option within the Rise Web Page Widget and it seems to be working fine. 

I also notice this problem only happens (for me) on embedded videos. The other widgets (also iframes) on the page (RSS, scrolling marquee, photo show) refresh without any issues. It leads me to believe that I might be looking at this problem here:

https://code.google.com/p/chromium/issues/detail?id=570622

Not sure though... any advice would help.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Grover Fan,

Since we're venturing into some pretty technical areas, I'm not sure how much assistance I can provide. I would be interested if Chrome 49 is also having this issue, though. Would you be willing to be a guinea pig for me and test out Chrome's beta channel with the settings that aren't working in Chrome 48?
Photo of Grover Fan

Grover Fan

  • 202 Points 100 badge 2x thumb
Sure thing Blake.  I'll provision a couple of boxes on the Beta channel and let you know. 

Thanks for your attention on this.  I don't expect much on a fix as it seems it's pretty much Chrome 48 specific. But at least with this test we can confirm our suspicions and post it as a known error.
Photo of Grover Fan

Grover Fan

  • 202 Points 100 badge 2x thumb
Hi Blake,

Confirming that rolling back to Chrome 47 worked. So it looks as if 48.0.2564.92 had some issue with page caching specific to how embedded videos are displayed.

On a similar note, there was an incremental update to 48.0.2564.109 yesterday that seems to have resolved this issue entirely.  I've been running tests for almost 48 hours without any problems with the latest update.

Apologies to Ben Davis for hijacking this thread. I hope that the browser update will fix the issue for you too.

Cheers again to the amazing team at Rise who are always so responsive and willing to help!!  Thanks!
Photo of Ben Davis

Ben Davis

  • 256 Points 250 badge 2x thumb
No apology necessary. My chromebox player updated to48.0.2564.109 as well and is still working as expected.