probably before the condition after line 68 of getexportlink.js we could 
detect if it was a type you were likely to place at the root (e.g. a pdf 
file) and then not construct the path as below: 

finalLink = path_to_root + "data/";

James

On Saturday, 9 July 2016 19:32:45 UTC+1, James Anderson wrote:
>
>
> 1. Fixed : 
> https://github.com/welford/twstaticblog/commit/c2ac0ff9458a6b1964551d37b5450b122f3be585
>
> I didn't notice as a copy 
> of $:/plugins/welford/twstaticblog/helper/staticbanner was still in my TW
>
> 2. probably requires a change to getexportlink.js i'm about 1 year out of 
> touch with this code, maybe Jeremy or someone could give me a hint?
>
> Thanks,
> James 
>
>
>
> On Saturday, 9 July 2016 19:00:57 UTC+1, Pak Ruengrot wrote:
>>
>> Hi James,
>>
>> Thanks for your blog generation tool. I downloaded it from your github 
>> and it worked quite well, although with some bugs (I think)
>>
>>
>>    1.  In this commit 
>>    
>> <https://github.com/welford/twstaticblog/commit/e0da79ba19d7a2a72afc31ec06e79b8b5040b5b0>
>>  where 
>>    you did a lot of renaming. Among them is the change from staticbanner 
>>    to blog-banner. But in helper/template.tag.html.tid 
>>    
>> <https://github.com/welford/twstaticblog/blob/4791a9b3a7af361e6482866e6a04b39a72071885/helper/template.tag.html.tid>
>>     you are still using staticbanner, compared to other templates .tid 
>>    files where you use blog-banner. This causes a banner in an individual 
>> tag 
>>    page to disappear, as no such tiddler exists in the plugin folder.
>>    2. In export/getexportlink.js 
>>    
>> <https://github.com/welford/twstaticblog/blob/4791a9b3a7af361e6482866e6a04b39a72071885/export/getexportlink.js>,
>>  
>>    a path to an individual post , is set to yyyy/mm/dd/post.html. However, 
>> if 
>>    in post I link to a local file via [ext[file|file.pdf]], then when 
>> rendered 
>>    this link is changed to yyyy/mm/dd/file.pdf. This link doesn't work 
>>    (when viwed as a single page) as file.pdf is in the root of the blog 
>>    folder. This behaviour doesn't happen to [img[pic.jpg]] though even 
>> though 
>>    pic.jpg is in the root of the blog folder
>>
>> Do you know how to fix the above issues?  
>>
>> Thanks,
>> Pak
>>
>>
>>
>> On Friday, July 8, 2016 at 12:07:07 AM UTC+7, James Anderson wrote:
>>>
>>> http://phasersonkill.com/tags.html
>>> http://phasersonkill.com/a-z.html
>>> http://phasersonkill.com/archived-articles.html
>>> http://phasersonkill.com/updated-articles.html
>>>
>>> My plugin/exporter generates* these. 
>>>
>>> *generates is the wrong word, by these tiddlers exist in my plugin and 
>>> my exporter picks them up and puts them in the correct place.
>>>
>>> On Thursday, 7 July 2016 17:44:18 UTC+1, Mat wrote:
>>>>
>>>> David, 
>>>>
>>>> note that you can actually export multiple tiddlers including a 
>>>> filtered set of  tiddlers via the Advanced Search -> Filter. Once you 
>>>> enter 
>>>> something into the search field, there's a (barely visible) export button 
>>>> to export the result. (IMO this feature is not located in a good place and 
>>>> it needs better control, e.g export river: I've also posted on related 
>>>> matters <https://github.com/Jermolene/TiddlyWiki5/issues/1687> on 
>>>> github.)
>>>>
>>>>
>>>>> 2) James' way also exports an updated tags page, an updated A-Z page, 
>>>>> and an updated 'Recent' page. Exporting as HTML is just the tiddler, 
>>>>> nothing more.
>>>>>
>>>>
>>>> Yes, that makes sense for a page. If there's a ToC, is this also 
>>>> updated/exported?
>>>>
>>>> <:-)
>>>>
>>>

-- 
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/de7e502d-3988-4568-90cf-e0c7038a5bd2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to