hi tobias, I think the server doesn't care about the modified field. I tested with TiddlerTweaker and set a tiddler modified to 2010.09.16. It works as long as you don't reload. I think the server or tiddlySpace core plugins overwrites this field again. I should have checked this, before I posted the feature request.
I have to test it with hoster. But autosave is checked now, which is a welcome side effect :) thx. mario On Sep 17, 7:58 pm, Tobias Beer <[email protected]> wrote: > Hi again, PMario, > > I think I've got it now. After the final... > > store.saveTiddler(...); > > in setTag I added... > > if(config.options.chkAutoSave)autoSaveChanges(); > > That seems to trigger saving. > > However I just noticed that when there is an included tiddler form > some other space that goes by the same name ...then you have to make > it public for it to save?!? I find that weird. > > Cheers, Tobias. -- 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.
