[TW5] Bob and BobEXE version 1.2.0 Wibbly Wobbly

[Jed Carty]

There are some big changes in this release!!

BIG IMPORTANT NOTE: If you are updating from a previous version you must go into the Available Wikis tab under Bob Settings in the control panel and click the button 'Auto-populate list from Wikis folder' with the checkbox checked. Otherwise all of the paths to existing wikis in your Wikis folder will be incorrect.

The biggest is that Bob can now detect and automatically list wikis that are in your Wikis folder. You can also change the name and path of wikis the folder.
It can also optionally remove any links to wikis that don't exist. The button that does this is in the Available Wikis tab under Bob Settings.

You can give wiki names with / in them and they will be placed in subfolders of your wikis folder. So giving the name people/Me would create the folder people in your wikis folder (if it doesn't exist) and make the wiki in a folder called Me.

Many of the other changes are in preparation for setting up a server that we will allow people to host wikis on. More about that later.

The plugin version of Bob is on GitHub here: https://github.com/OokTech/TW5-Bob
The newest version of BobEXE is available here: https://github.com/OokTech/TW5-BobEXE/releases

If you want to support the development OokTech has a patreon page here
https://www.patreon.com/OokTech

or if you prefer there is a link for PayPal herehttps://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZG94CTLHTKYRE

Here is the full changelog since the last announcement:

!! Version 1.2.0 Wibbly Wobbly

- Don't sync tiddlers that start with `$:/WikiSettings`
- General improvements to message handling
- You can now give a path (absolute or relative) for wikis instead of always making wikis in the `./Wikis` folder.
- Bob can now automatically detect and list any wikis in the wikis folder or subfolders
- Wikis that are listed but don't exist can also optionally be removed.
- If you are logged in you can set new wikis to be prefixed by your username to prevent naming collisions on multi-user systems.(currently only relevant with the secure server)
- You can make new wikis in subfolders by giving a name like path/to/wiki/wikiName
- Fixed a bug that would sometimes prevent changes to the tags field from being properly synced.
- Optionally set the server to automatically unload wikis that have no active connections to reduce ram usage (experimental)
- Automatically close and remove socket objects that are no logner connected
- If you have authentication only wikis you are authorised to view will be listed.

!! Version 1.1.2 Unnamed Pastry

- The control panel tab has been refactored a bit (few visible changes)
- Separate the function that lets you determine if a wiki exists or not from the load function
- This lets us list only wikis that actually exist
- This may let us automatically detect available wikis in the future
- The available wikis listing now only shows wikis you have permissions to view.
- You can now set the default folder for storing wikis
- It can be relative to the tiddlywiki folder (or the folder with the executable) or an absolute path.
- You can now automatically detect wikis that are inside your wikis folder
- This can automatically populate settings.json for you
- This can also detect wikis that are listed but don't exist and remove them from the list.

[TonyM]

Jed,

Thanks you so much for developing this fantastic tool further. I am excited about all the features you put in, I currently use Bob exe to manage a number of Wikis, but Without shared or inter-wiki features.

To be honest I still have trouble translating how to achieve things you say it can do. I would be keen if you could be a little more verbose in the documentation, for new naive users, give more examples etc... But I Know this is difficult and I have offered to do documentation for you, however I have not yet being able to understand the features I would document yet, so I am a little stuck. I Will review what Josiah/TiddlyTweeter documented, but I imagine it is changing rapidly.

I am also keen to eventually host in an Online node environment, starting with a secure personal TiddlyWiki network.

Regards

Tony

[TonyM]

Jed,

I upgraded bobEXE but "Auto-populate list from Wikis folder" does not appear, however the existing ones are all there and the links to existing wikis work.

BIG IMPORTANT NOTE: If you are updating from a previous version you must go into the Available Wikis tab under Bob Settings in the control panel and click the button 'Auto-populate list from Wikis folder' with the checkbox checked. Otherwise all of the paths to existing wikis in your Wikis folder will be incorrect.

Regards

Tony

On Wednesday, January 9, 2019 at 1:01:27 AM UTC+11, Jed Carty wrote:

[Jed Carty]

if you are using absolute paths to wikis instead of creating them through the interface in the control panel or they are not in the wikis folder it should work fine without any changes.

[Jed Carty]

Tony,

We are working on more documentation, but as it is I get very little feedback about the development and I have no idea which features people care about and which ones they have trouble using. Also if you don't see the button than something strange is going on. Are you looking at the tab in the control panel? It isn't in the list of wikis that you can have in the sidebar.

[Jed Carty]

Argh, somehow I managed to upload a version that doesn't have the updated version of Bob and I was doing testing with a version that did have it.

I will update it when I get home in a few hours. Sorry about that.

[TonyM]

I did not want To impose.

I will give more feedback, the features mean a lot to me.

I will try the rerelease.

I am also about to identify a plugin that appears to abend bob just on import.

Thanks
Tony

[Riz]

Hi Jed,

First of all, thank you. Been using your work in first release. It is really great to see that you are bringing great deal of improvements to this.

I am running Bob in termux. The new plugin version, however, is not starting. I am attaching a screenshot of the error message. Hope you will look into it.

While I have you here, another issue I had, this time with previous version, was the inability to edit JavaScript files. For eg: if you clone the "now macro", a js file and meta file is created in the folder. However, changes I make is not propagated to server. Let me know what other details I can provide about this.

Sincerely,
Riz

[Jed Carty]

Riz,

It looks like the only way to get that error in the screenshot is if the root wiki doesn't exist. This may be because of the changes to how the pathing works between the old and new version. If you have the root wiki in the Wikis folder and listed as a relative path in settings.js try removing the 'Wiki' part of the path. So if the path is './Wikis/IndexWiki' change it to './IndexWiki'

If that isn't the problem than I am not sure what the problem is. Either way I am going to give a better message for your situation.

I am not sure why you wouldn't be able to edit javascript files. I will look into it and see if I can find anything. It may be a problem with how Bob handles .meta files, I haven't been able to test that as much as I would like.

[Jed Carty]

Riz,

After looking at it a bit more I think that the only way that you would get that error is if you have autoUnloadWikis set to true. Now that I am looking closer I see that there could be times on slower hardware when the root wiki could be unloaded before you can load it. So if you have autoUnloadWikis set to true remove that setting and see if the problem persists.

[Mark S.]

I feel there must be a page I'm missing somewhere with additional documentation. Or maybe it appears when it is installed? I don't see anything about external files, for instance.

Thanks !

-- Mark

[Jed Carty]

I updated BobEXE so it should have the correct version now. Let me know if there are more problems.

Mark,

There is a lot of documentation in the Bob Settings tab, including about how to serve external files. I am sure there are a lot of holes in it but it is there. I am not sure where else to put it.

[Riz]

No. I am testing it on a fresh install of everything including tiddlywiki. The problem happens from the get go.

Slow hardware could be the culprit here. Although, as I said, previous version worked well in termux.

Let me know if any other info I can provide.

[Mark S.]

Are you running out of names for bread products, BTW?

Win 64, Firefox 64

Not much luck.

Attempted to create "test" wiki. After pressing button, Bob will erase the contents of the name field. No wiki appears in the listing.

In the help text there is a missing link "see exporting wikis"

Attempted to add existing data folder.

First, had that problem where every single keystroke lost focus and had to be re-moused.

Second, no wiki was found/launched.

I could be using the right address. It's a windows absolute address, entered as C:\Users\Mark\Google Drive\wikis\scribbles\tiddlers

Not sure how to deal with the space in the name or if it makes a difference.

So, so far, only have managed to launch the Bob dashboard.

Thanks!

-- Mark

[Mark S.]

Looking in the settings directory, settings.json only has 2 bytes: {}

So, where is it saving settings? They seem to save, though they don't do anything.

-- Mark

[Mark S.]

I take it back. When I restart Bob, the wiki settings I had previously inserted are gone.

[Mark S.]

Deleted the artifacts Bob had made, and started again. When Bob first starts, Bob has settings.json with about 92 bytes of data. After you attempt to make changes, it generates a 2 byte file.

-- Mark

[Mark S.]

If I take the 92 byte file and manually restart Bob, Bob still ignores the new settings -- they don't show up in the editor and the new wiki doesn't appear in the wiki listing.

-- Mark

[Jed Carty]

Mark,

Are you using BobEXE or the plugin? How did you install the plugin if that is what you are using? I haven't been able to replicate anything you have mentioned on linux or osx using BobEXE or Bob as a plugin. I don't have access to a windows computer to test on.

And the path isn't to the tiddlers folder, it is to the folder that has the tiddlywiki.info file. I have no idea how windows handles spaces in path names, the last time I regularly used windows it was 3.1 and you couldn't have spaces in paths.

The missing exporting wikis link leads me to believe that you somehow don't have the full plugin somehow.

[Mark S.]

I was using BobExe on windows 7, home 64.

Yes, I was using the path to the folder with tiddlywiki.info. The tiddlywiki.info path was part of a data tiddler used previously by tiddlyserver.  I also tried it with a path to the empty editions tiddlywiki.info folder of tiddlywiki from the TW github repository. I also tried just making a new Wiki.

The big problem seems to be that the settings file is written over as a 2 byte file. But even when I hand-populate it, it gets ignored.

You really haven't used windows since 3.1 ?

-- Mark

[Jed Carty]

It sounds like either the window executable didn't compile correctly or there are some very strange interactions between my code and windows paths. The path you mentioned a few post ago was to the tiddlers folder, not where the tiddlywiki.info file is which is why I mentioned it.

Does the IndexWiki work? Can you create and edit tiddlers in it and have them save correctly?

[Mark S.]

Yes, IndexWiki works.

[Jed Carty]

Ok, then it sounds like the windows build is somehow corrupted if it is missing documentation tiddlers. There may also be some problems with windows and its weird pathing. If I remember correctly I had trouble before because windows doesn't understand cwd the same way as every other system so that may be part of what is causing the trouble. Problems like this make me just want to drop windows support.

[Mark S.]

I'm rebooting my computer to see if there were any memory problems (typing from a Linux machine, while waiting for infernal Windows updates to complete).

Dropping support for windows? 80% of desktops/laptops are running windows.

[Jed Carty]

A lot of desktops use it but that doesn't get me anything. The windows exe file is also two levels of things that I don't use, windows and BobEXE, which means I put a lot of time and effort into debugging something that I can't test and that I don't use.

I probably won't actually drop support, but I can dream. Its refusal to play well with others makes my life more difficult.

[Mark S.]

Not "a lot of desktops" -- 80% of desktops. Most desktops.

Ok. Rebooted. I also turned off my add blocker and privacy badger. Was able to create an empty edition. Hurrah!

But then I tried entering a path to an existing data folder, and got the 2 byte settings file again.

The main problem appears to be that settings gets written over as a 2 byte file when using the manual settings option. Even if it doesn't like the file path I give it, that shouldn't make it write a corrupt settings file.

Remember also that the "field" field has a focus problem, making it infuriatingly difficult to write a proper name there. That suggests something is wrong with the code, since the path entry does not have the same problem.

Maybe I should try again and completely skip the manual settings tab.

-- Mark

[Mark S.]

I can create a path using a text editor. Apparently windows paths need to have the backslash escaped, like C:\\mypath\\to\\tiddlywiki.info\\dir

When I view this in the manual settings tab, the double \\ are reduced to single \. When I attempt to edit in the Manual Settings tab, everything is made into a 2 byte file.

In fact, even if I take a working set up, and simply delete the existing empty in the Manual Settings tab, the settings file is made into a 2 byte file.

So basically, the Manual Settings tab, or perhaps the "Update" function, corrupts the settings file and turns it into a 2 byte {} file whenever it is used.

So, it's not about windows pathing. It's about either the Manual Settings editor, or the "update" button.

Good luck!

-- Mark

[Mark S.]

Additional note about odd behavior. When I'm in the Settings Tab and refresh the screen, it will ask me if I want to leave the page (even though I haven't changed anything on the page). When I say "yes" and it refreshes, Bob closes itself out. Don't know if that's intended.

