melquibrito / source-code-editor-tinymce-plugin Goto Github PK

If you use the TinyMCE codesample plug-in alongside ace editor plug-in. Viewing the source code of HTML document with codesample inserted. When you save the HTML source from ace the code sample tags are reformatted.
Is there anyway resolve this ?

codesample before save

`

View example's code

  

after save

<pre class="language-markup"><code></code></pre> <div class="card-footer position-relative"><a class="collapse-link collapsed stretched-link" data-bs-toggle="collapse" href="#collapse-2">View example's code</a></div> <pre class="language-markup"><code></code></pre>

I have a page with 2 tinymce editors on it. And just installed your code editor plugin (which is very nice, BTW). If I try to use the code editor plugin on the first editor, when I click Save, it overwrites the contents of the second editor with the value instead of updating the first. It appears that tinymce.activeEditor is not always returning the editor that the plugin was called from. I hacked around it by passing the editor variable to displayToxEditorModal and setting the id of the editor as a data attribute on the modal, which I then read back in saveContent()... But I'm sure there's probably a cleaner way to do it.

function displayToxEditorModal(e, display = true) {
  let el = document.getElementById('tox-codeeditor-wrap');
  if (display) {
    el.dataset.editor = e.id;
    el.style.display = "flex";
    el.focus();
    document.body.classList.add('tox-codeeditor__disable-scroll');
  } else {
    e = e || tinymce.get(el.dataset.editor);
    el.style.display = "none";
    document.body.classList.remove('tox-codeeditor__disable-scroll');
    e.focus();
  }
}

function saveContent() {
  let el = document.getElementById('tox-codeeditor-wrap');
  let e = tinymce.get(el.dataset.editor);
  e.focus();
  e.undoManager.transact(function() {
    e.setContent(aceEditor.getValue())
  });
  e.selection.setCursorLocation();
  e.nodeChanged();
  displayToxEditorModal(e,false);
}

If you re-arrange the themes so that Twilight is not first, the selector will have the first theme selected, but it always applies the Twilight theme, regardless.

Workaround for me was:

aceEditor.setTheme("ace/theme/"+themesPack[0]);

Hello thank you for this plugin. Makes editing the source to easier. By default plugin seems to be reverting to the Spanish language when it should be English ?
Regards
Paul