Hey there, toolset does use for the wysiwyg fields the native tinymce version. But i want to use the neweset version of tinymce 5 or even a different editor like quill editor.
Could you help me not to use the native wordpress tinymce version for the wysiwyg toolset fields?
Hello. Thank you for contacting the Toolset support.
There is no workaround I can offer to update the tinymce version within our core plugins. Additionally, we do not recommend users to modify anything within our core plugins as there is the chance of having possible neative impact of those changes and plugin may break and not work as expected.
The only thing I can offer you is that you should file a feature request to update the TinyMCE version using the following link, that will allow you to raise your voice in front of our product manager and they can possibly review your request and if accepted they can prioritize accordingly.
=> https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/
this is very sad. Because there is no way i can extend or customize the tinymce editor even there are a lot of things you can do as you can read here: enlace oculto.
Maybe you can help to get a workaround here:
1. I implement the new tinymce editor 5 in a form as html with a textarea and the id. 'mytextarea'. Like in the documentation with javascript:
This works perfekt:
2. i have a toolset multiline-field with the name: 'textmirror' in that form which will be hidden in the front end.
3. Maybe i can pass the the raw html value of the tinymce 5 editor to that toolset multiline-field with jQuery and a change event?
.keyup should not work with this because you change the input with buttons in the toolbar.
there are events like change event which gets fired when the editor content changes have been commited, such as when moving focus away from the editor.
tinymce.init({
selector: 'mytextarea',
setup: function(editor) {
editor.on('change', function(e) {
//jQuery pass value of #mytextarea to toolset multiline-field with name: ''textmirror''
console.log('The Editor reacts on change');
});
}
});
So with that this must work to pass the value?
What do you think
1. Good that you able to make it work.
2. I'm afraid that I do not have any workaround to that and as I acknowledged before that even If I try to help and share some workaround there is high possibility that the custom code you added may get broken at any time.
I really wanted to help you but I've limitations as we do not entertain custom code and sharing such workaround is not recommended. Maybe you can try to implement it on your own or ask for experts help from our certified partners from who you can expect the pro help for such customizations:
=> https://toolset.com/contractors/
I just read your latest replay about the events but I could not guide you for the same reason I just shared above. The best thing to do is to check with our certified partners.