Mike, You're correct, sadly that's not the answer I'm looking. I am using SetUserNamePlugin and have it set up to automatically prompt the user for their name when the TW opens if the name is set to YourName. I had to set it up that way because I am also using the TiddlyLock plugin. With TiddlyLock, if you start to edit a TW with the user name set to YourName, then the TW becomes locked by YourName.
So if I force SetUserNamePlugin to check the value of the user name when the TW is loaded, that avoids problems if the user needs to edit the TW as SetUserName and TiddlyLock don't bump into each other when the TW is put into edit mode. Unfortunately, if I can't resolve the cookie saving issue, then every user will be getting prompted for their user name on every TW every time it's pulled up. We use hundreds of TW files in our office, so it's not an insignificant annoyance if the UserName prompt has to be dealt with every time. I still don't understand how to set the cookies exception for localhost, which I'm hopeful might be a solution, but I'm not overly optimistic that it will. ~Roger On Apr 2, 11:50 am, Mike <[email protected]> wrote: > May not be the answer you are looking for, but I had a similar > problem on a multi user TW and I > installedhttp://www.tiddlytools.com/#SetUserNamePlugin > Prompting for User name a the start of the document > > Mike > > On Apr 2, 8:05 am, Ken Girard <[email protected]> wrote: > > > In my home environment I am having no problem with cookies in a 2.5.0 > > TW on Firefox 3.1b3. > > It saves my userName and various configs, right down to having the > > options panel open. > > But, I just realized that this cookie might be also what is causing my > > cookies to persist for 2.4.1 TW files. > > Interesting as I'd never tried to think of it that way before. > > > Ken Girard > > > On Apr 1, 6:37 pm, roger <[email protected]> wrote: > > > > FND, > > > Yes, I've been to that link a few times just trying to make sure I > > > correctly understood what was being communicated. > > > > Hmmm, well I guess it doesn't matter so much why FF3 is playing nice > > > with our 2.2.5 files, it's the fact that I can't save the txtUserName > > > cookie for the ver. 2.4.1 files that I need to fix. > > > > Will the localhost URL work for the situation I described? According > > > to the wiki: > > > "using a localhost URL (e.g. file://localhost/home/user/TiddlyWiki.html > > > instead of file:///home/user/TiddlyWiki.html) - that way a cookie > > > exception can be added for localhost" > > > > But, how do I add a cookie exception for localhost? > > > > ~ Roger > > > > On Apr 1, 12:27 pm, FND <[email protected]> wrote: > > > > > > Why does the txtUserName cookie work fine in FF3 with ver 2.2.5 of > > > > > TW, but not 2.4.1? > > > > > TiddlyWiki's cookie handling should not have changed between those > > > > versions*, so this is most likely a browser issue. > > > > > Firefox 3 is not supposed to store cookies for local files: > > > > http://tiddlywiki.org/wiki/Firefox#Cookies > > > > However, I /believe/ I'd also noticed some inconsistencies in the past. > > > > However, I haven't been able to make out a reliable/reproducible > > > > pattern, so it's hard to analyze this... > > > > > -- F. > > > > > * that's just a guess, so I might be wrong --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
