On Sep 11, 7:14 pm, Eric Shulman <[email protected]> wrote: > > Okay, that will take care of the user name, but what about the other > > settings (AutoSave, No backups, etc)? > > Is there a general solution to the problems with Chrome? > > http://www.tiddlytools.com/#CookieSaverPlugin > > CookieSaverPlugin automatically generates the needed javascript > assignment statements to set TW internal config.options[...] values > corresponding to checkbox and text <<option>> settings that are > usually stored as cookies. > > It saves these statements within the document itself in a tiddler > called [[CookieJar]], which is tagged with 'systemConfig' so that, > when the document is opened, after reading cookie-based values (if > any), the [[CookieJar]] statements will be invoked, and the desired > option values are set, thus bypassing the browser's (broken) cookie > storage mechanism. > > enjoy, > -e
For some reason, this isn't working in Chrome. I'm still trying to figure it out, but settings are not being remembered, even thought the CookieJar javascript is being generated and looks just fine to me. Is there some other plugin that CookieSaver requires that wasn't mentioned? One thing I have noticed is that CookieJar seems to be remembering user-specific settings based on user name, which is one of the pieces that is not being remembered for me. I can create my own systemConfig to set the user name, but since there's no guarantee of what order it will execute the systemConfigs (that I know of anyway), I can't be sure that my name will be restored before CookieJar executes. Any ideas? Mel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