-- Mark

[Mark S.]

@TiddlyTweeter

You don't know off hand if Bob can serve single file TWs ? I'm assuming not.

@TiddlyTweeter and/or Jed

Can you set lazy loading in the settings?

Where do you change the virtual "file" path (like to make it "images", for instance).

Thanks!

-- Mark

On Thursday, January 10, 2019 at 10:18:29 AM UTC-8, @TiddlyTweeter wrote:

Jed & Mark

I can't add much constructive to Mark's comments ... but thought it worth emphasising ...

-- manual settings entries are losing focus on edit character by character. NB: previous versions of bob.EXE Windows did not have that issue on settings.

-- I tried updating or adding several different settings. In all cases the problem Mark outlined occurs.

Mark S. wrote:

... Apparently windows paths need to have the backslash escaped, like C:\\mypath\\to\\tiddlywiki.info\\dir

Yes. I believe that is how node is able handle path settings? This method of storage of paths was the same in previous Bob.EXE editions so I doubt its any issue in this. FWIW Tiddly Desktop also uses escapes in its path settings.

Jed Carty wrote:

... The windows exe file is also two levels of things that I don't use, windows and BobEXE, which means I put a lot of time and effort into debugging something that I can't test and that I don't use.

I probably won't actually drop support, but I can dream. Its refusal to play well with others makes my life more difficult.

