ID del Client: 28e9bf497ba347efa2387d4c6f35d216
Sinc. versione: 3
Profilo versione: 47
Portachiavi supportato: Sì
Revisione: 826006c
Autolinker: 1.0.4
Automatic Backlinks to note: 3.0.3
Backup: 1.4.1
Combine notes: 1.2.2
Conflict Resolution: 1.2.3
Copy link to active note: 1.0.1
Csv Import: 1.0.1
Email Note: 1.2.2
Freehand Drawing: 2.9.1
Headings 4 to 6: 1.0.1
Markdown Table: Sortable: 1.2.2
Menu items, Shortcuts, Toolbar icons: 1.1.0
Note Link System: 0.8.0
Note list and sidebar toggle buttons: 1.0.3
Note overview: 1.7.1
Note Tabs: 1.4.0
OCR: 0.3.2
Paste Special: 1.1.2
Plugin Bundle: 0.5.5
Quick HTML tags: 0.2.0
Quick Links: 1.3.2
Suitcase: 0.3.3
Toggle Markup Type: 1.0.0
Sync target
WebDAV
Editor
Rich Text Editor
What issue do you have?
Hello all,
it is possible to roll back to stable versione 2.14.22 from pre-release 3.0.8?
I just tried to do so with the portable version but I get a profile error (required version for 2.14.22 is 46 while 3.0.8 uses 47).
Is there a simple way to downgrade or it's better to way for a fix in the 3.x version.
TIA
tony
The earliest version you can move back to without seeing the error is 3.03 (as shown in this table).
Reverting can be done but it involves deleting all your local Joplin data and downloading all your notes again from your WebDAV sync target. The downsides of this are that if you have lots of notes it will take time. Additionally you will also have to setup your plug-ins and customisations all over again.
If the issue for which you are wanting a fix is present in both the current version (2.14.22) and the latest pre-release version (3.0.8) it's probably worth just sticking with the pre-releases until v3.x is declared stable. Speaking of which, v3.x development is due to go into "freeze" soon with a planned publishing date in the first week of July.
Is the fix you are looking for related to a known issue? If not it may be worth explaining what you have found in an issue on GitHub (or a new support post here). Then the devs are hopefully aware of it during the "freeze" as that is where adding new features is halted and they concentrate on performance and any remaining bug fixes.
I believe that the reason was that the options did not work, in that after applying any formatting it was lost when moving from the note and it was then converted to Markdown.
The only relevant PR is #10059. It handles the first row as header row, but at the cost that not all options are available at the table menu. I guess the question is: Are the cell properties at the table context menu sufficient or do we need them at the top menu, too? In the latter case, we would need to define the entries for the top menu manually.
But indeed I think they won't work in most cases... except if the table contains elements that can't be converted back to Markdown. In that case the table is saved as HTML and any customisation is saved. But probably it means that if background colours are used the table should be saved as HTML
