Upgrading external-core tiddlyhost files

[Springer]

How best to upgrade external-core tiddlyhost file?

To confirm my worry that it doesn’t stay external-core while following standard drag-and-drop upgrade path (https://tiddlywiki.com/upgrade) I just tried upgrading one of the projects that I initiated with tiddlyhost’s external-core option. Sure enough, it’s no longer external-core.

For folks who aren’t super-tech-savvy, what’s the best path to upgrade an external-core wiki hosted at tiddlyhost?

-Springer

[simon]

I don’t think it’s possible using the standard upgrade wizard, but here is a method that I’ve used successfully.

[TW_Tones]

There is related documentation here Upgrading your standalone wiki at the bottom of Using the external JavaScript template

It’s great you documented a method @simon, but surely there is another way?

• It seems to me one should be able to change the external-core tiddlyhost file reference, save and reload. I could be wrong as you change the root tiddler.
• However I note here Using the external JavaScript template for single file wikis it must be in the current folder.
• I had hoped it could point to an external core on a CDN

@Springer

Sure enough, it’s no longer external-core.

• This could be useful for an initial offline test
• Perhaps we could have an upgrade external core site?

[Mark_S]

I guess this begs the question – what happens during an upgrade? If it’s just the core tiddlers getting replaced, then all you should have to do is point at the new core to be up and running. I suspect that there other things (e.g. configuration tiddlers) that have to happen too.

[simon]

What is the “export tiddlywiki core” button referred to in those docs? I can’t find that button anywhere.

FWIW, I do think converting from a self-contained TiddlyWiki to an external core TiddlyWiki by modifying $:/config/SaveWikiButton/Template should work. Perhaps I’ll give that method a try soon.

[Mark_S]

I feel like those instructions keep reverting to node.js, even though the targeted section is for stand-alone TW. Most people are not going to want to launch node.js just to create a stand-alone wiki. In any event, if you scroll up the instruction tiddler, you’ll see the button to export the core. I think for most people with standalone wikis, these instructions will be more useful:

How to reduce the size of your Tiddlywiki

Using the external JavaScript template If you want to start from a new wiki, you can find a empty tiddlywiki with external core here, or here for the latest prerelease . You will need to download the core too, see the steps bellow. Obtain the external JavaScript file (core) [export core js] In your wiki (or a new one like https://tiddlywiki.com/empty.html), create a tiddler containing the text {{$:/core/ui/ExportTiddlyWikiCore}}. In the current releases, you can simply navigate to $:/core/…

[simon]

@simon

…converting from a self-contained TiddlyWiki to an external core TiddlyWiki by modifying $:/config/SaveWikiButton/Template should work

Here’s some instructions for doing that. It’s pretty much exactly as described here but I tried to make it less scary.

So I guess that’s a second viable solution, i.e. first use the normal upgrade process, then convert the resulting internal core TiddlyWiki back to external core like this.

[Springer]

@simon

first use the normal upgrade process, then convert the resulting internal core TiddlyWiki back to external core like this .

Great, thanks everyone! Maybe someday something like the standard drag-and-drop process can be streamlined for external-core files, but this is certainly workable enough, and helpfully explained.

-Springer

[Mark_S]

Are all versions of the core supported on TiddlyHost? If not, is there a list?

The reason I ask is, what if I have a wiki that I want to externalise the core, but don’t want to upgrade? (Because the upgrade would break some custom code).

Thanks!

[tomzheng]

@TW_Tones

However I note here Using the external JavaScript template for single file wikis it must be in the current folder.

It is not necessary to have the html files and corejs files in the same folder. For example tomzheng wiki — decentral 20k tiddlywiki

<script src="https://tomzheng.com/f/theme-vanilla-5.3.5.js" <script src="https://tomzheng.com/f/theme-snowwhite-5.3.5.js" <script src="https://tomzheng.com/f/plugin-markdown-5.3.5.js" <script src="https://tiddlyhost.com/tiddlywikicore-5.3.5.js"

[Mark_S]

How do we hack TW to allow this?

Thanks!

[simon]

@Mark_S

Are all versions of the core supported on TiddlyHost? If not, is there a list?

Tiddlyhost has an external core js file for versions 5.2.3 and higher. See here for a list.

[tomzheng]

Loading tiddlywiki and plugins in html

Manually reduce the size of tiddlywiki without using cdruan’s external js plugin. cdruan updated this plugin two years ago, and the plugin also suggests to be careful with it. This time the topic, cdruan is not present either. So I tried the method of manually reducing the size of tiddlywiki. The result of the attempt was a file size reduction from 107KB to 14KB. There are some problems with the content of this topic above. But the topic can’t be edited anymore. So some revision updates are in…

[telumire]

I made a post back in september where I explain how to upgrade a tiddlywiki in place using wikitext, see: Updating a single file tiddlywiki in-place

I use this method regularly since then, so far so good.

Related: An easier way to update a external core tiddlywiki · tiddlyhost/tiddlyhost-com · Discussion #430 · GitHub, [IDEA] Allow in place upgrades for single file TW · Issue #9155 · TiddlyWiki/TiddlyWiki5 · GitHub