-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Older classic TiddlyWikis are not considered "valid" #83
Comments
This might be a wontfix. As well as the versionArea differences, there's some more incompatibilities. Some things I learned about the older classic TiddlyWikis (I'm looking at http://simon.tiddlyspot.com/ FYI).
vs
1 in particular makes the injection of the ThostUploadPlugin not work. It gets added, but it's not recognized by TiddlyWiki. We could write some more code to detect the tiddler format, and handle it correctly, but maybe it's not worth the effort. Effectively we'd need to support three types of TiddlyWiki:
|
I'm not sure how much demand there is for supporting TiddlyWikis from 2006 on TiddlyHost. Perhaps "Classic-older" can remain unsupported. |
As a workaround, I think probably "Classic newer" supports importing tiddlers from a "Classic older" file. This could be documented, or at least hinted at. |
Another blocker to supporting these is that the plugin doesn't work. For example doHttp is not defined. So we'd need an older compatible version of that as well. |
The old format is from before TW 2.5 or so. Actually it's not worth it since the thostuploadplugin don't work. doHttp is not defined. Probably give up now.. Issue #83
The old format is from before TW 2.2 or so. (Actually this is on hold since I realised the thostuploadplugin won't work. doHttp is not defined for example.) Probably give up now.. Issue #83
Some of the methods used to "validate" a TiddlyWiki classic fail for TiddlyWikis older than a certain date.
Not sure what the version is but it's between 2.1.2 and 2.5.0.
This is only an impact for users who upload an old site. Creating a new "classic" site gets you 2.9.2.
The reason is because <script id="versionArea"> doesn't exist.
The text was updated successfully, but these errors were encountered: