Wolfgang Thanks for the feedback.
Presumably this means I can't inspect the code for the fix via a tiddler (though presumably I could dump the source and inspect that) but I could still apply the fix via the custom plugin. Does that mean that I just dump all the code above into a tiddler and tag it with systemConfig? I'm not at all clear whether there'd be additional code I'd need to precede it with or end the tiddler with, never having created a plugin other than by importing. And feel free to warn me off if this approach is complex - I'm not very technical and am only looking to see if there's a simple solution within my reach, rather than a complex solution that demands a lot more time in the TW documentation and forums. It still seems odd that this problem persists in 2.4.1. I'll also see what happens if I map a drive letter to the UNC path. Meanwhile many thanks for your guidance as ever. Kevin On Oct 19, 11:39 pm, wolfgang <[EMAIL PROTECTED]> wrote: > Hi Kevin, > > > warning to leave the core alone and modify a plugin instead, I wasn't > > sure where this specific core function exists and hence which shadow > > tiddler to check and modify if necessary. Which would it be please? > > core function all exists in the TW file itself and you could see and > edit them - which is warned of - if you open your TW not in a browser > - but in an editor. There are no core functions in shadowed tiddlers. > > Regards, > > W. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
