Disabling the green highlighting is not possible right now, but I will add an issue and try to add this functionality. I might be able to optimize the visuals though — why exactly do you want to disable it?
I want to completely move away from modals for this rewrite. That’s why the page button is not yet implemented. I have a local proof-of-concept displaying the page list inside the toolbar. Keep an eye on this issue: https://github.com/medienbaecker/kirby-simplemde/issues/2
@texnixe I added an option to disable the Kirbytag highlighting: c::set('simplemde.kirbytagHighlighting', false);
@jenstornell Thank you! I hesitated at first because of Kirby 3 — maybe this field will not even be needed anymore. But I thought it would be a great project for my first Kirby 3 plugin. It’s very straight forward and not as bloated as the Enhanced Textarea.
As there is already a code function in SimpleMDE it was very easy. But adding more buttons is quite straight forward too. Just have a look at the existing button functions.
Therefore, editor.js is the file to work with whenever you want to extend the plugin with custom buttons? Cool. Will look at simplemd’s readme as well.
It works for me.
If it can’t find the translation.json on your installation, it probably won’t find the index.json for the page link search either.
Can you access the files directly?
The panel routes are defined in line 16 and line 33 of the simplemde.php and a data-json attribute with the url is added to the field.
Maybe there’s a better way of adding panel routes? I couldn’t find anything in the documentation about that.
Is there an known issue between this (awesome) plugin and the latest version (2.10) of Kirby? I have it running on several sites with version 2.8 without any issues, but just installed it on a site with 2.10, and it doesn’t seem to work at all - ie., none of the editor buttons show up…