Sorry about the late reply.  

Also, I should have been more clear that this behaviour occurs in fresh 
nodejs version of TW5 and not in the regular import between versions. 
Importing between two regular files preserves the dates.

The behaviour of changing dates to imported date appears in nodejs (fresh 
install and importing from a regular tiddlywiki file).

The correct dates show up when importing. But after restarting the server, 
all the imported tiddlers show up in the current date in the 'recent' 
timeline. I wasn't sure if this was the intended behaviour.

The load from file command line option  works correctly, the dates are 
preserved. 

So, there isn't any problem getting the right dates even in the nodejs 
version, as long as the command line is used and not the import option from 
the sidebar.

Thanks for the response.

On Wednesday, March 2, 2016 at 2:21:51 PM UTC+5:30, Jeremy Ruston wrote:
>
> > For my use case, where importing to a new wiki from older files, all the 
> old dates are lost, and timeline collapses to a single date 
>
> Are you importing a TW5 HTML file by drag and drop into another TW5 HTML 
> file in the browser? 
>
> The intended behaviour of TW5 on import is to preserve the modification 
> date of incoming tiddlers. Nor does the import process assign a 
> modification date to tiddlers that don’t have one. 
>
> I’d like to be able to reproduce the problem and understand what’s going 
> on. Would you be in a position to share the files concerned? Either 
> publically, or directly with me via email (jeremy (at) jermolene (dot) 
> com). 
>
> Best wishes 
>
> Jeremy

-- 
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/76fa3141-5289-47cf-bc29-ab863990fb9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to