\whitespace trim
\import [subfilter{$:/core/config/GlobalImportFilter}]
\define saveTiddlerFilter()
[is[tiddler]] -[prefix[$:/state/popup/]] -[prefix[$:/temp/]] -[prefix[$:/HistoryList]] -[status[pending]plugin-type[import]] -[[$:/core]] -[[$:/boot/boot.css]] -[is[system]type[application/javascript]library[yes]] -[[$:/boot/boot.js]] -[[$:/boot/bootprefix.js]] +[sort[title]] $(publishFilter)$
\end
<!-- Important: core library is provided by serving URI encoded $:/core/templates/tiddlywiki5.js -->
\define defaultCoreURL() %24%3A%2Fcore%2Ftemplates%2Ftiddlywiki5.js
<$let coreURL={{{ [[coreURL]is[variable]then<coreURL>else<defaultCoreURL>] }}}>
{{$:/core/templates/tiddlywiki5-external-js.html}}
</$let>
the : all-external-js , saveTiddlerFilter macro
appears to
(i guess) minus ‘-’ prefixing filter is remove
and is used to exclude things contained in $:/core/templates/tiddlywiki5.js
I think you need to do a deep research into the external core if you want be sure the innerwiki to use it, however I would have thought it possible if the calling wiki uses it the innerWiki will as well.
The innerwiki is transient unless you save it, be carful not to overwrite the parent wiki, passing tiddlers with a different save to file name, to the innerwiki is possible.
tiddlyhost can optionally use external core, install innerwiki on it and see if the resulting inner core uses it. I am sure it’s documented somewhere and you just need to provide the right tiddlers to the innerwiki and start it and check it keeps the external core.
you would ask a technical need, you just need to dig a little deeper.
That shouldn’t matter as long as you have the pictures online. They don’t have to be in any particular folder, or any relationship to the main wiki. For instance:
idk but i had considered
the potential for minimization of innerwiki
using external-js
… it might be easier to test with a local copy ruining on node **
( aligning paths between client server is always fun but better/easier to debug if you can configure both locally )
** ill probably try the inner wiki plugin on node
when i have time to bork/fix my svr config(s)
Adjust https://tiddlywiki.com/tiddlywikicore-5.3.8.js to some relative path if you want.
If the latter template is saved in a tiddler named innerwiki external core template, then this works (I tested at https://tiddlywiki.com/editions/full/ which has the innerwiki plugin):
The innerwiki references the external core and if you save the innerwiki, the resulting html also references the external core.
However, there seems to be an innerwiki bug and child $data widgets are not properly inserted. For example the tiddlers defined by the following data widgets are not present in the innerwiki:
I think the reason it isn’t working is because the SPLIT_MARKER is looking for a string in the html which is not present for external core. Since the SPLIT_MARKER isn’t found, the data tiddlers are not implanted. See this code:
@TW_Tones is right. Coming up with my answer required researching the external core. Looks like @wiki_user researched the same.
I’ve been reading your posts for years, including many, many dictionary references. I read widely, and believe I have a fairly large vocabulary. This is the first time you’ve supplied a word I didn’t know. Thank you. I’ll have to remember that one!
I started doing them because we write in somewhat limited “computer English” here and, as an English teacher abroad, realizing many folk on this group are not native English speakers, I thought it useful to them to give a few extra words with their definitions.