[TW5] Bob and BobEXE version 1.2.2 Friend Potatoes

[Jed Carty]

There is only one big change in this release which is that now wikis can have nested paths, so now you can have a wiki at localhost:8080/students and a wiki at localhost:8080/students/alice

There are also some bug fixes, many of them shouldn't be too noticeable because they deal with having the browser resyncing with the server after being disconnected.

In BobEXE there are also default paths for plugins, themes and editions. When you start BobEXE it now makes the folders Plugins, Themes and Editions, if you copy plugins, editions or themes into them than they will be available to your Bob wikis. And as I wrote that I realised that while you can change plugins from within the wiki I haven't made an interface to add or remove themes. That will be coming soon. But the plugins will be available in the in-wiki interface and any editions will be listed in the editions list for making new wikis.

With all the changes I expect there to be the usual string of bugs that appear as soon as I post this, so let me know if you run into any problems.

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 here https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZG94CTLHTKYRE

Here is the changelog for this release:

!! Version 1.2.2 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)

!! Version 1.2.1 Timey Wimey

I didn't track things here... Something happened I am sure.

[Birthe C]

Hi Jed,

BobLinux32, I created a new wiki from empty, it was created in the Wikis folder but Auto-populate list from Wikis folder does not show any wiki. Then I wanted to create from html. Selected the file and gave a new name. The same happened as with the last Bob release. This time just not in the Wikis folder. It totally went berserk creating NewWiki, NewWiki1 and so on an on. I could not really do anything on my computer, no way to stop it. But I could shut down computer.

In the title above you called it Friend potatoes, but I did realize when downloading it was really Fried Potatoes ;-)

Birthe

[TonyM]

On updating to latest bobwin.exe on Windows 10 my wiki list looks like this and does not link to the wikis

I tried to auto populate and remove missing wikis with no improvement.

Regards

Tony

• 5.1.18-PreRelease/__path
• Core/__path
• Desktop/__path
• MyDirectory/__path
• PSaTSolutionsSuite/__path
• PSaTSuite/__path
• PSaTTWFactory/__path
• PSaTTax/__path
• PSaTWork/__path
• PluginRepository/__path
• PortFolio-Veritasium/__path
• Registry/__path
• TW5Reference/__path
• TechReferences/__path
• Test/__path
• TiddlyWikiPortfolio/__path
• xlsxTools/__path

[Jed Carty]

Of course no bug free software survives the first contact with people.

Birthe,

I may have fixed the naming problem you ran into. I can't be sure because I haven't been able to replicate it, I am not sure if that is because I am doing something differently than you are or if the 32bit version is somehow different. I am uploading a version with a naming bug I found patched which could cause an infinite loop when generating names which could cause what you are describing. I am uploading a patched version now that will hopefully work.

I may have to name the next version Potato Friends in honour of my not being able to spell.

Tony,

That is an error that I had before and made a fix for, hopefully I just didn't upload the correct windows executable to GitHub. I am uploading versions with a bug in the code that ensures that each wiki has a different name, please try that and see if it still appends __path to the end of the names. Also if you have a moment to try, try going opening up the other wikis by entering the urls, they should be the same as what is listed but without '__path' at the end. If that works it is just a display problem and not some strange difference between operating systems again.

[Jed Carty]

Make sure you back up your data before testing these things. Always put the new version into its own folder and try it out there first.

[Birthe C]

Hi Jed,

Boblinux32: Creating a new wiki from html, this time around "only" created NewWiki and 3 numbered ones also. But it did not go on an on and on. I do enter a name for the new wiki but that has not worked in any of the releases for me. Available Wikis list show all 4 of them.

Creating from Edition, Empty does create a new wiki in the Wikis folder and with the name i wanted. Nothing is shown in the Available Wikis list.

It feels quicker and my computer is not heating this time.

Thank you for all your work, Jed,

Birthe

[Jed Carty]

