Returning to the earlier discussion "Favicon is not displayed" 
<https://groups.google.com/forum/#!msg/tiddlywiki/ozfuGHdeG-U/tBDv4EKADAAJ> I'm 
glad to inform the community - the issue has just been resolved.

Somehow, I noticed the difference between html-codes in cases when favicon 
is displayed and is not:

Favicon is displayed:
<div created="20161225200011567" modified="20161225200033805" title=
"$:/favicon.ico" type="image/x-icon" revision="0" bag="default">

Favicon is not displayed:
<div _canonical_uri="./images/%2524%253A%252Ffavicon.ico" created=
"20180827172657219" modified="20180827172709036" title="$:/favicon.ico" type
="image/x-icon" revision="2" bag="default">

The difference is obvious: the favicon is not displayed when 
*_canonical_uri* mechanism is used for the favicon revealing.

So, I decided to exclude *$:/favicon.ico* from externalization. For this 
instead of the build command parameters below:

"externalimages": [
    "--savetiddlers [is[image]] images",
    "--setfield [is[image]] _canonical_uri 
$:/core/templates/canonical-uri-external-image text/plain",
    "--setfield [is[image]] text '' text/plain",
    "--rendertiddler $:/plugins/tiddlywiki/tiddlyweb/save/offline 
externalimages.html text/plain"
]

I implemented the following modified parameters:

"externalimages": [
    "--savetiddlers '[is[image]] *-[[$:/favicon.ico]]*' images",
    "--setfield '[is[image]] *-[[$:/favicon.ico]]*' _canonical_uri 
$:/core/templates/canonical-uri-external-image text/plain",
    "--setfield '[is[image]] *-[[$:/favicon.ico]]*' text '' text/plain",
    "--rendertiddler $:/plugins/tiddlywiki/tiddlyweb/save/offline 
externalimages.html text/plain"
]

And it works!

-- 
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/b33caba9-731e-43e7-a96f-b065bffff85a%40googlegroups.com.

Reply via email to