Just loaded 789. Browser keep wanting to do a refresh. Not able to work on anything .
Same here - constant need to refresh it.
+1
I tried it last night, and again this morning, in two different browsers (Firefox and Safari) including all the usual clear cache (prefs etc) and force-reload options. I also re-upgraded, just in case there were residual elements of the old build, but no-joy.
After upgrading to 1.0.789, I can no longer use the Vera UI without the dreaded:
[code]VERY IMPORTANT!
You have upgraded Vera, but your browser has cached an old version of the site.Please tell your web browser to reload the page. This is usually done by pressing Ctrl+F5 or choosing Reload from the menu.
Support code: [1.0.787] [1.0.789] [1.0.789]
[/code]
popping up every 30-60 seconds.
It also happens if I use my iPhone to access the Admin interfaces, and I haven’t used it to access Vera in a very long time.
It’s actually my mistake. When coding I run the web engine against my development system and hardcode the javascript version so it matches the .js file. Normally it’s a special token that’s replaced by the build script. When I make a big commit with lots of files, sometimes I forget to uncheck that hardcoded version and it gets committed. I don’t see the error right away since it matches the cache in my browser. Anyway, I just put a check in the build script that it will abort the build if the special token isn’t there. This should prevent it from happening again. Version 790 fixes it.
Confirmed, this fixes the problem for me. 
yup that fixed that…
What about accessing the log through Vera’s advanced tab > Logs?
I’ve been so used to using that I forgot how to telnet into for the logs can you post the link for the info to get the back door logs?