Installing the Lite plugin (track changes) on CKEditor/WYSIWYG

Try

            'buttons' => array(
              'accept_all' => t('Accept all changes'),
              'accept_one' => t('Accept one change'),
              'reject_all' => t('Reject all changes'),
              'reject_one' => t('Reject one changes'),
              'show_hide' => t('Show hide'),
              'track_changes_on_off' => t('Track changes on off'),
            ),

You'll need to switch them on at /admin/config/content/wysiwyg/profile/{profile}/edit - under buttons

I've updated the original post with the correct button names (this plugin made it unnecessarily difficult to figure out that part).

You will need to install jquery_update module and configure it to use at least jQuery 1.7 because it needs the jQuery.on() method not available in the version shipped with D7.

You will also need to fix the plugin itself, since there's a critical bug in its destroy event handler. The error thrown there will prevent Wysiwyg from detaching the editor correctly.
You can fix this by editing LITE's plugin.js on line 104.
Change

var ind = this._findPluginIndex(editor);

to

var ind = _findPluginIndex(editor);

Added bug note to original post.

Sounds like a great sandbox project!

I had to work on the same feature i posted the 1st version of the module on github

https://github.com/ibakayoko/ckeditor_track_changes

Lite plugin got a function setUserInfo i could not find where or how to call it to set the current user info. Any help will be appreciated this way we will not need to alter the lite plugin library.

Here is the module that actually works, either through WYSIWYG or CKEditor module - https://www.drupal.org/project/ckeditor_lite

AndyB

@ibakayoko, a quick tip: I would not create global values like that, there's a risk other modules expose a $settings variable which gets overwritten by your code. Calling drupal_add_js() there will also make Drupal add the script file as soon as the plugin file is loaded, regardless of the reason why it's being included (maybe someone just wants to check which plugins are available, like on the admin pages).
Move them inside the function and you'll be good for now (Btw, use at least a check_plain() for the username!).

However, Wysiwyg module will later cache the return value from that function to increase performance and not always have to load the plugin file. That means your drupal_add_js() line won't run when the plugin data is fetched from the cache. When that happens, you'll be able to include scripts via the metadata, and possibly define a "load callback" for adding dynamic content.
Keep eyes on #841794: Cache wysiwyg_load_includes() and #1039076: Allow plugins to specify libraries and multiple javascript files for more on that.
You could also do it like the ckeditor_lite module, mentioned above, does it. They implement hook_wysiwyg_editor_settings_alter() and inject the dynamic data that way. That completely avoids potential caching issues in the future.
(Adding "namespaced" plugin settings using the hook like this is a fine use case, but I would not recommend most modules to implement it for modifying any existing edit settings, as this is mostly for site-specific custom modules).

@duozersk, for your hook_wysiwyg_plugin() implementation you can skip the 'path' and 'file' keys and just set 'internal' => TRUE instead, since you're relying on the user to install the plugin into the CKEditor library's plugin folder. Then you could make the Libraries API dependency optional if you add a module_exists('libraries') check and fall back to a hardcoded path for hook_ckeditor_plugin().

TwoD,

Thank you for your time to review the code, really appreciate your efforts on developing and supporting the WYSIWYG module.
I also plan to implement the block to toggle the changes highlighting when you view the node with changes.

AndyB

Michael,

Sure, will wait for your review and suggestions/patches in the issue queue.

AndyB