I upgraded to FF3 some time ago and was of the understanding that it
doesn't save cookies for local files from session to session.  The
cookie I'm specifically interested in is txtUserName.  I have TW's
that several of the people in my office access which are based on TW
2.2.5.  Some of us are on FF3 and others on FF2, but none of us have
had any issues with txtUserName not preserving our individual user
names from session to session.

I've also been working on a TW based on 2.4.1  Every time I open the
2.4.1 TW the user name is set to YourName.  I did install the
CookieSaverPlugin and set the value of several cookies in the
CookieJar.  However, I can't really set the value of txtUserName in
the CookieJar since the TW will be accessed by multiple users, each of
whom will need to user their own user name.

Unfortunately as it stands right now, if I implement this new version
of TW in my office environment, each user will have to enter their
user name every time they start a new session with this TW.  Everyone
in the office is accustomed to working with the 2.2.5 TW's and not
having to enter their user name each time they access the file.  I'd
really like to keep it working that way as we move everyone in the
office to FF3 and ver 2.4.1 TW files.

So I guess my question are:
1) Why does the txtUserName cookie work fine in FF3 with ver 2.2.5 of
TW, but not 2.4.1?
2) And what's the best way to accomplish the same UserName experience
for multiple users of a local TW 2.4.1 file in FF3 as they've been
accustomed to so far with ver 2.2.5?

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

Reply via email to