It is as Tobias said. I am not using the password functionality of store.php at all. I pulled the entire password management functionality out of the php script.
But, if I just ignore the password in the Tiddlywiki, it won't save the page to the Url. Instead it tries to store locally. If I set a password in Tiddlywiki, it overrides the one set by the browser in the header when it saves. Thus, I have to go into the Tiddlywiki settings and set the password instead of letting it use the one cached by the browser when I loaded the wiki. As to multi-user Tiddlywiki, you are right about the risk of overwrite. I do have store.php do a check and send a warning if there is going to be a conflict using last modification time of the wiki file and a little bit of log analysis during save time. It isn't scaleable but works in a 2 user environment. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/91cf5d3e-2d4b-4fe8-b853-091e96462463%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
