Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.This is an amazing plugin, thanks for the great work.
The Save plugin is in my TinyMCE (version 3.x) plugins folder. How can I add the Save icon to the TinyMCE toolbar using WYSIWYG module? It's not listed under Buttons and Plugins. Our users find it crucial to have that button as they use the fullscreen toggle all the time and want to save from fullscreen mode without having to jump back into the Drupal screen to Save.
How to add this?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | wysiwyg-DRUPAL-6--2.save_.patch | 926 bytes | sun |
Comments
Comment #1
mecvo1984 CreditAttribution: mecvo1984 commentedI added the following code to tinymce.inc to get the Save choice to appear in the module. It appeared in the list and I checked it, but the Save icon never appeared in the toolbar. What else do I have to do to get the Save functionality in the toolbar in TinyMCE? I love this editor and want to use it, but no Save functionailty from the toolbar could be a dealbreaker. Thanks to anyone who can help.
'save' => array(
'path' => $editor['library path'] . '/plugins/save',
'extensions' => array('save' => t('Save')),
'url' => 'http://wiki.moxiecode.com/index.php/TinyMCE:Plugins/save',
'internal' => TRUE,
'load' => TRUE,
),
Comment #2
sunIt could be easy.
However, I'm getting JS errors in fullscreen mode when Drupal plugins are enabled. Secondly, when multiple editors are in the same form, one needs to click multiple times on the save button to trigger the save (the more clicks the more editor instances are on the page).
Comment #3
mecvo1984 CreditAttribution: mecvo1984 commentedI noticed the Save button option is also missing in FCKeditor when using WYSIWYG module, was wondering what was up with that as well.
Cheers and thanks for the patch. I just tried it and it's working well in both fullscreen mode and not. Will keep an eye out for the behavior you describe, but so far, no js errors.