I finally figured out what the issue was. Apparently, when you remove the textarea element from the DOM, you also need to remove the wp editor that has been attached to it. (if you decide to re-add the textarea to the DOM later) I found out that even though the textarea is successfully removed, its … Read more
If you wait for the SetupEditor event then you can access the editors: add_action( ‘admin_print_footer_scripts’, function () { ?> <script type=”text/javascript”> jQuery(function ($) { if (typeof tinymce !== ‘undefined’) { tinymce.on(‘SetupEditor’, function (editor) { if (editor.id === ‘contentLeft’) { // Could use new ‘input’ event instead. editor.on(‘change keyup paste’, function (event) { console.log(‘content=%s’, this.getContent()); }); … Read more
well, it turned out not to be an issue with tiny mce at all, rather php DOMdocument that was filtering tinyMCE’s output, interpreted in the wrong charset, then passing garbage characters to the page. Fun!
As mentioned in the comments, this is a lack of wp_autop() and other formatting functions that get applied to the the_content filter. The editor does not save <p> tags at all, but later on line-breaks are converted into paragraphs via wp_autop(). For meta content, I like to recreate the default filters. I do this because … Read more
I’ve fixed it by creating the following tiny plugin: <?php /* Plugin Name: Fix “Add Media” button in WordPress 4.5 Plugin URI: twitter.com/ojeffery Description: The 4.5 update of WordPress changed to the most recent version of JQuery, which broke the Add Media button when you call wp_editor via the front end. This tiny plugin fixes … Read more
As you noted, setting quicktags to false removes the “visual” and “text” tabs. So, to leave the tabs you need to set quicktags to true and remove the buttons: $settings = array( ‘quicktags’ => array( ‘buttons’ => ‘,’ ) ); wp_editor($input, ‘editor_name’, $settings); To have this in all quicktags instances you can use quicktags_settings filter: … Read more
If you are using WordPress 4.0+ you can do this using the wp_editor_settings and the global $pagenow to determine if you are on the comments page. add_filter( ‘wp_editor_settings’, ‘remove_editor_quicktags’, 10, 2 ); function remove_editor_quicktags( $settings, $id ){ global $pagenow; if ( $id == ‘content’ && $pagenow === ‘comment.php’ ){ $settings[‘quicktags’] = false; $settings[‘tinymce’] = true; … Read more
I was looking for a solution to place custom metabox above the default editor and i’ve found the solution to my old question (how to customize the default editor with the wp_editor)! The solution was to unset the default editor first. Then create another metabox to to place the content then use wp_editor to create … Read more
I copied your code into my functions.php, and added a simple admin panel (‘Foo’) to display the editor. Then I created a new directory inside my current theme for the editor button, and put the editor button JS into the relevant file: /wp-content/themes/[my-theme-dir]/tinymce_buttons/pH/editor_plugin.js. Result: when I went to Dashboard > Foo (the panel I’d created), … Read more
If you are using the settings API, you can use exactly the same code for calling wp_editor as you would anywhere else I’ve test the code below, it adds a setting section to the reading section, and then adds a field to the section containing a WYSIWYG editor with buttons limited to link, img and … Read more