I am glad that it feels quicker, at least the memory parts that I added may be working. I have run into a lot of bugs that I didn't notice yesterday with creating wikis from html files and it is very unstable right now. I am working on it. Do the wikis show up if you update the list manually using the button in the control panel? If so than it is because creating the wiki takes longer than the timer I am using to run the update function for the list. I need to find a better way to set that up.

[Birthe C]

Jed, The new wikis from html do show up after updating the list in the control panel. And I just deleted the superfluos NewWiki 1 2 and 3 and renamed one of them the name I wanted. That do show up in the list now. I am very happy as it is an old wiki with lots of beautytricks ;-)...enormous and now it runs beautifully.

Creating from edition, Empty gets the right name and is placed in the Wikis folder under Bob, but it does not show up in the wikis list. Maybe the settings?

Jed, you are creating complicated software and then it is run by all sorts of users on all sorts of systems. But we love it.

Birthe

[Jed Carty]

I just put out 1.2.2r2 with some other simple fixes.

The additional changes are:

- (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.

This has fixed most of the problems with converting html wikis to Bob wikis, but still be careful with testing. It doesn't always update the list of available wikis automatically, but clicking the update list button should take care of that. I am still looking at how to reliably update the list automatically on slower hardware. Also I have only been able to test on 64 bit linux and osx, so I don't know if windows is still listing the wrong urls.

[Birthe C]

Hi Jed,

My wikis found automatically. Creating new from Edition, Empty created the right name, but two of them.

Creating from html, stil got NewWiki - 1, 2 and 3. But they are found too. I do have slow hardware, it just doesn't feel that way using Tiddlywiki and now also Bob.

Birthe

[Jed Carty]

Berthe,

Are you using 1.2.2r3? I just uploaded it a few minutes ago, it has what I hope is a fix for the multiple wiki creation problem, but if you are already using it than I guess it didn't fix it.

[Birthe C]

Hi Jed,

No that is not the one I am running right now. I'll go get it now and test it.

Birthe

[Birthe C]

Jed,

Created from Empty, right name and no repeats, opdated Available list. Creating from html, created one folder named NewWiki.

You nailed it! No multiple wiki creation.

Now how do we use the Themes folder?

Birthe

[Jed Carty]

One bug I have seen is sometimes when you convert an html wiki into a Bob wiki it ignores the name you give it and it defaults to NewWiki (or NewWiki5 or whatever the next number would be, it doesn't overwrite anything) instead of the name you want it to use. I haven't found a consistent cause for this but larger html files seem to be more likely to get the wrong name from my very tiny number of tests. But renaming the folder on the file system will rename the wiki as a work-around for now.

Berthe,

For now to use the themes folder you have to do things manually, the benefit of the folder right now is that you don't have to set environment variables to set the location of themes. Copy the theme into the Themes folder the same way as the plugins folder. Themes go inside an author folder the same as the default themes, like tiddlywiki/snowwhite. When you put a theme in the Themes folder than you can add it to the tiddlywiki.info file for a wiki and it should work. In the future I will add a way to manage themes the same way as plugins and hopefully make something to help creating new themes.

[Jed Carty]

There is now a manage themes interface like the manage plugins interface. Eventually I need to add a way to get themes and plugins off of GitHub. But that is a future jed problem.

[Jed Carty]

BIG NOTE OF DOOM: THIS IS VERY EXPERIMENTAL
I haven't run into bugs, but as this thread demonstrates that doesn't mean that there aren't a lot of them. Back everything up before trying out the new features.


That said, because I can't let things go, now you can get plugins directly from GitHub repos when using Bob. The same thing can be extended to Themes and Editions without too much trouble but I haven't done that yet. Languages too but I don't think that would be as useful, I don't think anyone is doing a translation that isn't available in the main plugin library.

To use this you find the url of a GitHub repo for a tiddlywiki plugin (like https://github.com/OokTech/RandomValue ), open up the control panel -> bob settings -> fetch plugins and put the url into the text box in that tab and click Save Plugin to Server, after you do that you can go to the Manage Plugins tab and click Update Plugin List and the new plugin should be included in the list and ready to be used in your wikis.

The updated bit of the changelog is here:

- 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.

[Jed Carty]

I just made another update to Bob. It now supports unicode wiki names and names with spaces. This includes emoji wiki names and many languages that don't use the latin alphabet.

So now Bob is on version 1.2.2r6 and 'Things are done ✅' and 꿀벌 are both usable wiki names. 

[TonyM]

Jed,

I am back at my office and installed 1.2.2r6 (latest as at writing). 

As suggested by you I can access the correct address without __path but the wiki listing persists in adding __path. Auto Populate and Remove links to missing wikis is not regenerating this list wityhout __path

In the manual settings I see

"wikis": {
   "5.1.18-PreRelease": {
         "__path": "5.1.18-PreRelease"
   }, ....

Should I just modify these entries? if so how please ?

On a related note when I tried to zip all my wikis as a backup I could not do so because a number of wikis have a tiddler called ⚒.tid which seems invalid in the Windows file system and I can't search for this in TW or Windows. Is it safe for me to rename the ⚒.tid files to fix this?

I can find these tiddlers ⚒.tid in a given wiki with

<$list filter="[search[⚒]]">

</$list>

Regards

Tony

[Jed Carty]

Tony,

That is how the settings.json is supposed to look. That is what the third line in the changelog in the original post is talking about. It is required to allow wikis to be hosted on paths that contain other wikis, otherwise I have no way to list in the settings that you can have a wiki called foo and a wiki called foo/bar.

And I am sorry, but I don't know how to interpret 'Auto Populate and Remove links to missing wikis is not regenerating this list without __path'.

Windows is the bane of my existence, at least in the context of developing Bob. If windows doesn't support unicode filenames than I do not think that I can do much about it. Although in this case it may be a limitation of the zip implementation if the wiki works other than not being able to be put into a zip file.

There shouldn't be any problem renaming tid files regardless of what is in their titles. But if you do this with Bob running it won't work and the tiddler files will have their names changed back to match the tiddler title. If you change the title than the filename will change so that is an option, or you could change the filenames manually before ziping it, but this seems like a time consuming solution.

If you change a the name of a .tid file with running than Bob will change it back to match the tiddler title, respecting the modifications from the FileSystemPaths filters you may have. So if unicode titles are giving you a problem on your system you have to change the titles to have it may any effect. I can see about adding a no unicode filename option for systems that don't support it. This may cause some confusion because then you would have filenames that look like %23%45%24.tid or something like that, but it may remove the filename problem.

[Birthe C]

Hi Jed,

This is working as super duper Friendly Bob for me.

Creating wiki from html is still creating 2 or 3 NewWiki, as we have discussed before. Renaming one of them and deleting the rest is no problem. It is listed correctly in Available Wikis.

At first it worried me, that all the first created NewWikies were still in the settings file. I thought that file would grow enormously if it did that for every wiki created from html. But I am stupid, they are in the settings, but have of course the same names, NewWiki, so it does not grow. And it does not matter as they are not shown in the Available Wikis.

I am very happy.

Birthe

[TonyM]

Jed,

I am fine with the settings looking however you decide. My problem at present is my available wikis list looks like this and the links do not work;

For example Clicking opens a URL like this http://127.0.0.1:8084/5.1.18-PreRelease/__path which fails, http://127.0.0.1:8084/5.1.18-PreRelease works.

I want to do nothing except restore working links. I expect its an artifact of an intermediate version of bob, and possibly a one off, I just need advice on how to reset these correctly.

Thanks in advance

Regards

Tony

[TonyM]

Jed,

I have only raised the  ⚒.tid issue to simply put it on your radar and if you had any suggestions. I think this may have being the cause of me not being able to "import" other wikis into bob.

In my sentence 'Auto Populate and Remove links to missing wikis is not regenerating this list without __path' I was just telling you I used Bobs facility to regenerate the list of wikis from the folders.

Regards

Tony

On Tuesday, April 2, 2019 at 7:17:27 PM UTC+11, Jed Carty wrote:

[Birthe C]

Hi Tony,

Did you look in your settings.json, 

"WikisPathBase":

After runnning Bob the first time, it has my path correct and my wikis are found, links working.

I have to set Bob to not open in browser automatically for it to work on my computer before running Bob, but that is the only reason for me to look in the settings.json. It is very automatic now.

Birthe

[TonyM]

Birthe,

The setting you mention reads

 "wikiPathBase": ".", 

  With 

"wikisPath":"./Wikis",

With each wiki defined link this

"wikis": { 
   "5.1.18-PreRelease": {
         "__path": "5.1.18-PreRelease"
   }, ....

I tried making  "wikiPathBase": ".",  like "wikisPath":"./Wikis", but no change is observed.

Thanks for some help

Tony

[Birthe C]

Tony,

In my settings,

  "wikisPath": "./Wikis",

  "wikiPathBase": "/home/lenovo/Dokumenter/TWfolders",

Then it finds what is under that path. 

Birthe

[Birthe C]

Mine too, Tony.

With each wiki defined link this

"wikis": { 
   "5.1.18-PreRelease": {
         "__path": "5.1.18-PreRelease"
   }, ....

the "__path" is that not the short way of repeating the path in  "wikiPathBase"

Birthe 

[TonyM]

Bithe,

Do you mean "the "__path" is now the short way repeating the path in  "wikiPathBase" ?

Can I assume your Bob.exe is located in the folder "/home/lenovo/Dokumenter/TWfolders"

I placed "C:\Data\TW5\Instances\Bob" in the wikiPathBase with no change.

Sad

Tony

[Birthe C]

Tony,

You need the path to were your wiki folders are. My wikis are in "/home/lenovo/Dokumenter/TWfolders"

wikiPathBase, the base path for wiki......at least I think.

Hope you find a solution, Tony

Birthe

[TonyM]

Jed et al..

My master wiki has all my wikis listed as "http://127.0.0.1:8084/Registry/__path" and opens that path http://127.0.0.1:8084/Registry/__path

Removing "/__path" from the address in the browser opens the intended wiki.

All wikis but the master wiki have the correct available wikis list.

eg Registry gives http://127.0.0.1:8084/Registry

Regards

Tony

[Jed Carty]

Tony,


Try deleting the tiddler '$:/plugins/OokTech/Bob/Wiki Listing', it may be a template problem. Because that tiddler has a tag added to it to make it appear in the sidebar it is no longer a shadow tiddler and isn't updated when Bob is updated. I am looking into how to fix this.

[Jed Carty]

The __path entries are the path for a wiki that is at that level, nothing more. The reason is that if you have an entry like "foo": "/path/to/foo" in the settings than you can't list any wikis under foo, so now it is 

"foo":{

   __path:"path/to/foo",

   bar: {

    __path:"path/to/bar"

   }

}

so you would have a wiki on localhost:8080/foo and a wiki on localhost:8080/foo/bar. To make a wiki like this you just put the name in as foo/bar and it does the nesting and sets up the settings file automatically.

The wikiPathBase setting lets you set the path to where your Wikis folder is. In the case of BobEXE it defaults to the folder where the executable is, for the plugin version it defaults to wherever the command is run. You don't have to touch this if you are using BobEXE with wikis you create in the in-wiki interface. If you use absolute paths than this has no effect.

[TonyM]

Jed,

I deleted the '$:/plugins/OokTech/Bob/Wiki Listing" which was an overridden system tiddler and the fault was corrected. Thanks for your help

Nesting wikis will be helpful, especially once I learn how to manage a single plugin store etc...

Thanks for Bob.

Tony

[Paul Richards]

Hello Jed,

I setup a node.js version of TW on a Raspberry Pi last year to run a family GTD system. Unfortunately, it didn't have a great reception, being deemed too complicated. I also had hosting issues.

I've decided to revisit the project, did some reading to refresh my memory and saw Bob. I'd like to know a bit more about how it differs from a straight node.js implementation (which I had configuration issues with) and whether Bob will suit my needs. Are there any resources I can look to to get a better grasp of what Bob does.

Any help gratefully received. (I regularly contribute to open source projects and will do so gladly if Bob is something I can use). One of the problems of the TW universe is that there are so many variations, so many use cases, so much information that it is quite difficult even knowing where to start. BTW I am computer literate, being an ex analyst programmer.

Regards Paul.

[Jed Carty]

Paul,

Bob is a plugin that replaces the server component of the normal node tiddlywiki. The big differentiating features are that it has close to real-time updates to sync tiddlers between any connected browsers and the harddrive, multi-user features so multiple people can use and edit the same wiki at the same time, and features to create and manage wikis within the wiki itself.

Edits made to tiddlers outside a wiki will appear in all of the browsers viewing that wiki almost immediately. The syncing also goes the same way, so if you have two browsers that are viewing the same wiki if you edit one of them the edits show up in the other one. This allows multiple people to use the same wiki at the same time without conflicting edits or losing information. Unfortunately this isn't the same sort of real-time collaboration like on google docs where you see someone else typing, instead when someone starts to edit a tiddler it locks that tiddler in every other connected browser and shows the changes after the editing is finished.

The wiki management features include the ability to share a plugin library between all wikis served by Bob, creating new wikis from within Bob, converting single file wikis into node wikis, exporting node wikis as single file wikis with the unneeded plugins stripped out, and just about every configuration setting for the server can be set and modified from within the wiki itself. You can also fetch plugins directly from GitHub instead of having to drag and drop them into wikis.

Within the next week or two I will add the ability to rename/move, delete, and duplicate wikis as well. And I am in the process of adding syncing between servers so that you could have a version on your laptop and on the pi at home and the two versions would sync when you are on the same network.

I have it running on a raspberry pi 3 on my home network and it hasn't given me any trouble. I added a line to rc.local to start up the server process when the pi boots.

[Stefan Pfister]

Jed, can you post your raspi configuration of tw bob? I would like to use this too on my raspi nas. Thanks, Stefan

--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/54ebf41e-317b-4e97-8495-02a8753aacd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Paul Richards]

Hi Jed, sorry for not responding sooner...work got in the way I'm afraid. Thanks for the comprehensive post.

Bob sounds very promising...a *lot* of work for you. One question..do I need to make any changes to my node.js setup on the pi to allow Bob to work? Or do I need to make a clean install?

Cheers Paul.

[Jed Carty]

Bob is a plugin, so nothing should need to be changed as far as node is concerned. To set bob up you clone the repo into your plugins folder then the command to start is

node tidddlywiki.js /path/to/wiki --wsserver

there are no other command line arguments because I am very bad at command line arguments.

it will by default serve on 8080, you can change this from inside the wiki or edit the settings.json that will be created in a settings folder. You can edit that manually or from inside the wiki to change settings.

[Mark S.]

When I try BobExe on windows, it doesn't populate the side list.

I set "wikisPath": to "D:\data\Wikis" and tell the configuration to auto-update. I see that it is able to find the wikis and write them in the configuration file. But the wikis don't appear in the side list.

I restart Bob to see if that is the problem.

I get the error:

new connection
Error getting wiki paths { Error: ENOENT: no such file or directory, scandir 'C:
\Apps\Bob-1-2-2-r6\Wikis'
    at Object.fs.readdirSync (fs.js:895:3)
    at Object.fs.readdirSync (pkg/prelude/bootstrap.js:780:35)
    at getRealPaths ($:/plugins/OokTech/Bob/NodeMessageHandlers.js:1644:35)
    at Object.$tw.nodeMessageHandlers.findAvailableWikis ($:/plugins/OokTech/Bob
/NodeMessageHandlers.js:1695:25)
    at WebSocket.$tw.Bob.handleMessage ($:/plugins/OokTech/Bob/NodeWebSocketsSet
up.js:151:52)
    at WebSocket.emit (events.js:182:13)
    at Receiver.receiverOnMessage ($:/plugins/OokTech/Bob/External/WS/lib/websoc
ket.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)
  errno: -4058,
  syscall: 'scandir',
  code: 'ENOENT',
  path: 'C:\\Apps\\Bob-1-2-2-r6\\Wikis' }
Wrote settings file

It seems to want to still use C:\\Apps\\Bob-1-2-2-r6\\Wikis, and not the WikisPath. Or do I need to change the path in two places?

Thanks!

-- Mark

[Jed Carty]

It looks like there is a bug in the function to find the available wikis. Try setting wikiPathBase to 'D:\Data', that may work until I get around to releasing the next BobEXE release.

[Mark S.]

Do I need to move IndexWiki too? Where is the real settings.json file kept?

I tried it with the two paths both changed as suggested. Restart. Tell it to auto-populate. Looks promising. I can see it is identifying the Wikis. But they don't appear in the side list. Looking in the file structure, I see IndexWiki/settings/settings.json has 0 bytes. Where is it really writing the settings?

I restart Bob, and get this message at the top:

NodeSettings - Malformed settings. Using empty de
NodeSettings - Check settings. Maybe comma error?

All defaults are reset.

It appears to me that after auto-populating, Bob creates a zero-byte settings.json file. This causes it to reset to default on the next boot.

Maybe if I just wrote the file by hand ... ??

Thanks!

-- Mark

[Mark S.]

Setting up the Wikis by hand seems to work. So it appears that the auto-populate generates a zero-byte file. Maybe those windows \ slash symbols mess with parsing?

With wikis working, I notice this error:

Bob error: includeWikis is not supported yet!

But don't know what that refers to.

Thanks!

-- Mark

[Mark S.]

Can file images be served from only one place, or from multiple wikis? I was pretty sure you were working on the latter option, but I don't see it mentioned in the documentation or configuration file.

Thanks!

-- Mark

[Jed Carty]

It is documented here: https://github.com/OokTech/TW5-Bob/blob/master/Documentation/Serving%20Files.tid

[Mark S.]

This is just my opinion, but it appears that the default response to errors in the settings.json file is to write over the settings.json file, without making a backup and without asking the user. This may actually be deleting a lot of time-consuming setup info. It would be better, I think, if Bob gave the user a warning and then closed without starting. This gives the user a chance to fix whatever is wrong -- which may be only a single misplaced comma!

Thanks!

-- Mark

[Jed Carty]

It is set this way so that when I break the settings it still starts. The in wiki interface protects against things like misplaced commas.

Unfortunately adding a setting to change the behaviour would be in the settings.json file which kind of defeats the purpose.

[Mark S.]

It is set this way so that when I break the settings it still starts. The in wiki interface protects against things like misplaced commas.

But what about when the auto-populate generates a zero-byte file? So, the wiki interface may not be bullet proof.

Thanks!

-- Mark

[Mark S.]

I think it's having trouble with images I loaded into a Wiki. For one of my wikis, I'm getting:

Bob error: includeWikis is not supported yet!

{ Error: EPERM: operation not permitted, read
    at Object.fs.readSync (fs.js:634:3)
    at Object.fs.readSync (pkg/prelude/bootstrap.js:550:32)
    at tryReadSync (fs.js:474:20)
    at Object.fs.readFileSync (fs.js:507:19)
    at Object.fs.readFileSync (pkg/prelude/bootstrap.js:679:36)
    at Object.$tw.loadMetadataForFile (C:\snapshot\BobEXE\TiddlyWiki5\boot\boot.
js:1523:35)
    at Object.$tw.loadTiddlersFromFile (C:\snapshot\BobEXE\TiddlyWiki5\boot\boot
.js:1511:18)
    at Object.$tw.loadTiddlersFromPath (C:\snapshot\BobEXE\TiddlyWiki5\boot\boot
.js:1558:22)
    at C:\snapshot\BobEXE\TiddlyWiki5\boot\boot.js:1553:40
    at Object.$tw.utils.each (C:\snapshot\BobEXE\TiddlyWiki5\boot\boot.js:69:12)
 errno: -4048, syscall: 'read', code: 'EPERM' }

I don't understand C:\snapshot\BobEXE... at all, since that is not where Bob is installed. The $tw.loadMetadataForFile is what makes me think it might be related to images.

Thanks!

-- Mark

Edit: Deleting the meta file and zero-byte png file for the image fixed the problem.

[Jed Carty]

If you are looking for something bullet proof than you should probably look somewhere other than some software that I make for myself in my free time.

If you are looking for software that is set up for your preferences with conflict with mine you can get information about pricing and availability from info @ooktech.com

The snapshot stuff is part of the magic that lets everything be packed into the executable file. That error is saying that the wiki is having trouble loading a tiddler that has meta data, probably, so a corrupted or non-existent png file makes sense as the reason.

[Mark S.]

FYI

When I use the Bob interface to tell Bob to make an empty edition, it doesn't use filePathRoot, wikiPathBase, or wikisPath as the copy target directory. Instead it puts it in "Wikis" below the executable.

HTH

-- Mark

[Jed Carty]

To make any reasonable fix for that I would need to see your settings.json file.

[Mark S.]

Here it is:

{
  "wikis": {
    "recipes": {
      "__path": "recipes"
    },
    "scribbles": {
      "__path": "scribbles"
    },
    "TWAQ": {
      "__path": "TWAQ"
    },
    "Groceries": "groceries",
    "scheduler": "scheduler",
    "test": "test",
    "Bible2": {
      "__path": "Bible2"
    },
    "Bible21": {
      "__path": "Bible21"
    }
  },
  "filePathRoot": "D:\\data\\Wikis",
  "fileURLPrefix": "files",
  "pluginsPath": "C:\\Apps\\Bob-1-2-2-r6\\Plugins",
  "includePluginList": {
    "0": "OokTech/TW5-ServerImages"
  },
  "ws-server": {
    "port": "8080"
  },
  "API": {},
  "serverInfo": {
    "ipAddress": "192.168.1.117",
    "port": "8080",
    "host": "127.0.0.1"
  },
  "wikisPath": "D:\\data\\Wikis",
  "wikiPathBase": "D:\\data",
  "excludePluginList": {}
}

-- Mark

[Mark S.]

Also, when it created the empty wikis, the plugin part of the tiddlywiki.info file was empty. I don't know if this was on purpose, but it makes the datafolder incompatible with other node.js products.

That is, these plugins were missing:

        "tiddlywiki/tiddlyweb",
        "tiddlywiki/filesystem"

Thanks!

-- Mark

[Jed Carty]

That is desired behaviour, the empty edition is empty, it doesn't have any plugins. If you want those plugins then you need to use the server edition or add them in.

I don't see any problem with the settings, I will have to poke that later.

[Jed Carty]

I keep forgetting that I haven't pushed version 1.2.3 yet. It gets confusing trying to track down bugs that are not there anymore.

[Mark S.]

I can relate. "Branches in git are cheap" we are admonished. Yes, but branches in my head are not. ;-)

-- Mark

[@TiddlyTweeter]

Ciao Jed,

erm ... which version do you need testing? :-)

I'm in process of updating BobEXE win 64 currently.

Best wishes

Josiah

[Jed Carty]

Oh, yeah I forgot about that. I will build something and put it up on dropbox or something sometime tonight so people can test the potentially unstable version.