readme/about/changelog/desktop.md
.one files with many attachments fail to import (#15117 by @personalizedrefrigerator)<span>s are hidden in HTML notes (#15089 by @personalizedrefrigerator)joplin.fs.archiveExtract plugin method (#14625).onepkg file import: Fix import failure when notebook titles contain certain Unicode characters (#14090) (#14084 by @personalizedrefrigerator).onepkg file import: Fix import failure when notebook titles contain certain Unicode characters (#14090) (#14084 by @personalizedrefrigerator)titles as Markdown (#13876) (#13872 by @personalizedrefrigerator).one files from OneNote 2016 (#13391 by @personalizedrefrigerator)ocr_driver_id (#13051) (#13043 by @personalizedrefrigerator)$s creates math blocks on save (#12398) (#9593 by @personalizedrefrigerator)setting.globalValues and deprecate setting.globalValue (ef51386)joplin.shouldUseDarkColors API (fe67a44)==marked== text in the Markdown editor (#11794 by @personalizedrefrigerator)warn when a decryption error occurs (#11771 by @personalizedrefrigerator)electron-builder and @electron/rebuild (#11512) (#11508 by @personalizedrefrigerator)undefined errors in translations (#11407 by Self Not Found)editor.setText (#11117) (#11105 by @personalizedrefrigerator)exports fail to load (#10900 by @personalizedrefrigerator)safeStorage for keychain support (#10535 by @personalizedrefrigerator):w trigger sync in the beta editor's Vim mode (#10778) (#10768 by @personalizedrefrigerator)Avenir Next (#10686) (#10679 by @personalizedrefrigerator)settings.json are lost on startup (#10458) (#10381 by @personalizedrefrigerator)settings.json not applied (#10383) (#10382 by @personalizedrefrigerator)--enable-wayland-ime flag to fix input method issues on startup (#10349) (#10345 by @personalizedrefrigerator)@codemirror/search (#10205 by @personalizedrefrigerator)webviewApi.postMesage) (#10158) (#8931 by @personalizedrefrigerator)Trying to fix the Apple silicon version. If you are not on this platform you can skip this update.
@codemirror/lang-markdown and @lezer/highlight (#9753) (#9752 by Henry Heino)Authorization tokens (#9707) (#9706 by Henry Heino)o not working in Vim normal mode (#9700) (#9699 by Henry Heino)--disable-gpu flag (#9179) (#9130 by @orl0)Note: This release does not support Windows 7, 8, or 8.1. See the release notes for version 2.12.7.
s in markdown while still preserving initial paragraph indentation (#8529) (#8530 by Henry Heino)--safe-mode command line flag (#7919) (#7889 by Arun Kumar)null variable (#7987) (#7986 by Henry Heino)MasterKey from Sync Status report (#8026) (#7940 by Arun Kumar)null variable (#7987) (#7986 by Henry Heino)Important: If you use custom notebook icons and sync with the mobile app, make sure also install the latest 2.7 mobile app.
joplin.workspace.onResourceChange (2660ff3)CAUTION: This release will ask you to upgrade your sync target, whether it's Dropbox, OneDrive, Joplin Cloud, etc. Once it is done, only apps version 2.3+ will be able to sync with it, so make sure you are ready to upgrade all your apps before installing this version.
IMPORTANT: If you are a plugin developer or if, as a user, you notice a plugin that no longer works, please read this post: https://discourse.joplinapp.org/t/19278
Attention: The default font size has been changed in the Markdown editor. You can change it back in Config > Appearance > Editor font size.
joplin.plugins.installationDir to allow accessing external files packaged with the pluginjoplin.plugins.require API to allow using sqlite3 or fs-extra from a pluginplugins.dataDir function, to provide a path for plugin to store its own datajoplin.plugins.installationDir to allow accessing external files packaged with the pluginjoplin.plugins.require API to allow using sqlite3 or fs-extra from a pluginplugins.dataDir function, to provide a path for plugin to store its own datafile:// URLs would not be rendered correctlyAt this point, this release is only to allow using Joplin Server as a sync target.
Fixed ENEX import regression: Fix issue when importing ENEX file that contains invalid list elements
Although soft-break is part of the CommonMark spec, it requires a special editor that can wrap text at a certain limit. That doesn't make much sense in Joplin, where the editor can have various sizes, from desktop to mobile, and where the tools to wrap text are not present.
Breaking Changes:
joplin.views.dialogs.open() now returns an object instead of the button ID that was clicked. So for example instead of getting just "ok", you will get { "id": "ok" }. This is to allow adding form data to that object.Deprecated:
The following features are deprecated. It will still work for now but please update your code:
create() functions under joplin.views now take a viewId as a first parameter.MenuItemLocation.Context is deprecated and is now an alias for MenuItemLocation.NoteListContextMenuapp_min_version manifest property is now required. If not provided it will assume v14.id manifest property is now required. If not set, it will be the plugin filename or directory.Plugin doc has been updated with some info about the development process.
Breaking Changes:
joplin.views.dialogs.open() now returns an object instead of the button ID that was clicked. So for example instead of getting just "ok", you will get { "id": "ok" }. This is to allow adding form data to that object.Deprecated:
The following features are deprecated. It will still work for now but please update your code:
create() functions under joplin.views now take a viewId as a first parameter.MenuItemLocation.Context is deprecated and is now an alias for MenuItemLocation.NoteListContextMenuapp_min_version manifest property is now required. If not provided it will assume v14.id manifest property is now required. If not set, it will be the plugin filename or directory.Plugin doc has been updated with some info about the development process.
Breaking Changes:
joplin.views.dialogs.open() now returns an object instead of the button ID that was clicked. So for example instead of getting just "ok", you will get { "id": "ok" }. This is to allow adding form data to that object.Deprecated:
create() functions under joplin.views now take a viewId as a first parameter. It will still work for now if you don't provide one, but please update your plugins.MenuItemLocation.Context is deprecated and is now an alias for MenuItemLocation.NoteListContextMenuPlugin doc has been updated with some info about the development process.
IMPORTANT: If you use the Clipper API, please note that there are a few breaking changes in this version. See this link for more information: https://github.com/laurent22/joplin/pull/3983
IMPORTANT: If you use the Clipper API, please note that there are a few breaking changes in this version. See this link for more information: https://github.com/laurent22/joplin/pull/3983
openProfileDirectory command and menu item<strike>, <s> tags (strikethrough) from Evernote (#3936 by Ian Slinger)openProfileDirectory command and menu item<strike>, <s> tags (strikethrough) from Evernote (#3936 by Ian Slinger)IMPORTANT: If you use the Clipper API, please note that there are a few breaking changes in this version. See this link for more information: https://github.com/laurent22/joplin/pull/3983
openProfileDirectory command and menu item<strike>, <s> tags (strikethrough) from Evernote (#3936 by Ian Slinger)openProfileDirectory command and menu item<strike>, <s> tags (strikethrough) from Evernote (#3936 by Ian Slinger)openProfileDirectory command and menu item<strike>, <s> tags (strikethrough) from Evernote (#3936 by Ian Slinger)openProfileDirectory command and menu item<strike>, <s> tags (strikethrough) from Evernote (#3936 by Ian Slinger)<strike>, <s> tags (strikethrough) from Evernote (#3936 by Ian Slinger)<strike>, <s> tags (strikethrough) from Evernote (#3936 by Ian Slinger)This release is to fix the sync lock issues on devices that have an incorrect clock. Specifically, it should fix this error: "Cannot acquire sync lock: either the lock could be written but not read back. Or it was expired before it was read again".
This release will ask you to upgrade your sync target and, once it is done, only the latest clients will be able to sync with this sync target. So please make sure you upgrade your other clients too (mobile, cli, etc.).
This version also includes an update to the search engine and as a result starting the app the first might be SLOW, as the search engine indexes all your notes. It might take from a few seconds to several minutes depending on how large your note collection is. This is a one off operation.
IMPORTANT: This pre-release will ask you to upgrade your sync target and, once it is done, only the latest clients will be able to sync with this sync target. Currently that includes the desktop app (v1.0.234+) and Android app (v1.0.337+). It means if you are using these two clients you'll be fine. However if you are using the iOS or CLI clients you might want to wait till these clients are updated. Any issue with the sync target upgrade, please post on the forum.
This version also includes an update to the search engine and as a result starting the app the first might be SLOW, as the search engine indexes all your notes. It might take from a few seconds to several minutes depending on how large your note collection is.
Regression fixes:
Main changes:
IMPORTANT: This pre-release will ask you to upgrade your sync target and, once it is done, only the latest clients will be able to sync with this sync target. Currently that includes the desktop app (v1.0.234+) and Android app (v1.0.337+). It means if you are using these two clients you'll be fine. However if you are using the iOS or CLI clients you might want to wait till these clients are updated. Any issue with the sync target upgrade, please post on the forum.
This version also includes an update to the search engine and as a result starting the app the first might be SLOW, as the search engine indexes all your notes. It might take from a few seconds to several minutes depending on how large your note collection is.
Regression fixes:
Main changes:
IMPORTANT: This pre-release will ask you to upgrade your sync target and, once it is done, only the latest clients will be able to sync with this sync target. Currently that includes the desktop app (v1.0.234+) and Android app (v1.0.337+). It means if you are using these two clients you'll be fine. However if you are using the iOS or CLI clients you might want to wait till these clients are updated. Any issue with the sync target upgrade, please post on the forum.
This version also includes an update to the search engine and as a result starting the app the first might be SLOW, as the search engine indexes all your notes. It might take from a few seconds to several minutes depending on how large your note collection is.
Regression fixes:
Main changes:
Important: This pre-release will ask you to upgrade your sync target and, once it is done, only the latest clients will be able to sync with this sync target. Currently that includes the desktop app (v1.0.234+) and Android app (v1.0.337+). It means if you are using these two clients you'll be fine. However if you are using the iOS or CLI clients you might want to wait till these clients are updated. Any issue with the sync target upgrade, please post on the forum.
This version also includes an update to the search engine and as a result starting the app the first might be SLOW, as the search engine indexes all your notes. It might take from a few seconds to several minutes depending on how large your note collection is
Important: This pre-release will ask you to upgrade your sync target and, once it is done, only the latest clients will be able to sync with this sync target. Currently that includes the desktop app (v1.0.234+) and Android app (v1.0.337+). It means if you are using these two clients you'll be fine. However if you are using the iOS or CLI clients you might want to wait till these clients are updated. Any issue with the sync target upgrade, please post on the forum.
This version also includes an update to the search engine and as a result starting the app the first might be SLOW, as the search engine indexes all your notes. It might take from a few seconds to several minutes depending on how large your note collection is.
This release is to remove the hierarchical/nested tags feature for now, as it has a performance issue.
This release includes a rewrite of the note editor component in order to allow further improvements (which were no longer possible) and to make it easier to maintain both WYSIWYG editors and regular editor.
A new button "Code View" has been added to switch between the WYSIWYG editor and the Markdown editor.
The note-specific toolbar has also been moved next to the title field for now because it wasn't practical to leave it with the editor-specific toolbar (and also not logical). It might be tweaked or moved later on once we have a clearer idea of what we want to do.
Finally, the tag bar has been moved to the top of the note editor pane. Again this was in part necessary after the refactoring, but also more logical since the tags are relevant to the note, but not to the note content. So it makes more sense to have the editor toolbar right next to the editor content, without the tag bar in between, as before.
This release includes a rewrite of the note editor component in order to allow further improvements (which were no longer possible) and to make it easier to maintain both WYSIWYG editors and regular editor.
A new button "Code View" has been added to switch between the WYSIWYG editor and the Markdown editor.
The note-specific toolbar has also been moved next to the title field for now because it wasn't practical to leave it with the editor-specific toolbar (and also not logical). It might be tweaked or moved later on once we have a clearer idea of what we want to do.
Finally, the tag bar has been moved to the top of the note editor pane. Again this was in part necessary after the refactoring, but also more logical since the tags are relevant to the note, but not to the note content. So it makes more sense to have the editor toolbar right next to the editor content, without the tag bar in between, as before.
This release includes a rewrite of the note editor component in order to allow further improvements (which were no longer possible) and to make it easier to maintain both WYSIWYG editors and regular editor.
A new button "Code View" has been added to switch between the WYSIWYG editor and the Markdown editor.
The note-specific toolbar has also been moved next to the title field for now because it wasn't practical to leave it with the editor-specific toolbar (and also not logical). It might be tweaked or moved later on once we have a clearer idea of what we want to do.
Finally, the tag bar has been moved to the top of the note editor pane. Again this was in part necessary after the refactoring, but also more logical since the tags are relevant to the note, but not to the note content. So it makes more sense to have the editor toolbar right next to the editor content, without the tag bar in between, as before.
This release includes a rewrite of the note editor component in order to allow further improvements (which were no longer possible) and to make it easier to maintain both WYSIWYG editors and regular editor.
A new button "Code View" has been added to switch between the WYSIWYG editor and the Markdown editor.
The note-specific toolbar has also been moved next to the title field for now because it wasn't practical to leave it with the editor-specific toolbar (and also not logical). It might be tweaked or moved later on once we have a clearer idea of what we want to do.
Finally, the tag bar has been moved to the top of the note editor pane. Again this was in part necessary after the refactoring, but also more logical since the tags are relevant to the note, but not to the note content. So it makes more sense to have the editor toolbar right next to the editor content, without the tag bar in between, as before.
This release includes a rewrite of the note editor component in order to allow further improvements (which were no longer possible) and to make it easier to maintain both WYSIWYG editors and regular editor.
A new button "Code View" has been added to switch between the WYSIWYG editor and the Markdown editor.
The note-specific toolbar has also been moved next to the title field for now because it wasn't practical to leave it with the editor-specific toolbar (and also not logical). It might be tweaked or moved later on once we have a clearer idea of what we want to do.
Finally, the tag bar has been moved to the top of the note editor pane. Again this was in part necessary after the refactoring, but also more logical since the tags are relevant to the note, but not to the note content. So it makes more sense to have the editor toolbar right next to the editor content, without the tag bar in between, as before.
This release includes a rewrite of the note editor component in order to allow further improvements (which were no longer possible) and to make it easier to maintain both WYSIWYG editors and regular editor.
A new button "Code View" has been added to switch between the WYSIWYG editor and the Markdown editor.
The note-specific toolbar has also been moved next to the title field for now because it wasn't practical to leave it with the editor-specific toolbar (and also not logical). It might be tweaked or moved later on once we have a clearer idea of what we want to do.
Finally, the tag bar has been moved to the top of the note editor pane. Again this was in part necessary after the refactoring, but also more logical since the tags are relevant to the note, but not to the note content. So it makes more sense to have the editor toolbar right next to the editor content, without the tag bar in between, as before.
This is to fix a few regressions in previous release.
Goto Anything modal on outside click (#2940 by Siddhant Sehgal)The main purpose of this pre-release is to allow evaluating the WYSIWYG editor.
.desktop file & force refresh (#2479 by Brandon Wulf)More fixes following latest pre-release.
Fix more regressions from previous pre-release.
Fixed issue from previous pre-release 1.0.187.
.desktop file & force refresh (#2479 by Brandon Wulf)This is to test the Electron framework upgrade and the switch to a separate note renderer. If you find any bug please report on the forum or GitHub tracker.
<kbd> tag support (#2044) (#2043)Note that on Windows the code signing certificate has been renewed, which some times triggers warnings when installing the application.
Ctrl+K (#1705) (#1342)Cmd+Opt+T / Ctrl+Alt+T) (#1638)This release only adds additional logging for the note history feature.
Same as v1.0.151 but with a fix to the migration issue, that was in turns affecting synchronisation.
Same as v1.0.150 but with a small fix to set the resources file size.
This is to test the revision service. It is not yet recommended to upgrade as the corresponding mobile apps have not been released to the stores yet (the Android APK is available though).
This pre-release is mainly for testing the new rendering engine.
This is only for testing the Arabic translation.
To test Windows 32-bit build.
Note: this is the same as v132 but with a fix for the resizeable column bug, and for PDF export and printing.
Note: this is the same as v132 but with a fix for the resizeable column bug.
This big release aims at improving the overall usability of the application and to make it more accessible to newcomers.
Important: This release might be slow on startup due to the need to index all the notes, especially if you have many of them with lots of content. The best is simply to wait for it even if it takes several minutes. This is just a one off and afterwards startup time will be the same as before.
Important: This release might be slow on startup due to the need to index all the notes, especially if you have many of them with lots of content. The best is simply to wait for it even if it takes several minutes. This is just a one off and afterwards startup time will be the same as before.
This is mostly a bug fix release following the recent v115 release.
This is a rather large release which includes many of the pull requests that were submitted during Hacktoberfest, plus some extra improvements and bug fixes. Many thanks to all the contributors!
This is mainly a release to fix a bug related to the new IMG tag support.
/resources/:id/fileThis is a release only to get the new API out. If you do not need the functionalities of this API or you don't know what it is, you can probably skip this version.
To test the latest security fix only. Won't be released officially.
Note: this release is no longer signed to avoid issues with renewing certificates. If you get a warning or the application cannot be installed, please report on the forum on GitHub.
This is a bug-fix release following v100 with the following fixes:
Note: This is the same as 1.0.97, but with a fix for the Linux version, which could not start anymore.
If you're using the web clipper, make sure to also update it!
If you're using the web clipper, make sure to also update it!
This release is mainly to fix various issues with the recently released Web Clipper.
Same as v1.0.90 but with a fix for #510
Note: This is the same as v84 but with the note creation bug fixed.
Note: This fixes an invalid database upgrade in the previous version.
Still more fixes and improvements to get v1 as stable as possible before adding new features.
IMPORTANT: If you use Nextcloud it is recommended to sync all your notes before installing this release (see below).