Here are some new fixes and improvement
- Improved: Enable more options on multimd-table plugin (#1586)
- Improved: Improved config screen with dark theme
- Improved: Make bold text more visible (#1575)
- Fixed: Fix internal note links (#1587)
- Fixed: Fixed empty separators in menu
This morning Joplin gave a notification, that a new version is available, this update. I pressed yes, download the update, and my browser (Firefox, the latest release) began to download. However it took something like over five minutes to complete, and when it finally was downloaded, the OS gave me a warning about a suspicious file.I thought, that the download got corrupted and therefore tried to download anew. This time the download got stuck all together past a couple of minutes.
I’m running MS Windows 10 Enterprise N 64-bit on a 40 MB mobile connection, which works (e.g. Skype for business reports no issues and that’s picky software), so this looks like an issue on Github.
Here in download works fine and rarely was as fast as today. It downloads from Amazon AWS, maybe you have problems to access this service.
Is it OK to upgrade to 158 from 152 on desktop before the IOS upgrade is available?
i did that and use android which i do not upgrade yet and works fine
Thanks. I’ve updated on Windows and Android, and IOS is still running fine.
The problem was the note history change. Since this has been rolled out to all platforms, you should not have any problems upgrading.
In the future Laurent will notify users, if an upgrade of only one platform will block a sync.
I understand the last terminal client version is v1.0.137. Will there be a compatible version to current Linux desktop v1.0.158? I had to upgrade because of the note history changes in Android. I use the terminal client version to automatically backup up (export) my notes in clear text via a cron job. Would be very happy if I could do that again
@maxmopp I’m not sure what you are asking. The CLI version (1.0.137) is able to understand type 13 notes (note history entries).
Maybe I miss something else, but my joplin throws:
Error: Unknown profile version. Most likely this is an old version of Joplin, while the profile was created by a newer version. Please upgrade Joplin
I rebuilt joplin with nodejs v11.15.0
I meet the same behavior …
I have 1.0.158 and update joplin terminal like this
NPM_CONFIG_PREFIX=~/.joplin-bin npm install -g joplin
but get that error
joplin --profile ~/.config/joplin-desktop/
Error: Unknown profile version. Most likely this is an old version of Joplin, while the profile was created by a newer version. Please upgrade Joplin at https://joplinapp.org and try again.
at JoplinDatabase.upgradeDatabase (/home/foxmask/.joplin-bin/lib/node_modules/joplin/lib/joplin-database.js:272:38)
at JoplinDatabase.initialize (/home/foxmask/.joplin-bin/lib/node_modules/joplin/lib/joplin-database.js:623:33)
at process._tickCallback (internal/process/next_tick.js:188:7)
Hmm, this is really strange and I don’t quite understand why this is happening. @laurent will have to look at this. IMO this is a bug, because this shouldn’t be happening, but maybe I’m wrong.
@foxmask, does it still happen with the latest version cli-v1.0.139?
@laurent at least at work that seems ok .
Could update to joplin 1.0.139 today: works perfectly. Thanks a lot