Eek! I hope you will stick with Windows. Previous versions I had no problems of this type with and its worked very reliably on Windows (7 & 10) for me. 

The only issue I had in Windows was around the Windows command processor. But that is not a Bob issue. Its an O/S issue that can arise in the running of scripts initiated by Bob. Its easily solvable and I posted about what users need to know to address it.

Very best wishes

Josiah

 

[Jed Carty]

It could be every desktop using windows and it wouldn't mean that I get anything more for supporting windows than not supporting windows.

I think I found the source of the problem and I will get a fix for it eventually. And no, Bob doesn't serve single file wikis, what it does is it makes it simple to convert a single file wiki into a wiki it can serve and then to export it back to a single file wiki. At some point I hope to make this happen transparently so it would be almost the same as serving a single file wiki.

[Mark S.]

Hi Jed

It could be every desktop using windows and it wouldn't mean that I get anything more for supporting windows than not supporting windows.

If you're hoping for patronage, then your odds are 5x better if you include the windows world at little extra cost (or at least so it appears from the armchair developer).

I think I found the source of the problem and I will get a fix for it eventually. And no, Bob doesn't serve single file wikis, what it does is it makes it simple to convert a single file wiki into a wiki it can serve and then to export it back to a single file wiki. At some point I hope to make this happen transparently so it would be almost the same as serving a single file wiki.

