Roger This is all very helpful and I'll digest it carefully. Some of my users are children and I'd prefer they weren't digging into the file system behind the scenes too much. But they may be using their TWs during the day when I'm at work and not in a position to fix rogue locks.
So I'll weigh these options up to see if I can make my multi-user environment more reliable. Many thanks Kevin On Nov 1, 2:13 pm, roger <[EMAIL PROTECTED]> wrote: > Kevin, > We make extensive use of TW's at my office and TiddlyLock is a > necessity for us. > Occasionally a user will be locked out of a TW when they shouldn't be, > but their are only two types of events that seem to be connected to > that problem. > We have the SetUserName plugin installed that checks the username and > if it's still set as YourName, then the user is prompted to enter > their username when they try to create or edit a tiddler. However, if > you're running tiddlylock, then the username in TW.lck gets set to > YourName, so entering a username as requested by the SetUserName > prompt, the user ends up being locked out of the TW by YourName. > Fortunately, that's not a recurring type of problem. > > The more common situation we've run into is that some type of problem > occurs when saving the file. Once the TW is put into edit mode, > the .lck file is updated with the necessary information (timestamp and > username). If for some reason the file isn't saved after the edit, > then .lck never gets updated. We have autosave turned on and > ConfirmExitPlugin to assist in making sure that if a TW has been > modified, that the updated TW is saved. But if a user ignores the > prompts or a browser session crashes or something else happens that > results in the TW not being saved, then the .lck file has to be > deleted or at least the username has to be deleted from the .lck > file's content. > > As for explaining to other users how to correct the problem if a TW is > locked when it shouldn't be, you could include a tiddler that explains > the solution and add it to the menu of the TW. I suppose you could > also create a batch file that deletes the .lck when it's messed up and > access the batch file with a tiddler using LaunchApplicationPlugin. > Deleting the .lck file could just be a click away. Of course, that > could be put to use when the TW really is being edited by another > user, which would frustrate the purpose of using TiddlyLock in the > first place. > > ~Roger --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
