Hi All,

I've been chasing a strange problem or problems since upgrading to the 
latest TiddlyDesktop (14) from the previous release. I only use TiddlyWiki 
in TiddlyDesktop and I don't use the single html file version. All my wikis 
use folders and I only use macOS.

Since I upgraded I've had occasional problems with hanging while TiddlyWiki 
is trying to save (cloud icon turns red and stays red). Quitting allows me 
to restart and work but, of course, unsaved changes are lost. I've had 
trouble pinning down the cause enough to even ask a question but now I 
think I might be on to something. I discovered there are a few tiddlers in 
my wikis that have type "application/x-tiddler." I don't even see that type 
documented in the ContentType tiddler on tiddlywiki.com, though it looks 
similar to the type for classic tiddlers. These display fine but opening 
one to edit it immediately causes the hang. I "fixed" these by opening the 
problem tiddlers in a text editor and pasting the text and fields into new 
tiddlers.

I thought that I had fixed my problem but I've discovered the following. I 
can create new tiddlers with the + button. These have no type. There is no 
type displayed while editing and no type is present when I open the tiddler 
in a text editor. For example

created: 20200624180914393
modified: 20200624180941199
tags: 
title: A New Tiddler

testing


If I then drag that .tid file into another wiki and import, it has the type 
"application/x-tiddler" in a .tid.meta file. For example-

created: 20200624180914393
modified: 20200624180941199
tags: 
title: A New Tiddler
type: application/x-tiddler


The .tid file that goes with the .tid.meta file contains the tiddlers text



If I attempt to edit it in TiddlyDesktop, the sync icon turns red and stays 
that way. 

I thought I must be doing something strange. I have wikis with thousands of 
tiddlers in them and some homemade plugins that mean I have plenty of 
opportunity to mess something up but I have now tried this with two totally 
fresh wiki folders that had nothing in them but a tiddler folder and a 
tiddlywiki.info file. I've tried with both the info file that I have been 
using for years (and have no idea where I got it, but it has been fine) and 
also with the example info file for IIS on tiddlywikis.com. The behavior 
was the same both times. I can't think what else I can do to try to 
eliminate more possibilities user error from my testing.

My standard wiki setup is full of buttons that create new tiddlers. While I 
could try to find them all and make sure that they explicitly set the type 
to "text/vnd.tiddlywiki," at this point I'm not sure that would fix things, 
and this behavior seems wrong in any case.

Does anyone have any suggestions?





P.S. Please don't focus on these but possible clues I have are that the 
large wiki that I was working with when I discovered the tiddlers with type 
application/x-tiddler has become so slow that it is unusable- I can't type 
more than a few characters into it before I have to wait. As far as I can 
tell, I can copy everything to a new wiki folder and it works fine, so 
maybe something in the TiddlyDesktop backstage that refers to that wiki has 
become corrupted along the way. The other odd thing I've seen is that on 
occasion i've had things hang while commenting out a line in a tiddler but 
only if I start with the end of the line. This might only be happening when 
there was some other problem, since it never seemed to be consistent. For 
example, I might get a hang at a stage when the line I was working on 
looked like this-

Line that is to be commented out--

So the final > never appears. If instead I start with <!-- at the beginning 
of the line then terminate the comment, no hanging would occur.

-- 
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/1c40aad3-057c-431a-a6b1-0edf5df64238o%40googlegroups.com.

Reply via email to