That's an interesting way of looking at it. I'll have to try that with a couple wikis. 

Thanks!

-- Mark

[Jed Carty]

As far as patronage goes, I do support windows now and each month I get enough to cover about 15 minutes of my time at normal contracting rates. And I have spent about 40 to 50 hours trying to track down weird things from windows. So from a financial point of view I have lost many times the income I have made from this because I support windows.

Also I don't respond very well to coercion.

[Mark S.]

On Thursday, January 10, 2019 at 11:55:39 AM UTC-8, Jed Carty wrote:

Also I don't respond very well to coercion.

Are you feeling coerced? Then give it up. I'm certainly not coercing you.

Moving on to Linux.

Attempting to connect to a setup I used last time I beta-tested Bob, (October 2018), from a wiki that I regular serve up using tiddly-server, I get a page full of syncer-browser-tiddlyweb errors and Bob dies. I can't tell if it dies before or after the errors. Launching from the command line doesn't reveal any errors. I do notice that each time Bob runs the port number gets incremented. I check each time so I know the process is dead (ps -A | grep "node"), so it's not like I'm running multiple versions of node/Bob.

Thanks

Mark

[TonyM]

Jed,

I desperately want to donate to you, but I am just starting in business, and not earning enough yet.  Hang in there if possible. Since my $ are low, I plan to help you with Windows as soon as possible, but I still need to get to know Bob well enough, to be confident I can help correctly. This is taking me longer because you are not on Windows.

