Since June 22nd, Google has begun requiring an API key in order to use google maps on your website. Without the key, you see an 'Oops! Something went wrong.' notice instead of the map. This affects anyone using WSN's maps features on a new website. Pre-existing websites are exempted from this requirement, at least for the moment, as google doesn't wish to break the entire internet -- but they warn that the quality of service will be lower for the legacy keyless sites and recommend getting a key.
If you're in the European Union, or some of your clients are, you're probably aware of the EU requirement to notify visitors that your website uses cookies. In today's WSN 10.0.9 Beta 1 release, I've added an 'EU cookie privacy notice' switch at Admin Panel -> Settings -> Switches. Enabling this switch automatically handles your legal obligations by adding a cookie notice in a semi-transparent bar at the bottom of the screen. The visitor can dismiss the notice by clicking the X (which, appropriately enough, sets a cookie lasting one year to remember that they've dismissed it).
For a long time, it has been easy to convert a WSN site to use https:// secure URLs by default: simply change the http to https in the URL at Admin -> Settings -> System Configuration -> WSN Links Installation Details -> URL. But this misses two common scenarios: the case where you want non-secure to be the default but want to allow people to use a secure version if they choose, and the case where you want to forcibly redirect to the secure version of each URL. What if you want to optionally enable https, while leaving http as the default?
The big enhancement in WSN 10.0.8 is submenus support for the main menu in the menu manager. This solves the problem of having more pages than you have horizontal space for on the menu bar. In new installations, the Options menu is a submenu associated to the member home menu, such that everything from the member home menu automatically shows on it. If you wish you can disassociate this and build a custom options submenu. Bootstrap themes use the native bootstrap menu javascript and css. Non-bootstrap themes use superclick.
When you set up a website, there are two ways people can access it: www.yourdomain.com, or just yourdomain.com. This creates a couple of problems. First, unless you've set the site's cookie domain to .yourdomain.com, when someone logs in at yourdomain.com they won't be logged in at www.yourdomain.com -- which leaves them confused if they end up on the other version from a link they found somewhere. Secondly, search engines don't like the duplication. The solution for this has always been to add redirection into the .htaccess file to redirect www URLs to their non-www equivalents or vice versa.