Bonjour Jed, Glad to see this releases notes ! It's great to see new about secure server version. I would like to test further, but my skills with the Node.js version are lacking, and I may have some constraints with my web host (which proposes the installation in 1 click of the Node.js TW version, so there would be a way to have some assistance I think if we take the time).
Cheers, Sylvain Le dimanche 13 décembre 2020 à 19:40:21 UTC+1, [email protected] a écrit : > Most of the changes deal with me getting ready for the secure server > version as a possible replacement to Tiddlyspot, there will be an > announcement and demo later. > > There hasn't been as much testing as usual because an adorable kitten > managed to fry my development computer and I have only had my laptop and a > raspberry pi to test on. > > The BobEXE version is available here: > https://github.com/OokTech/TW5-BobEXE/releases/tag/1.7.0b1 > The plugin is available here: https://github.com/OokTech/TW5-Bob > > !! Version 1.7.0 Can of soup > > - clean up some code problems > - add framework for limiting access to settings and plugins based on > login status (secure server only) > - Ensure that the settings are always correctly loaded in some edge > cases > - Add RootWiki to the list of wikis that can be duplicated in the UI > - The disableBrowserAlerts setting now takes input > values yes and no instead of true and false > - Added the option to serve single file wikis without Bob to people > who aren't logged in (secure server only) > - Modify how settings are loaded to work better with the external > server > - Many changes to the internals to work with the external server > better, most don't affect functionality > - improve the http api > ** See the http api documentation for more > > !! Version 1.6.2r2 Une Vie Typique > > - Fixed a regression that would prevent websocket connections if the > wiki had a space in its name. > - Add a /api/status http route that returns settings and other wiki > information > - Switched to using the /api/status route to get wiki settings instead > of the setLoggedIn websocket message to make behaviour more predictable > and > prevent some race conditions > - Lots of refactoring and cleanup on the wiki management functions in > the back-end > - You no longer need to click a button to see the available > plugins/themes/editions/languages on the server. If any new ones are added > while you have a wiki open you need to either refresh the page (the reload > button on your browser, nothing special) or refresh the settings. > - Big update to the http api routes > - Documented the http api > - Fix a crash from a variable scope problem > - Fix a problem with disabling the browser automatically opening > > !! Version 1.6.1 Scream in your heart > > - Changed how saveTiddler messages are handled that reduce the number > of redundant messages. This prevents some undesired behaviour and in some > extreme cases infinite saving loops. > ** This makes some significant speed improvements, everything but > saving many tiddlers in the browser is now close to the speed it was > before > switching to the internal syncer > - Fixed some formatting to fit better with tiddlywiki coding styles > - Fixed the basepath for the file server > - Simplified the file system monitor in a way that should prevent race > conditions when used with external syncing services like git or dropbox > ** Thanks @lineOneTwo <https://github.com/lineOneTwo> > - Fixed the name enableBobSaver so that the GUI can disable the saver > correctly > - Updates to setting the modified flag for a wiki on the server to be > more consistent > - Update action-downloadwiki documentation to show you can set which > core to use and set the default download name > - Improved the handling of uploaded files > - Add proper handling so expired login tokens aren't sent when they > shouldn't be > - Create a single shared method for getting login tokens > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/5b0a3408-3d85-4378-b614-6dba07185102n%40googlegroups.com.