I expect I could provide a Windows virtual machine online to you, however I am not sure that is what you need or want. Perhaps we need to ensure you have the collaborators you need.

Regards

Tony

[Jed Carty]

Tony,

I didn't mean to be soliciting donations by my comments. I was just pointing out that trying to leverage money against me on this wouldn't be very effective. I am very grateful for the donations that I do get but they are far from enough to be the main motivation for any of this.

For the most part just having someone using or testing Bob in windows and giving me bug reports should be enough.

[TonyM]

Jed,

Fact is I am keen to support your effort, and will.

Thanks for all your contributions.

Tony

[Jed Carty]

I just put out a bug fix release, so 1.2.1 is up. The changes are just fixing bugs. Thanks to mklauber for contributing to this release. It is marked as a prerelease to see what sort of horrible bugs pop up next.

It should fix the bugs mentioned here except for the one where changing the manual settings in the wiki loses focus after every key stroke. I haven't found what is causing that, but now that there are other ways to add wikis and remove incorrect paths manually editing the settings shouldn't be as important.

[Riz]

Hi Jed,

If you have an android phone, can you test it on termux? I need to make sure that it is not an issue of my setup. I did a fresh install from scratch with the following commands

git clone --depth=1 --branch v5.1.18 https://github.com/Jermolene/TiddlyWiki5.git
git clone --depth=1 https://github.com/OokTech/TW5-Bob.git TiddlyWiki5/plugins/OokTech/Bob
mkdir TiddlyWiki5/Wikis
cp -r TiddlyWiki5/plugins/OokTech/Bob/MultiUserWiki TiddlyWiki5/Wikis/BobWiki/
cd TiddlyWiki5 node ./tiddlywiki.js Wikis/BobWiki --wsserver

I didn't change any setting. I got the same error as before.

sincerely,
Riz

[Mark S.]

Linux. Bob Timey Wimey.

When I try to run one of my existing data folders I get a series of yellow 404 messages similar to:

syncer-browser-tiddlyweb - 21:38:31 11 1 2019

XMLHttpRequest error code: 404

syncer-browser-tiddlyweb - 21:38:33 11 1 2019

Sync error while processing '$:/StoryList': XMLHttpRequest error code: 404

Sync error while processing '$:/EditionsList': XMLHttpRequest error code: 404

syncer-browser-tiddlyweb - 21:38:33 11 1 2019

Sync error while processing '$:/Bob/VisibleConfigurationTabs': XMLHttpRequest error code: 404

They reference tiddlers that are not part of the target TW project, so must be an artefact of Bob.

I've tried clearing out the wikiindex and starting over. I've renamed existing paths so none of them have "wikis" in them. I've checked the contents of the data folder directories. I can't see anything wrong.

Is there a way to run Bob at the command line with better error messages?

Thank you,

Mark

[Jed Carty]

Riz,

 I will try to install termux on my phone and see how it goes. I couldn't find any reason in the code for that error so there is probably something I am overlooking.

Mark,

Those errors are from the tiddlyweb plugin. If you have it listed in the tiddlywiki.info file and don't have the plugin as a .tid file it is blocked by Bob, but if you have it as a plugin file than it gets loaded and causes errors like what you are seeing because the server it expects isn't there.

[Jed Carty]

