On Thursday, December 24, 2020 at 3:14:52 PM UTC-8 wrote:
> > As am I. I suggest re-reading my previous message with this in mind, as > well as last looking at the links provided here and in the GitHub issue. An > input field being filled in does not necessarily mean the underlying > tiddler exists and has a value. > But ... it was working with 5.1.21. The field must have been filled in or it wouldn't have worked. So how did it become unfilled? I understand that just because a value is displayed doesn't mean there is an underlying tiddler. But when and why did it disappear? It was there previously, or it would not have been able to save. > I would wager you never entered a value for the branch, but rather used the displayed default which is pre-filled as "master". Why would I need to enter a branch value, when it already had one in it's prior use on github? It not only APPEARED to have the field filled in, it must have actually had the tiddler filled in or it would never have saved. Or does the upgrade process strip out existing configuration? In other words, why doesn't the underlying tiddler exist, or why wasn't it used? I did not download "empty" and then try to save it. I was using an existing TW on github which should already have had all fields filled in. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0cd2180d-2ee7-4050-b06b-503e00a4e79an%40googlegroups.com.
