mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-26 21:05:55 +03:00
[GH-ISSUE #1094] no way of importing cjon files? #457
Labels
No labels
android 🤖
assigned to core 🦹
bug 🐛
documentation 📚
documentation 📚
duplicate 🚫
external issue 🔼
external issue 🔼
feature request 🌟
funded on issuehunt 💵
help wanted 🆘
improvement request 🔨
improvement request 🔨
ios 🍎
mobile 📱
needs investigation 🔬
needs more info ℹ️
needs specs 📐
plugin idea 🔌
plugin idea 🔌
poll 🗳️
pull-request
question ❓
rewarded on issuehunt 🎁
security issue 🔑
won’t fix ❌
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/BoostNote-App#457
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jsulam on GitHub (Aug 17, 2021).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/1094
Current behavior
Cannot import cjon files from Boostnote 0.11 that I hold locally.
Expected behavior
There are a number of importing notes options, but none of them apply to previous versions of boostnote.
Environment
Desktop/Web
@Komediruzecki commented on GitHub (Aug 17, 2021):
Hi, jsulam,
The notes import into cloud space is for other systems, between boost note versions you can migrate data (local space to cloud) or transfer from legacy to boost note next (legacy file system to new file system space).
There is a way to do this but it's a bit complicated.
The steps would be:
Note that newer application versions will not support local space file system storages and for that you need to install local space only desktop application: https://github.com/BoostIO/BoostNote.next-local/releases/tag/v0.21.1
If I misundestood something, and you want to just use local file system space and load previous notes from legacy boostnote (*.CSON) then you can follow the above procedure but do not migrate the local storage to cloud (rather to new local space only desktop application - with instructions provided on latest release from this repository)
Sorry for the troubles, for last case it should be easy to do from local space only application but currently there is a fix which will be released soon (no space tab in preferences)
Let me know if you have any questions
@jsulam commented on GitHub (Aug 17, 2021):
Thanks Komediruzecki!
I think I'm half way there:
I also do not think my local boostnote.next is logged in to my boostnote.io account, but I cannot find any "log in" option here in v.019.
Do you see anything I might be missing?
@Komediruzecki commented on GitHub (Aug 17, 2021):
Hi,
Did you try reloading the app on 401? (
ctrl+r)Some screenshot would be helpful as I have hard time understanding what went wrong, so please describe steps in detail and provide some screenshot of the steps.
Also open dev console tab (
ctrl+shift+ior from menu) and screenshot it for any additional errors.The things you are describing should all work as expected but there might be a confusion between the applications itself.
So let me link you issue where I described the current state of boost note desktop apps: https://github.com/BoostIO/Boostnote/issues/3720
In short:
All of this started from 0.20.x so I am not sure why you would not see Sign In in 0.19.x - assuming you installed the app from this repository? (of course new repository probably does not have previous versions)
For the 401 error, you should probably be creating cloud space first (sign in etc) and then migrate the notes to particular cloud workspace, have you done that? (please also ensure internet connection)
@jsulam commented on GitHub (Aug 17, 2021):
Hi,
Yes, reloading does not help. Here's the screenshot of the workspace.
Upon clicking on the cloud symbol (bottom left), i'm prompted with this:

And after selecting "Migrate this local space.." I get the error message:

Note that the Next button is disabled.
The console dev tab does reflect errors, but it's hard for me to understand their meaning:

@jsulam commented on GitHub (Aug 17, 2021):
Here's an update: I realized I could go and manually export each of the folders in the old boostnote as md files, and then create each of these folders and directly import the corresponding files either via the boostnote.io or into a cloud space with the newest versions of Boost Note.
This is not perfect (some attachments are lost), but it'll do for now. Thanks for your help @Komediruzecki
@Komediruzecki commented on GitHub (Aug 18, 2021):
Hi,
So, assuming you imported legacy notes successfully into file system space in one of the previous versions, to migrate to cloud I would suggest installing latest version.
You will get prompt that the FS storage is not supported and option to migrate data.
For signing in, can you screenshot the space switcher and how does it miss the sign in?
Can you click on get started and try create new test cloud space with some sign in?
401 generally mean you didnt auth well, so sign out sign in might help, but I would do that in latest version to ensure application is bug free.
Glad to hear the workaround, yes notes can be exported from local space.
Please try the above, the most important being logging in latest boost note in cloud space, and trying migrating, you should get your attachments easily this way.
If you can, please document as much details, steps and screenshot for me to analyse the problem.
@Rokt33r commented on GitHub (Aug 19, 2021):
@jsulam The feature is discarded from the app but I think I can still help you by writing some migration script so you can migrate more easily. If you still need help, please join our slack and send me a DM(@rokt33r). We can even do a video call if you need. Anyway, sorry for the trouble.
Our slack channel : https://join.slack.com/t/boostnote-group/shared_invite/zt-cun7pas3-WwkaezxHBB1lCbUHrwQLXw
@jsulam commented on GitHub (Aug 19, 2021):
Got it - thank you all!
@Komediruzecki commented on GitHub (Aug 19, 2021):
No problem,
if you still have problems with this, please don't hesitate to ask more questions.