I have absolutely no idea where the losing focus error came from, and if it is fixed now (I don't think it was last time I tested it on my computer) I also have no idea why. It may be a mystery of the computer gnomes.

[Jed Carty]

Riz,

I finally got everything installed on the phone and I am getting the same error as you. I am not sure why it is happening but I have some ideas, I will let you know if I get a fix.

[Jed Carty]

Riz,

I think I found the source of the problem, I am testing it now. It looks like for some reason on termux the browser is trying to load the favicon before the RootWiki is loaded. I am not sure if this is a problem specific to termux or if it is because phones generally have less power than other hardware running Bob. I fixed the error but now it isn't finding the RootWiki. I think it has to do with pathing again, but I am not sure exactly where. I will continue looking.

[Riz]

Jed,

Glad you could replicate it. If it helps, this is an issue with new release. Previous release worked well in termux.

Also, since I don't have a working Bob to verify (don't have access to my desktop now, only termux), I hope you looked into the the editing JavaScript issue. I had outlined the steps to replicate the issue in my first comment

Sincerely
Riz

[Jed Carty]

I have not had a chance to look at the editing javascript issue, but I did find the source of the termux errors. I have been using absolute paths to the root wiki on all of my tests and the error only appears when using relative paths. So you may be the only person other than me who is using the plugin version of Bob because the second error isn't related to termux. But it should be fixed now if you pull the newest version. I will spend a few minutes looking at the javascript error now but I don't have a lot more time to devote to this today.

[Rizwan Ishak]

Thank you, can confirm that the bug is fixed now.

 So you may be the only person other than me who is using the plugin version of Bob because the second error isn't related to termux.

I am sure there are others. People are usually little behind in update cycles.

 I will spend a few minutes looking at the javascript error now but I don't have a lot more time to devote to this today.

No rush. Just bringing it to your attention. I know how one person cannot do all possible tests to find edge cases. That is where community can help out, aiding you to evolve it into a better product.

You should know that a lot of us appreciate the umpteen number of hours and expertise you sunk into this project for the sake of community. May be it is not vocalised every time, but it is there.

Keep up the great work. Practically all my node instances of Tiddlywiki are Bob now.

Sincerely,
Riz

[Dave]

Is there something I'm missing to get the recent fixes?  

I was under the impression that I should just go to the Tiddlywiki5 folder and enter "git pull", but when I do that it says "Already up to date."

I'm (obviously) not really knowledgable about git, so, is there some obvious thing I'm missing?  I tried sudo, and also going up a directory but neither worked.

[Jed Carty]

You have to go into the Bob plugin folder. If you followed the instructions in the readme without changing anything than from the TiddlyWiki5 folder you would type:

cd plugins/OokTech/Bob

git pull

the Bob repo is inside the TiddlyWiki5 repo, if you are not inside the Bob folder than it will try and pull TiddlyWiki, not Bob.

If you put Bob somewhere else you need to cd into that folder and git pull there.

[Dave]

Thank you - my Bob is up and running again :)

I had the same error that the fellow above using Termux had, and I'd originally done a git pull in Tiddlywiki5 folder that broke my install.  I wonder if that's why.

(don't forget you're dealing with amateurs here :D )

[Jed Carty]

The error was due to a fix for something else breaking relative paths for the root wiki, so it wasn't anything you did wrong. I just need to make a more robust test suite than 'whatever things I think of to test at the time'.

[Dave]

Ha ha, well you know what they say: "Beggers (me) can't be choosers"

I'm just thankful you've brought Bob into the TW community. I've been waiting for years to be able to have a file-per-tiddler system.

Now that I've taken the steps to figure out Bob I suppose I could have figured out tiddlyweb server or whatever the previous file per tiddler system was, but Bob seems way more user friendly for beginners than those other systems. So anyway please consider your work important and I hope your baby here leads to great things :)

Ps when I win the lottery you and Jeremy will be my first non family donations - I guess I better start buying tickets, ha ha (plus Eric and Tobibeer and Mark and...)

[TonyM]

