It turns out that TinyMCE has it’s own autop setting, so if you kill it before the sort and then put it back you should be good to go! Check out the autop setting handling in this snippet: <script> (function($) { // by default, wpautop will be true var wpautop = true; // this function … Read more
Finally I got around this. You need to modify tinymce args passed to wp_editor function. WordPress have a argument wp_autoresize_on to allow the editor to be resized automatically. So instead of these: ‘tinymce’ => array( ‘toolbar1’=> ‘bold,italic,underline,link,unlink,forecolor’, ‘toolbar2’ => ”, ‘toolbar3’ => ” ) you need to use this: ‘tinymce’ => array( ‘autoresize_min_height’ => 100, … Read more
In theme options, I had to define wp_editor_settings. So, just in options.php, I used: //WP_editor settigs $wp_editor_settings = array( ‘wpautop’ => true, // Default ‘textarea_rows’ => 15, ‘tinymce’ => array( ‘plugins’ => ‘fullscreen,wordpress,wplink, textcolor’ )); Basically, I’m adding tinymce plugin.
Yes as per @Nibbr Web Development, TinyMCE editor IDs cannot have brackets. Which is the html field ID, so what we will do is create a different but similiar name for the ID attribute and still use our desired name in for the text area field name, like so. $content = $options[‘textareafield’]; // editor_id cannot … Read more
Without an explicit example I can only guess that if inserting <br> is good enough for you then you can get the same effect by adding a class to the paragraph that is created by default to remove any margins and paddings from it. This of course is not a good semantic solution but I … Read more
I’m not good with English, but the answer is that the editor class calls the scripts needed in the admin footer (wp-includes/class-wp-editor.php line 160) : add_action( ‘admin_print_footer_scripts’, array( __CLASS__, ‘editor_js’), 50 ); add_action( ‘admin_footer’, array( __CLASS__, ‘enqueue_scripts’), 1 ); So when you call the wp_editor function in your ajax, the scripts aren’t printed with it, … Read more
you’ve got a lot of options. some of which are: to toot my own horn, i have used WP Alchemy to create repeating sortable tinyMCE editors with all the code available here http://www.kathyisawesome.com/426/multiple-wordpress-wysiwyg-visual-editors/ there is also the http://www.advancedcustomfields.com/ plugin. you can definitely have multiple instances, but you can’t add dynamic blocks on the fly.
You need to first define the $settings and the $editor_id and the $content variables. Then you can call wp_editor(). Something like this should work for you: // default settings $content=”This content gets loaded first.”; $editor_id = ‘my_frontend_editor’; $settings = array( ‘wpautop’ => true, // use wpautop? ‘media_buttons’ => true, // show insert/upload button(s) ‘textarea_name’ => … Read more
Make sure tinymce option has a valid value. Remove it or set it to true if you don’t pass any parameters to tinymce $editor_config = array( ‘teeny’=>true, ‘textarea_rows’=>10, ‘editor_class’=>’csec_text’, ‘textarea_name’=>’csec_body’, ‘wpautop’=>false, ‘tinymce’=>$tinymce_options //THIS OPTION SHOULD BE VALID ); Edit: Made a small research. Add wpview in plugins argument of tinymce options. $tinymce_options = array( ‘plugins’ … Read more
That can be achieved with the hooks edit_form_after_title and edit_form_after_editor and proceed like a meta box. I noticed a “glitch”, though, if you swap Visual/Html in the custom wp_editors and then publish/refresh the page, their state will be the same as the main editor (the post content). Adjust the post type, page in this example. … Read more