Just trying to correctly guess here, as I'm out of wits here: I would 
suspect that the same origin policy comes in here; this means that your 
referenced PDFs need to be imported into your Node.js-based TW5 too. To the 
best of my limited knowledge this would be a manual process you need to 
carry out directly on the file system where your tiddlers are stored. You 
need to place the PDFs into a subfolder with the same name and hierarchy as 
you did so far with your stand-alone TW5.

Regards,
-- TheDiveO

On Thursday, September 25, 2014 10:02:45 PM UTC+2, prsmendonca wrote:
>
> Hi!
>
> Many thanks, that did 90% of the work. The only problem I've had so far 
> were with externalized tiddlers of type "application/pdf", where the field 
> "_canonical_uri" contained an absolute path to a pdf file; for those 
> tiddlers, the pdf is no longer displayed in a frame, as it did before. 
> Imported pdfs show just fine. I have seen the post "under under Node.js, 
> why does _canonical_uri need a doubleurlencoded of the tiddler title?" it 
> seems to be relevant to my problem, but I am not entirely sure. At any 
> rate, I wouldn't know how to provide to "_canonical_uri" a 
> "doubleurlencoded of the tiddler title." The answer there seems to indicate 
> the use of <$view ... format="doubleurlencoded"/>, but, if yes, where? 
>
> Thanks again!
>
> P
>
> On Thursday, September 25, 2014 11:10:25 AM UTC-7, TheDiveO wrote:
>>
>> If you already have an "empty" TW5 server instance up and running then 
>> one way could be to navigate your browser to this server instance 
>> (localhost:8080). Then drag the file containing your single-file TW5 
>> instance into the browser and follow the normal import procedure. You 
>> should then see the newly imported tiddlers getting synchronized as 
>> individual files with your local file system. If you have many tiddlers 
>> then you may want to organize them into subfolders. Maybe the hierarchical 
>> filesystem sync adaptor then may be of interest,  see my ThirdFlow plugin.
>>
>> There are probably other ways to explode a single-file TW5 into its 
>> tiddlers ... so I'm also interested to learn about other solutions. 
>>
>> Regards,
>> TheDiveO
>>
>> Am Donnerstag, 25. September 2014 18:28:28 UTC+2 schrieb prsmendonca:
>>>
>>> Hi, there!
>>>
>>> (First posting on this group, please do school me on the appropriate 
>>> netiquete.)
>>>
>>> Not quite sure how to phrase my question - I lack the tiddlywiki 
>>> vocabulary, - but here it goes: I have a single-file tiddlywiki built on 
>>> TW5. I'd like to move it to a setup based on node.js. Could you please give 
>>> me some pointers on how to do it? I am all set on setting up node.js and 
>>> running a server-based tiddlywiki.
>>>
>>> Many thanks!
>>>
>>> P
>>>
>>

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Reply via email to