Jed,

For the latest and prior versions of BobExe running on Windows and in FireFox when I go to close FireFox most tabs containing a BobWiki generate the following prompt regardless of if the WIki has already saved updates;

**This page is asking you to confirm that you want to leave - data you have entered may not be saved**

So there seems to be a problem informing the Browser that the page has no updates pending.

Is this a known issue and is there a way to fix it?, when one uses Bob heavily it takes sometime to close my browser and I always have to make a "tab by tab" visual check to see if there is no outstanding and unsaved changes.

Thanks for considering

Tony

---

I am running (check any that apply, put an x inside the [ ] to check a box, like this: [x]):

- [X] Windows

- [ ] OSX

- [ ] Linux

- [ ] Other

and using

- [ ] The nodejs version

- [X] The single file executable

Before posting I read [issue guidelines](./IssueGuidelines.md) and:

- [X] I am using the newest version

- [X] The answer to my question isn't listed in the documentation or this isn't

  a question

- [X] This is not a duplicate issue

- [?] I have not done anything that required me to set acceptance to

  `I Will Not Get Tech Support For This`

On Wednesday, January 9, 2019 at 1:01:27 AM UTC+11, Jed Carty wrote:

There are some big changes in this release!!

BIG IMPORTANT NOTE: If you are updating from a previous version you must go into the Available Wikis tab under Bob Settings in the control panel and click the button 'Auto-populate list from Wikis folder' with the checkbox checked. Otherwise all of the paths to existing wikis in your Wikis folder will be incorrect.

The biggest is that Bob can now detect and automatically list wikis that are in your Wikis folder. You can also change the name and path of wikis the folder.
It can also optionally remove any links to wikis that don't exist. The button that does this is in the Available Wikis tab under Bob Settings.

You can give wiki names with / in them and they will be placed in subfolders of your wikis folder. So giving the name people/Me would create the folder people in your wikis folder (if it doesn't exist) and make the wiki in a folder called Me.

Many of the other changes are in preparation for setting up a server that we will allow people to host wikis on. More about that later.

The plugin version of Bob is on GitHub here: https://github.com/OokTech/TW5-Bob
The newest version of BobEXE is available here: https://github.com/OokTech/TW5-BobEXE/releases

If you want to support the development OokTech has a patreon page here
https://www.patreon.com/OokTech

or if you prefer there is a link for PayPal herehttps://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZG94CTLHTKYRE

Here is the full changelog since the last announcement:

!! Version 1.2.0 Wibbly Wobbly

- Don't sync tiddlers that start with `$:/WikiSettings`
- General improvements to message handling
- You can now give a path (absolute or relative) for wikis instead of always making wikis in the `./Wikis` folder.
- Bob can now automatically detect and list any wikis in the wikis folder or subfolders
- Wikis that are listed but don't exist can also optionally be removed.
- If you are logged in you can set new wikis to be prefixed by your username to prevent naming collisions on multi-user systems.(currently only relevant with the secure server)
- You can make new wikis in subfolders by giving a name like path/to/wiki/wikiName
- Fixed a bug that would sometimes prevent changes to the tags field from being properly synced.
- Optionally set the server to automatically unload wikis that have no active connections to reduce ram usage (experimental)
- Automatically close and remove socket objects that are no logner connected
- If you have authentication only wikis you are authorised to view will be listed.

!! Version 1.1.2 Unnamed Pastry

- The control panel tab has been refactored a bit (few visible changes)
- Separate the function that lets you determine if a wiki exists or not from the load function
- This lets us list only wikis that actually exist
- This may let us automatically detect available wikis in the future
- The available wikis listing now only shows wikis you have permissions to view.
- You can now set the default folder for storing wikis
- It can be relative to the tiddlywiki folder (or the folder with the executable) or an absolute path.
- You can now automatically detect wikis that are inside your wikis folder
- This can automatically populate settings.json for you
- This can also detect wikis that are listed but don't exist and remove them from the list.

[Ste Wilson]

Hello!
Finally ssh'd into my pi and updated both Bob and tiddlywiki. All went mostly well.
All $:/ tiddlers seem to have vanished as had JD's mobile theme. Fortunately I'd a backup!

Only snag so far is the 'download as single file' button reports an error and doesn't download.

Will try to have an explore of new rudely and bob stuff soon.

Thanks :)

