-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Day One 2 breaks exporter #29
Comments
Yeah, sorry. Since I have no plans on buying Day One 2 I won't be able to bake in support for that, sorry. Maybe someone else could do a bit of research on the new data format and if it's even possible to create new posts from external sources? |
Hey, thanks for the reply! I think I can make the fix, but I'm not so familiar with how how Elizabeth is structured - if you could answer a couple of questions I'll have, I'd be happy to add in a Day One 2 exporter. |
I've forked it and created a DayOne2Export.js, butchered from your DayOneExport.js. However, I'm a little over my head - I'm getting an error you might be able to shed some light on.
when I tell it to use the new exporter (which I know it's pulling in - I have it dump out 'this' around line 198 inside
Any ideas? |
Elizabeth uses my DayOne library to read/write entries. I think you need to bake in DO2 support there first: |
Thanks Philipp, You're absolutely right, of course. You also know I have 3 months of Moves data I've not imported yet! :) It was a fairly simple tweak to get your Day One importer to support Day One (1) and Day One 2 - just running some checks and then I'll pop the changes over there. Thanks again! |
Hi dave, did you ever complete those checks and get it to work? |
I was in deeper than I hoped to be, @blueneogeo. In the end, I just symlinked the Day One 2 import folder (I think it's in ~/Library/Day One 2/ somewhere) to the Day One 1 import folder, and it carried on fine. For a while, anyway - something else has snagged for me and I need to look into it properly. Try the symlink for a quick solution that might work, though. |
Thanks, I will give your symlink solution a shot
…On 8 Dec 2016, 16:14 +0100, Dave Mee ***@***.***>, wrote:
I was in deeper than I hoped to be, @blueneogeo. In the end, I just symlinked the Day One 2 import folder (I think it's in ~/Library/Day One 2/ somewhere) to the Day One 1 import folder, and it carried on fine.
For a while, anyway - something else has snagged for me and I need to look into it properly. Try the symlink for a quick solution that might work, though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
The application storage has both changed names, and deprecated features - iCloud and Dropbox are no longer supported.
The text was updated successfully, but these errors were encountered: