Bob autosave question

[Dave]

Hi, I've really been enjoying Bob and can't imagine my computer life without it :)

That said, I've been trying to figure out a nagging problem and I think it has to do with autosave somehow

Problem:  I have lists of todos, and ways to change a tiddler that marks it as "done" and is removed from the list.  Sometimes though the items come back from the dead and reappear on the list, usually in the 10-15 seconds range, but sometimes minutes later.

I thought I had autosave on and when a change is made it should be permanent, but I've been able to prevent the file changes from reverting by clicking on the save button after each change.

I'm a bit confused about autosave as two different tiddlers seem to have opposing values:

On the one hand there's this:

$:/config/AutoSave

yes

but on the other hand there's this:

$:/config/DownloadSaver/AutoSave

no

Any suggestions?

- Dave

[Jed Carty]

The save button doesn't do anything. The saving also ignores the $:/config/AutoSave and $:/config/DownloadSaver/AutoSave. Things save immediately as long as it is connected to the server.

Are you using the newest version? If you are using tags to set the state of the item on the list there was a bug that would sometimes fail to save the changes when the only change to a tiddler is adding or removing the only tag.

I don't remember which version that got fixed in, but it is probably the cause of your problem. If you are using the newest version than there may be some part of it I missed.

[Dave]

On one computer I'm at 1.2.3, and on another 1.2.2 (I think - that's the home computer) and the files of the tiddler folder are sync'd between them.  Would being at a different version affect anything?

And yes, the changes are via this:

<$button message="tm-add-tag" param="done" tooltip="Add done tag" class="tc-btn-invisible">

    complete

      </$button>

[Dave]

Ok, I have both Bob servers at the same version number and that seems to have solved it.

Thank you, I'll update here if it crops up again

[Jed Carty]

Syncing the folder would cause this. Having multiple things changing the files means that when Bob makes a change the syncing mechanism and Bob fight over how the files should be changed, particularly if both computers have bob open at the same time.

[Dave]

Thanks for pointing that out. I never thought of killing node when I'm done at that computer...

I suppose the best solution would be to figure out how to install the secure server on my raspberry pi and just access that single point