[Matthew Lauber]

Hey Jed, 

Since the update, I'm having difficulty using the <$action-websocketmessage> "internalFetch".  I was trying to populate my rootWiki with the $:/SiteTitle from the various other wikis, and had this working in 1.1.0.  Now, the call to internalFetch results in "Couldn't parse externalTiddlers input".

\define addPrefix() [addprefix[$:/state/Bob/$(WikiName)$/]]

\define getTitle() $:/state/Bob/$(WikiName)$/$:/SiteTitle

\define getSubtitle() $:/state/Bob/$(WikiName)$/$:/SiteSubtitle

Available Wikis: <$button>

  Refresh Titles

  <$list filter="[[$:/WikiSettings/split/wikis]indexes[]]" variable="WikiName">

     <$action-websocketmessage

       $type='internalFetch'

       fromWiki=<<WikiName>>

       filter='[title[$:/SiteTitle]]'

       transformFilter=<<addPrefix>>

       resolution='force'

     />

     <$action-websocketmessage

       $type='internalFetch'

       fromWiki=<<WikiName>>

       filter='[title[$:/SiteSubtitle]]'

       transformFilter=<<addPrefix>>

       resolution='force'

     />

   </$list>

</$button>

<$list filter="[[$:/WikiSettings/split/wikis]indexes[]]" variable="WikiName">

<li>

<a href=<<WikiName>> target='_blank'>

<$transclude tiddler=<<getTitle>> ><$text text=<<WikiName>> /></$transclude></a> <$transclude tiddler=<<getSubtitle>> />

</li>

</$list>

[Joshua Fontany]

Jed, this is excellent work. I just realized that the TW releases had broken my JsonMangler code in the latest version. I had been developing on tiddlyserver (& it doesn't like the latest) & needed to refactor.

Just got up and running with Bob, and the SLACK it has given me! ( ; ) ) Bravo. Bravo.

Best,
Joshua Fontany

[Joshua Fontany]

Hmmm. I have also run into the "syncer-browser-tiddlyweb" errors.

I also noted that at some point I stopped being able to save local single-file copies of the wiki by clicking normal checkmark/save button.

But if I don't have `tiddlywiki/tiddlyweb` in my tiddlywiki.info file, I can't just use node to --build an index.html...

So something here isn't working right. I just don't know if I made a mistake with setup or ???

Best,

Joshua Fontany

[Joshua Fontany]

And I found the Bob config tab & related docs. Cool, no worries on that.

It would be great to resolve the tiddlyweb plugin errors, as I would like to sync my local Bob wiki folder to github, but can't be sure others pulling it are using Bob.

Best,
Joshua Fontany

[Jed Carty]

The tiddlyweb error is probably because there is a .tid version of the tiddlyweb plugin in the tiddlers folder. It happens sometimes and I haven't gotten around to publishing the changes I made to keep that from being a problem.

The save button no longer saves a single file copy because people said it was confusing that they could save a single file copy that way that wasn't the same as the copy served by Bob. If you want a single file copy you can go to the control panel and under the Bob Settings tab there is a 'Download Single File Version' button, that downloads a single file version with the Bob plugins stripped out because they don't do anything for a singe file wiki.

If you want to customise how the download works there is documentation for it in the Bob Documentation tab, look at the ActionDownloadWiki part.

The problem about not being able to build a wiki without the tiddlyweb plugin is strange. The easiest thing to check is that there may be a comma error in the tiddlywiki.info file, next make sure that in the tiddlywiki.info file under the build key 'index' is listed. Past that I don't know, I am not very familiar with that part of the build process.