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 inspect the value of $in you should get something like: Array ( [mode] => exact [width] => 100% [theme] => advanced [skin] => wp_theme [language] => en [theme_advanced_toolbar_location] => top [theme_advanced_toolbar_align] => left [theme_advanced_statusbar_location] => bottom [theme_advanced_resizing] => 1 [theme_advanced_resize_horizontal] => [dialog_type] => modal [formats] => { alignleft : [ {selector : ‘p,h1,h2,h3,h4,h5,h6,td,th,div,ul,ol,li’, … Read more
You would need to place a globally namespaced javascript variable in your php code where you enqueue the script to be loaded for the editor pages. So, this code will enqueue a script function to be added to the “edit post/page” screens: add_action(‘admin_head’,’my_add_styles_admin’); function my_add_styles_admin() { global $current_screen; $type = $current_screen->post_type; if (is_admin() && $type … Read more
I believe that you have already registered your shortcode. Now what we need to do is to initiate the Button. Once the shortcode is registered [ph_min] let’s check if user can use rich editing: function add_highlight_button() { if ( ! current_user_can(‘edit_posts’) && ! current_user_can(‘edit_pages’) ) return; if ( get_user_option(‘rich_editing’) == ‘true’) { add_filter(‘mce_external_plugins’, ‘add_tcustom_tinymce_plugin’); add_filter(‘mce_buttons’, … 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
Here is an example of How to Update kses and TinyMCE to allow select data-* attributes in WordPress. Reference add_action( ‘after_setup_theme’, ‘x_kses_allow_data_attributes_on_links’ ); function x_kses_allow_data_attributes_on_links() { global $allowedposttags; $tags = array( ‘a’ ); $new_attributes = array( ‘data-foo’ => array(), ‘data-bar’ => array(), ); foreach ( $tags as $tag ) { if ( isset( $allowedposttags[ $tag … Read more
I came across this page — http://wp-snippets.com/set-default-editor/ * — which looks promising, though a little out of date. Instead of their code, I would suggest trying this: add_filter( ‘wp_default_editor’, ‘wpse101200_default_editor’ ); function wpse101200_default_editor( $editor ) { return ‘tinymce’; } Reference WPSeek’s wp_default_editor() page wp_default_editor() in the WordPress core source Unfortunately, the Codex doesn’t currently have … Read more
Problem was the page encoding. The wordpress database is UTF-8, i had switched the default to ISO-[something] to match the database we’re using to populate additional content and had not noticed any issue for over a month- until we started populating the blogs section of this page. We discovered the problem by following the code … Read more
Gutenbergs FreeformEdit Component (used for the classic editor block) demonstrates the way how to integrate a tinyMce editor. Recoded my custom Backform WysiwygControl and adopted the tinyMce integration. /** * External dependencies */ import Backform from ‘Backform’; /** * WordPress dependencies */ const { __ } = wp.i18n; const { F10, ESCAPE, ALT } = … Read more
They have actually fixed it so you can just add the shortcode within the paragraph content and it works. As simple as …However, when [expand tag=”span” title=”this trigger” targtag=”span”]hidden content[/expand] is clicked… That would be the contents of a paragraph block with inline shortcode. See this for more information.