Company Christmas Holidays
North American Headquarters in Miami, USA: Dec 25, 2015, Jan 1st 2016
European Headquarters in Muenster, Germany: Dec 21, 2015 until Jan 03rd 2016
Limited support is available during this period.
We at PROVISIO wish you Merry Christmas and a Happy New Year!

 

Support Request: Site failed to load properly due to outdated chromium browser

Description

Site kiosk uses chromium 59, which is a year and half out of date. How can I update that to the latest chromium version? I know you guys use CEF, and latest version of CE is at chromium 70. This is blocking our production deployment.

Answer: (4)

Re: Site failed to load properly due to outdated chromium browser PROVISIO\adams (Provisio) 11/1/2018 2:54 PM
Unfortunately, there is not a way to manually update the Chromium browser within Sitekiosk. However, there should be an update to the browser with the pending release of our next version of Sitekiosk 9.7. I believe the version it is being updated to is CEF 66. In the mean time, are you able to use the IE browser option to display what you need to display?
Re: Site failed to load properly due to outdated chromium browser Wei (User) 11/1/2018 3:24 PM
Thanks for the update. IE has other challenges. I think Chrome 66 is going to get us there. What's the timing for the 9.7 release?
Re: Site failed to load properly due to outdated chromium browser PROVISIO\adams (Provisio) 11/2/2018 3:49 PM
Another possibility (until the 9.7 is released) might be to change the user agent:

http://devblog.provisio.com/post/2017/02/20/Changing-the-User-Agent-of-the-SiteKiosk-Windows-Chrome-Browser.aspx

You can try using the user agent from the current version of Chrome and see if this might work for you:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

as far as an ETA for 9.7, it should be within the next few months pending testing.
Re: Site failed to load properly due to outdated chromium browser Wei (User) 11/2/2018 6:33 PM
The problem is there are bugs in Chrome 59 that's causing our site to not load. So changing user Agent string won't help in this case. Is there no other way to fix this? waiting a few months isn't really an option for us at this point.