How to switch back to the legacy Markdown editor after the upgrade to 3.1.20?

[adrianolszewski]

Operating system

Windows

Joplin version

3.1.20

Desktop version info

Joplin 3.1.20 (prod, win32)

Client ID: 90951b9bb06f4a24a36d25a9fb9374b7
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: 8199362

Autolinker: 1.0.4
Backup: 1.4.2
Copy Anchor Link: 1.1.0
Copy Code Blocks: 1.1.2
Draw.io: 2.2.0
Freehand Drawing: 2.12.0
MultiMarkdown Table Tools: 1.2.1
Note Link System: 0.8.0

Editor

Markdown Editor

What issue do you have?

[solved] After the upgrade all icons disappeared from the bar (as on the attached screenshot). [/solved]

Also, some of the plugins (like Note Link System, which was essential to my work) stopped working properly.

I remember a message that warned about the potential issue. I was just curious what "may not work" may actually mean, so I decided to give it a try.
I also remember that the message box suggested staying with the "legacy markdown editor". Since the new editor doesn't work for me and doesn't support the plugins, I would like now to switch to the "older" version, which allowed me to work.
How can I do that?
Do I need to uninstall 3.1.20 and reinstall the older 3.0.15 that worked fine for me?

---

EDIT:
OK, the old trick to hide this cursed button switching to WYSIWYG editor (ruining all plugins features) removed now all the buttons... I removed the custom CSS:

	/* removes the WYSIWYG button */
	 display: none !important;
}

and the icons now appeared.

/ I need to figure out how to hide the truly unwanted WYSIWYG button now. If only there was a single little [ x ] checkbox in the settings panel disabling it without all those CSS tricks, that can stop working unexpectedly /

But still, the MD editor doesn't work with the linking system plugin, so my question on how to restore the "legacy" one keeps valid

Screenshots

[adrianolszewski]

OK, found a topic about that:

What happened to overwrite after editor change

Operating system Linux Joplin version 3.1.18 Desktop version info Joplin 3.1.18 (prod, linux) Client ID: 31a65565d08c44a6beabd6fb2e6b47a9 Sync Version: 3 Profile Version: 47 Keychain Supported: Yes Revision: 26ae3f853 (dev) Admonition markdown extension: 1.1.0 Backup: 1.4.2 Combine notes: 1.2.2 Convert Text To New Note: 1.5.1 Create and go to tags and @notebooks: 1.3.7 Life Calendar: 1.4.1 Math Mode: 0.6.2 Note Tabs: 1.4.0 Paste Special URLs: 1.0.0 Quick Links: 1.3.2 Slash Comm…

Settings -> General -> Advanced ->
Use the legacy Markdown editor

Luckily my work is saved

[t0dd]

The icons and that pesky WYSIWYG editor button.

This is in my userchrome.css file:

/* removes the WYSIWYG (MARKDOWN/RICH TEXT) button */
/* …old method (Joplin 3.0.z and older) */
/*div.editor-toolbar div button {
    display: none !important;
}*/
/* …new method (Joplin 3.1.z and newer) */
div.editor-toolbar .markdown-active {
  display: none !important;
}

UPDATE: a prior version of this used div.editor-toolbar div button[title="Toggle editors"] But that relies on the English words "Toggle editors". .markdown-active is far better.

[ACR36940]

@t0dd

/* removes the WYSIWYG (MARKDOWN/RICH TEXT) button */
/* …old method (Joplin 3.0.z and older) */
/*div.editor-toolbar div button {
    display: none !important;
}*/
/* …new method (Joplin 3.1.z and newer) */
div.editor-toolbar div button[title="Toggle editors"] {
    display: none !important;
}

A littel problem.
The title changes with the language (In spanish needs title="Alternar editores" )

[personalizedrefriger]

An alternative that doesn't rely on title might also be

div.editor-toolbar .markdown-active {
  display: none !important;
}

[t0dd]

@personalizedrefriger

An alternative that doesn't rely on title

Perfect! I will update my examples as well.

[banan314]

@adrianolszewski

Settings -> General -> Advanced ->
Use the legacy Markdown editor

@adrianolszewski you don't have to use the legacy editor anymore, the overwrite is already working in the newest version (at least in 3.2.1)

[t0dd]

@banan314

the overwrite is already working in the newest version (at least in 3.2.1)

It should be noted that 3.2.1 is a beta. The newest versus is 3.1.24.