Thanks for bringing this to my attention Tony! Mario - would you consider contributing that overwrite detection to core?
Do you all think that this behavior is indeed a bug? Best, Diego On Monday, December 18, 2017 at 6:01:14 PM UTC-6, TonyM wrote: > > Sorry, > > My Mistake, I could not locate the option to select this, so I saved it. > It comes with the Marios Tiddler Bundle Plugin > > see https://groups.google.com/forum/#!topic/tiddlywiki/_Uqbg08Pjow > > and has the side effect of letting you choose to overwrite or create new > with duplicate tiddler names even when using the import facility. > > Tony > > On Tuesday, December 19, 2017 at 10:13:19 AM UTC+11, Diego Mesa wrote: >> >> Sorry Tony, >> >> Maybe I'm missing something, but is this just the code for the actual >> checkbox not the mechanism? >> >> Thanks! >> Diego >> >> On Monday, December 18, 2017 at 4:55:02 PM UTC-6, TonyM wrote: >>> >>> A Dump from my own notes=, using import, perhaps this will help. >>> >>> $:/config/wikilabs/enableOverwriteCheck = no vs Yes >>> >>> <$checkbox tiddler="$:/config/wikilabs/enableOverwriteCheck" >>> field="text" checked="yes" unchecked="no" default="no"> Enable Overwrite >>> Check</$checkbox> >>> >>> By default, the import mechanism overwrites existing tiddlers. By >>> enabling this option, you can activate a mechanism, that creates a new >>> tiddler name. By default this option is off. >>> >>> Tony >>> >>> On Tuesday, December 19, 2017 at 9:40:32 AM UTC+11, Diego Mesa wrote: >>>> >>>> Hello all, >>>> >>>> I just now realized that importing does not warn about overwriting >>>> existing tiddlers with the same name! I feel this is a bug, but am not >>>> sure >>>> if this is the desired behavior. If it is, I will open an issue on >>>> GitHub asking for a warning to be shown. >>>> >>>> *Steps to reproduce:* >>>> >>>> 1. Go to https://tiddlywiki.com/ >>>> 2. Drag and drop the attached tiddler to import >>>> 3. Accept import >>>> >>>> >>>> *Desired Outcome:* >>>> >>>> - The import tiddler warns you of the incoming tiddler with the >>>> same name *and* leaves that conflicting incoming tiddler unchecked, >>>> preventing accidental data loss. A user can still manually check it, >>>> acknowledging the warning. >>>> >>>> >>>> *Actual Outcome:* >>>> >>>> - The import tiddler shows *no* indication of a collision/existing >>>> tiddler. Upon accepting the import, the contents of the HelloThere >>>> tiddler >>>> are lost without warning. >>>> >>>> >>>> I came across this while trying to import around 100 tiddlers into my >>>> TW. These tiddlers were automatically generated using a modified bibtex >>>> importer in another playground TW for some papers I am working with. I >>>> realized after the fact, that I already had an entry in my actual TW for a >>>> paper, whose content I now lost. >>>> >>>> >>>> Note: The attached tiddler is just a title of "HelloThere" and the >>>> content "modified": >>>> >>>> [ >>>> { >>>> "created": "20171218222709327", >>>> "text": "modified", >>>> "title": "HelloThere", >>>> "tags": "", >>>> "modified": "20171218222716073" >>>> } >>>> ] >>>> >>>> -- 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/cd8aaf8b-0918-4e6a-99fa-573f743e0ede%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
