6.0.9.0 I would tell you what is new but...

[Tinman]

I assume we have to find out ourselves.

 

[bp2008]

I really have to wonder what their release process is, considering how often it comes out without any change log or notes. It could be a simple matter of their cloudflare proxy not having caching configured properly for the changelog URL too. But the smart money is on it being human error during a manual release process, forgetting to update the release notes.

 

[bp2008]

He included UI3-332 at least. So ... you can have UI3's change log I guess.

Version 332​

• Added Check for Updates button to UI Settings > Server Control based on a proposed updatecheck API which is not currently implemented in Blue Iris. Includes automatic fallback to a much simpler update checking interface and a link to the API proposal and documentation.

Version 331​

• Password input fields should now all have a button to make the password visible.
• Fixed a bug where using the "Apply" button to change a profile name caused future attempts to change the name to fail until the profile editor was closed and reopened.

Login page version 35​

• The "user" and "pw" URL parameters are now read by login.htm if they exist and credentials are not already saved.
• Password input fields should now all have a button to make the password visible.

The ball is in their court for implementing the update check API that will allow UI3's new manual update check capability to function. If/when Ken implements that in Blue Iris, UI3 will begin giving you a clone of the Blue Iris News and Updates panel from the local console. It'll be particularly helpful for anyone who (like me) uses UI3 for remote access and finds it cumbersome to log in with remote desktop or equivalent.

 

[IAmATeaf]

I really have to wonder what their release process is, considering how often it comes out without any change log or notes. It could be a simple matter of their cloudflare proxy not having caching configured properly for the changelog URL too. But the smart money is on it being human error during a manual release process, forgetting to update the release notes.

Don't forget that quite frequently the update released on their website isn't what it claims to be!