The solution would be if Bob used a special path name (virtual path) for the Wikis, and not for images. That way the two path types could be distinguished without making Bob incompatible with other uses of TW.
-- Mark On Friday, October 26, 2018 at 3:43:31 AM UTC-7, @TiddlyTweeter wrote: > > Jed Carty wrote: >> >> The reasons are the same as why until 5.1.18 comes out the node version >> didn't have a static file server and that the static file server with the >> server in 5.1.18 does the same thing: >> > > Right. I don't have any problem with it per se now I better understand it. > And I'm grateful you keep malicious hackers away. You have that skill & its > good. > > The singular issue I have is that node/Bob serving of files involves (1) > an url path that has a "folder" that does not exist on the hard drive so: > (2) the wiki end up with "hard-coded" addresses that don't exist on disk. > Which means (3) you have to manually edit them to adjust if you export to > single file. That is the central issue for me to solve for the kind of wiki > I make, involving quite a lot of images. > > Regarding me using the word "virtual". I don't really mind what word is > used actually. But the point was to help users, not familiar with node/Bob > that pathing to external local files do use a "fictive entity" in the path > (needed in the world of Bob/node, but a bit of a drag in any other). *I* > found that hard to grasp. And I think others would too, at first. > > Best wishes > Josiah > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ceb78746-a88e-4c46-adf3-c4b7095fb417%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
