[TW5] BobEXE for testing, version 1.2.3

[Jed Carty]

This should be a link to the different executables for BobEXE version 1.2.3

This thread is specifically about version 1.2.3, any bugs that are uniquely related to previous versions are not going to be addressed here.

Information about how to make an appropriate bug report is available here: https://www.ooktech.xyz:8443/Public#How%20to%20make%20a%20good%20bug%20report

I will be handling any bug report that contains the appropriate information before looking into any others.

If you want to test out the new features here is a link to the folder for downloading:

https://www.dropbox.com/sh/c2s22zy4oaal8wz/AACQ7GGEIDYyyKxZ2Q_iWuZba?dl=0

Back up your data, this may be unstable and may have all sorts of bugs. This is for testing before the full release.

The changelog, and things to test, is here:

!! Version 1.2.3 Boiled Potatoes

- Setting up the file server is simpler now
  - In the Bob Settings tab of the control panel there is a file server tab that lets you check a box to enable the server.
  - There are also text boxes that let you set the folder where files are served from and the path prefix for files
- The makeImagesExternal message was added. It takes all of the embedded media in a wiki and copies it into the folder for the file server and replaces the media tiddlers with tiddlers that have a _canonical_uri field pointing to the media file.
  - An option lets you copy the files into the globally available file folder or into the wiki specific file folder.
- Add interface to duplicate an existing wiki
  - You can optionally duplicate all of the child wikis that are contained in the folder of the wiki you are duplicating.
- Add interface to rename/move a wiki
- Add interface to delete a wiki, you can optionally delete all of a wikis children as well.
- Fixed some potential bugs dealing with paths when creating new wikis.
- Reordered some functions to make wiki creation more consistent.
- Added browser alerts for server events (like confirmations of creating or deleting wikis, fetching tiddlers, etc.)
  - There is a control panel tab that lists a history of server messages.
- Possibly fix a bug that could add incorrect path prefixes when using filters in $:/config/FileSystemPaths .

!! Version 1.2.2r5 Fried Potatoes

- Wikis can now be hosted on paths to other wikis. You can have both '/students' and '/students/eve'
  - No wikis can have the name `__path`
  - The way that wiki paths are listed has changed, but settings files are updated automatically without needing any manual editing.
- Lots of small back-end optimisations that hopefully reduce the memory usage.
- Improvements for reconnecting to and resyncing with a server after being disconnected
- Added an option to have verbose or compact help and documentation in the control panel.
- Fix the manual settings losing focus problem
- Improve the manual settings layout and interface a little
- Fix some situations where the tiddlywiki/filesystem and tiddlywiki/tiddlyweb were included when they shouldn't be
- Fix a bug that prevented internal fetch from working with a transform filter (and possibly in other situations)
- (BobEXE) the Wikis, Plugins, Themes and Editions folders are all now created automatically in a default location in the same folder as the executable.
- Fixed another bug that would sometimes allow a wiki with the same name as an existing wiki to be created
- You can now access the full settings interface from any wiki by checking a box in the control panel.
- Hopefully fix a race condition that could result in multiple wikis being created for a single command.
- Automatically populating the wiki list will now properly find wikis inside other wiki folders.
- Add an interface to manage themes like the manage plugins interface.
- You can now fetch plugins directly from github. (VERY EXPERIMENTAL)
  - This required two external modules that are now included in the Bob plugin
    - An updated (and not backwards compatible) jszip
    - follow-redirects
  - On GitHub.com or GitLab.com you can give the repo url to get the plugin
  - For github the repo url will be something like this `https://github.com/OokTech/TW5-RandomValue`, there is some special handling to get the zip url from the repo url for github.
  - for gitlab the repo url will be something like this `https://gitlab.com/inmysocks/ookbot`, there is also special handling to get the url for the zip from gitlab.com repos.
  - Anywhere else you have to give the full url for the zip file itself.
- Fix a bug where unicode or other uri encoded wiki names wouldn't work, this includes many south-east asian alphabets and character sets.
  - This also means that wikis can have spaces and emojis in their names

[Mark S.]

Minor things --

1. The [Click here] to set the host to 0.0.0.0




continues not to work. That is, the address continues to be 127.0.0.1 even after the server is manually reset.




2. Making a change that requires a reset (like adding plugins) creates the red "reset" message. To get the message to go away, you have to close down the server manually and restart.








3. The manage plugins page says to "Select which plugins you want in this wiki below then click Update Plugins"




The actual button, I think,  is labeled "Save Plugin Selection".




Windows 7, FF 66.0.3




-- Mark




[Jed Carty]

For 2, you don't have to restart the server, just reload the wiki. When you put in a new plugin you have to refresh the wiki the same as you have to when you install a new plugin with a single file wiki or using the node server.

