This is a followup from #894120: CKeditor deleting / not saving content when combined with WYSIWYG-module and an attempt at making the process of dealing with conflicting editor modules less aggressive.
The current method (disable known conflicting modules when Wysiwyg is enabled), was called stupid by Diogenes in #888950-23: Configuring ckeditor, WYSIWYG, IMCE modules and CKEditor & CKFinder libraries - a tutorial, so let's see what we can do about that.
I can't update the project page but I've made a simple patch which just shows and logs a message when known conflicting modules are detected.
Basically, you're now allowed to keep other editor modules enabled, but you are on your own in trying to use them with Wysiwyg.
I'll update http://drupal.org/node/358296 with the new text from the readme file when this is done.
Comment | File | Size | Author |
---|---|---|---|
wysiwyg-warning-conflicts.patch | 2.27 KB | TwoD |
Comments
Comment #1
TwoDSimplified title.
This issue is s mainly about the documentation since the code in hook_enable() runs very rarely and Wysiwyg's installation instructions do not mention installing other modules. Looks like we're going to have to tell them what not to do as well.
Comment #2
sunAn alternative would be to use hook_requirements() to throw a REQUIREMENTS_ERROR if one of the other modules is enabled (which effectively prevents someone from installing wysiwyg module).
Comment #3
sunx-post
Comment #4
TwoDWe could do that, but what if someone does want to use Wysiwyg module with TinyMCE as well as the standalone CKEditor module?
I'd not like to officially support that situation, but as long as they know what they are doing, it might be possible.
Comment #5
steinmb CreditAttribution: steinmb as a volunteer and at University Of Bergen commentedOld one [#358296] contains some documentation though I not sure how up to date it currently is and if still useful, perhaps it should be migrated to the new doc. system on ddo - https://www.drupal.org/drupalorg/docs/content/documentation#contrib