Somewhere between RC3 and RC5, Panopoly made the decision to restrict panopoly_wysiwyg's custom functionality (plugins, skins etc.) to only work on Panopoly's native input formats, creating an inconsistent experience for users of sites with multiple, custom input formats.

It is my opinion that Panopoly should globalize their customizations for the sake of consistency and supporting Panopoly's goal of making Drupal universally better. However, if Panopoly chooses to restrict their improvements, the documentation should be updated to instruct users how to globalize these features themselves. Below is a rudimentary code sample that could be offered:

/**
 * Implemenets hook_wysiwyg_editor_settings_alter()
 */
function MYMODULE_wysiwyg_editor_settings_alter(&$settings, $context) {
  if (module_exists('panopoly_wysiwyg')) {
    switch ($context['editor']['name']) {
      case 'tinymce':
        // Define the skin to use
        $settings['skin'] = 'cirkuit';
        
        // Define the spellchecking settings
        $settings['spellchecker_languages'] = '+English=en';
        
        break;
    }
  }
}

Comments

kmonty’s picture

Issue summary: View changes

Improving the clarity of the function name.

dsnopek’s picture

Issue summary: View changes

Panopoly WYSIWYG now includes a panopoly_wysiwyg_alter_wysiwyg_editor_settings() function that you can use your own modules to use the same settings! This probably should be added to the documentation somewhere...k

delacosta456’s picture

hi @kmonty
thanks for this . however @dsnopek i couldn't find any doc about the function you mention. any help please ?