If just reloading the page isn't working for you there is some other bug.

[Mark S.]

Well that's simple enough. But the there's this "Reconnect" button that gives the illusion that you just have to press it and the problem is fixed. Maybe just a message that says "Reload browser to reconnect" ?

Thanks!

-- Mark

[TonyM]

Jed et al..

Thanks for the continuing development of Bob and simple to use Bobexe. Of late I have needed to exit the use of Bob for my critical Wikis as I have too many issues arising. I have thus returned it to an evaluation platform and installed the latest version. The Export Wiki feature has helped me here thank you, using save rather than download, Download gives me the error "Internal Javascript error "TypeError: invalid assignment to const `excludeList'"

• Jed I understand you do not have the windows platform to test on so let me know if there are specific tests you want me to undertake.
• I keenly want to use the features in Bob but still find the instructions and documentation difficult, it's more that they are terse, to the point and technical. I have trouble extracting the conceptual understanding behind the various features I want to use. Perhaps this is because I do not understand tiddlywiki on NodeJS and this understanding is written between the lines.  It also stops me trouble shooting problems I face in bob.
• As offered before I am keen to help the adoption of Bob and documentation but so far I have not being able to build the expertise in Bob to do this, and the Windows platform adds additional distance.

Key issues

1. No matter that a wiki is saved, I get this message navigating away from a Wiki, "This page is asking you to confirm that you want to leave - data you have entered may not be saved"
   With a number of WIkis open closing my browser becomes a chore.
2. Are all the features basically setup by appropriate changes to the settings? perhaps using $:/plugins/OokTech/Bob/Configuration as a Guide?
3. Because I find it hard to get the concepts behind the features I am not sure what relates to all wikis, the root wiki or the child wikis eg the Plugin folder
4. I am getting unexpected closures of the console or the Error messages below

Current problem on console, stopping Bob Master connecting to server?

Unload wiki  RootWiki
WebSocket error:  Error: WebSocket is not open: readyState 2 (CLOSING)
    at WebSocket.send ($:/plugins/OokTech/Bob/External/WS/lib/websocket.js:315:19)
    at sendAck ($:/plugins/OokTech/Bob/NodeMessageHandlers.js:35:56)
    at Object.$tw.nodeMessageHandlers.unloadWiki ($:/plugins/OokTech/Bob/NodeMessageHandlers.js:1275:5)
    at WebSocket.$tw.Bob.handleMessage ($:/plugins/OokTech/Bob/NodeWebSocketsSetup.js:151:52)
    at $:/plugins/OokTech/Bob/NodeMessageHandlers.js:459:31
    at Array.forEach (<anonymous>)
    at Object.$tw.nodeMessageHandlers.syncChanges ($:/plugins/OokTech/Bob/NodeMessageHandlers.js:456:11)
    at WebSocket.$tw.Bob.handleMessage ($:/plugins/OokTech/Bob/NodeWebSocketsSetup.js:151:52)
    at $:/plugins/OokTech/Bob/NodeMessageHandlers.js:459:31
    at Array.forEach (<anonymous>)
WebSocket error:  TypeError: Cannot read property 'wiki' of undefined
    at $:/plugins/OokTech/Bob/NodeMessageHandlers.js:469:52
    at Array.forEach (<anonymous>)
    at Object.$tw.nodeMessageHandlers.syncChanges ($:/plugins/OokTech/Bob/NodeMessageHandlers.js:463:18)
    at WebSocket.$tw.Bob.handleMessage ($:/plugins/OokTech/Bob/NodeWebSocketsSetup.js:151:52)
    at $:/plugins/OokTech/Bob/NodeMessageHandlers.js:459:31
    at Array.forEach (<anonymous>)
    at Object.$tw.nodeMessageHandlers.syncChanges ($:/plugins/OokTech/Bob/NodeMessageHandlers.js:456:11)
    at WebSocket.$tw.Bob.handleMessage ($:/plugins/OokTech/Bob/NodeWebSocketsSetup.js:151:52)
    at $:/plugins/OokTech/Bob/NodeMessageHandlers.js:459:31
    at Array.forEach (<anonymous>)
WebSocket error:  TypeError: Cannot read property 'wiki' of undefined
    at $:/plugins/OokTech/Bob/NodeMessageHandlers.js:469:52
    at Array.forEach (<anonymous>)
    at Object.$tw.nodeMessageHandlers.syncChanges ($:/plugins/OokTech/Bob/NodeMessageHandlers.js:463:18)
    at WebSocket.$tw.Bob.handleMessage ($:/plugins/OokTech/Bob/NodeWebSocketsSetup.js:151:52)
    at $:/plugins/OokTech/Bob/NodeMessageHandlers.js:459:31
    at Array.forEach (<anonymous>)
    at Object.$tw.nodeMessageHandlers.syncChanges ($:/plugins/OokTech/Bob/NodeMessageHandlers.js:456:11)
    at WebSocket.$tw.Bob.handleMessage ($:/plugins/OokTech/Bob/NodeWebSocketsSetup.js:151:52)
    at WebSocket.emit (events.js:182:13)
    at Receiver.receiverOnMessage ($:/plugins/OokTech/Bob/External/WS/lib/websocket.js:720:20)
WebSocket error:  TypeError: Cannot read property 'wiki' of undefined
    at $:/plugins/OokTech/Bob/NodeMessageHandlers.js:469:52
    at Array.forEach (<anonymous>)
    at Object.$tw.nodeMessageHandlers.syncChanges ($:/plugins/OokTech/Bob/NodeMessageHandlers.js:463:18)
    at WebSocket.$tw.Bob.handleMessage ($:/plugins/OokTech/Bob/NodeWebSocketsSetup.js:151:52)
    at WebSocket.emit (events.js:182:13)
    at Receiver.receiverOnMessage ($:/plugins/OokTech/Bob/External/WS/lib/websocket.js:720:20)
    at Receiver.emit (events.js:182:13)
    at Receiver.dataMessage ($:/plugins/OokTech/Bob/External/WS/lib/receiver.js:415:14)
    at Receiver.getData ($:/plugins/OokTech/Bob/External/WS/lib/receiver.js:347:17)
    at Receiver.startLoop ($:/plugins/OokTech/Bob/External/WS/lib/receiver.js:134:22)

I truly love the Bob features but I am struggling at the moment to implement them. Returning Bob to a test environment frees me to learn more by experimentation and hopefully overcome these adoption barriers, I take full responcibility for my own limitations here.

Regards

Tony

On Sunday, April 21, 2019 at 7:46:46 AM UTC+10, Jed Carty wrote:

This should be a link to the different executables for BobEXE version 1.2.3

[Mark S.]

Hi Tony,

On Sunday, April 21, 2019 at 5:56:33 PM UTC-7, TonyM wrote:

Because I find it hard to get the concepts behind the features I am not sure what relates to all wikis, the root wiki or the child wikis eg the Plugin folder

I can explain what worked for me -- can't guarantee that it was the "right" thing, but it did work and I could see how it could be convenient.

 

What I did was set this to point to a path where I want to keep extra Plugins. Then I downloaded a plugin from github. It was one of Jed's, actually, so I put it below "OokTech". That is

<plugins folder>/OokTech/TW-External-Server/

Now when you open a wiki, you can go into the Bob's settings in the control panel, and under "This Wiki" select "Update Plugins". Then you can select which plugins you want to include in the wiki. The list will include the ones you have in your custom Plugins folder. After selecting the plugins you want, you can click on "Save Plugin Selection" and then reload to activate the plugin.

-- Mark

[Jed Carty]

I realise I should have put this is the first post, but here is a link to one of the wikis served on Bob on ooktech.xyz with some information about how to give an effective bug report or feature request: https://www.ooktech.xyz:8443/Public#How%20to%20make%20a%20good%20feature%20request:%5B%5BHow%20to%20make%20a%20good%20feature%20request%5D%5D%20%5B%5BHow%20to%20make%20a%20good%20bug%20report%5D%5D

Tony,

What did you do before getting that message? If it was changing plugins or something similar than I may know where the bug is but I need context.
The error starting with 'Unload wiki RootWiki' means it is almost certainly not a windows problem.

1 - I keep forgetting that this happens. There was something simple I can do to disable that but I keep getting distracted I will look for it now.

2 - yes, but I have been moving more toward putting everything in the control panel tab with better explanations. But to use Bob you don't have to configure anything, particularly with BobEXE you can just start it up and it should give you something that works. Changing any of the more advanced settings is, I think, generally not required.

3 - There is documentation in the control panel, but I need more specific feedback than this to determine which parts I should be focusing on

4 - I really need context to say anything useful, and maybe the content of your settings.json file (you can just copy the text from the manual setting tab).

[Jed Carty]

I updated the executables in the dropbox folder.

[TonyM]

Jed,

I will follow your feature and bug report process, but only from a newly installed test base of BobWin.exe.

Windows 10, TiddlyWiki version 5.1.19 with Bob version 1.2.2r2

I can confirm that item one above is re-ocurring on a new test base;

1. No matter that a wiki is saved, I get this message navigating away from a Wiki, "This page is asking you to confirm that you want to leave - data you have entered may not be saved"
   With a number of WIkis open closing my browser becomes a chore.

• Changes are immediately saved on a new or edited tiddler (according to the console) and the save changes button is dull (ie not red), in fact I never see it as red.
• If I try and navigate away from or reload the master or any child wiki after such a change I get the confirm if you want to leave prompt.
• If I do leave/reload the Wiki it does so, and reopens next time including the recently saved changes, ie no loss is occuring
• The filter [haschanged[]] results in a list of tiddlers modified in the current session, after save/reload, My own recently changed tiddlers no longer appear in this list.

My Guess is that bob is not resetting a TiddlyWiki or HTML standard "dirty" flag after it's save. 

Thanks in advance

Tony

[TonyM]

Jed,

On Item 2 above 

2. Are all the features basically setup by appropriate changes to the settings? perhaps using $:/plugins/OokTech/Bob/Configuration as a Guide?

yes, but I have been moving more toward putting everything in the control panel tab with better explanations. But to use Bob you don't have to configure anything, particularly with BobEXE you can just start it up and it should give you something that works. Changing any of the more advanced settings is, I think, generally not required.

You are correct, Bob works out of the Box, and immediately delivers multi-access services to multiple wikis, this is brilliant you achieved this; however we do need to create and import Wikis and using Bob to manage and distribute plugins and other features are compelling reasons to adopt Bob and it is with these additional features and some bugs I currently struggle.

3 - There is documentation in the control panel, but I need more specific feedback than this to determine which parts I should be focusing on

4 - I really need context to say anything useful, and maybe the content of your settings.json file (you can just copy the text from the manual setting tab).

I will work towards doing this. 

I will generate a fresh set of feature requests, comments or bug reports moving forward.

Thanks

Tony

On Monday, April 22, 2019 at 5:28:04 PM UTC+10, Jed Carty wrote:

[Jed Carty]

I will be handling any bug report that contains the appropriate information before looking into any others.

[Mark S.]

Was this supposed to fix Tony's problem #1 ? It seems to still be happening.

The documentation says that I need to configure pluginAPI in order to add new plugins. But I found just setting the pluginPath was enough to have local plugins be added to the selection. That's fine with me, but maybe not what you intended? Or maybe "pluginAPI" refers to use over the net, by remote (non-Bob) TW files?

@Tony -- is the reason that you were sticking with 1.2.2r2 because you were on the road? In which case maybe it would be better to just drop-in the plugin itself, which is less than 1 Mb.

 

Thanks!

-- Mark

[TonyM]

Thanks Mark,

1.2.2r2 was the latest Bob exe. Perhaps due to ignorance not being on the road, but I will next 48 hours. Are you saying the plugin is in advance of the exe? Would it be unwise to drop the plugin onto the running bob version? or must I go and setup a fresh bob set up without bob exe

Tony

[inmy...@gmail.com]

@TiddlyTweeter,

Thank you, the fix for this should be in the next version I upload.

[TonyM]

Mark,

As I normally use bobexe I have no idea where to find the plugin to drop into my running bobwin.exe It appears there is not running bob online from which to extract the plugin as would be the case for more other plugins.

Any Guidance would be appreciated. 

Regards

Tony

On Wednesday, April 24, 2019 at 3:42:09 AM UTC+10, Mark S. wrote:

[Mark S.]

I could extract and send it to you, if Jed doesn't mind. The only reason to do it this way is to save band-width. If you can download Bob yourself that of course is best.

-- Mark

[TonyM]

Mark,

I just though I could find the plugin tiddler somewhere. Searching the git hub I can see the tiddler, so must I load a node Bob so I can access the latest plugin?

Otherwise please send in a private message.

Regards

Tony

[inmy...@gmail.com]

As this thread is about the newest version of BobEXE, the link in the first post of this thread brings you to the download for the newest BobEXE.

Dropping another version of the plugin into a running instance of BobEXE will probably cause inconsistent or undesired behaviour.

[Mark S.]

It's possible that Tony doesn't have that first post. The link was/is:

https://www.dropbox.com/sh/c2s22zy4oaal8wz/AACQ7GGEIDYyyKxZ2Q_iWuZba?dl=0

@Tony -- I'll attempt to write offline. Sometimes my mail bounces, though.

-- Mark

[Jed Carty]

I updated the plugin version in the dropbox folder, it should be 1.2.3a2

The problem where empty sections in the settings not being removed correctly should be fixed.

The permissions errors are probably because the wiki was loaded on the server when you deleted it. I hadn't run into that while testing but it is an important case, I made it so that a wiki is unloaded before it is deleted. Let me know if you run into the permissions problem in the new version.

I haven't implemented a good solution to the alerts yet, the best I have so far is an option to disable the alerts in a wiki, or a setting to disable them globally.

There is a problem with making wikis from html files, I am working on it.