I suppose this post is directed to Eric's attention, but I've been struggling with a cookie issue where sometimes the UserName would persist and other times it would not. What I've finally determined is that it seems to be the SetUserNamePlugin that is the source of the trouble. I'm using core 2.4.1 with FF 3.0.8. If I set the UserName using <<option txtUserName>> then the UserName I specify will persist from session to session and TW to TW. However, if I set the UserName using the <<setUserName>> option provided by SetUserNamePlugin, then the UserName does not persist. I assume that means, it doesn't get saved to a cookie.
I installed SetUserNamePlugin because I am also using TiddlyLockPlugin. I was running into problems when a TW was put into edit mode if the UserName was set to YourName. The user would change their name at the prompt, but TiddlyLock would already have the file locked by YourName. Using SetUserNamePlugin helped resolve the TiddlyLock issue, but certainly seems to be the source of this UserName cookie problem. For now I can just include <<option txtUserName>> in plain site on the TW so the user can see what their UserName cookie is set to and change it if necessary. If SetUserNamePlugin didn't cause problems though, I'd prefer to use it rather than having to always display the txtUserName prompt. ~Roger --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
