Wysiwyg
This is the working group to discuss and coordinate the integration of client-side editors in Drupal core.
Developers and maintainers of client-side editors (aka. WYSIWYG) integration modules and other interested people are invited to join in and share their ideas and participate in the current efforts to build a Wysiwyg API that seamlessly integrates with Drupal core.
More information on the current status of the module can be found on the Wysiwyg API project page.
Live discussions on Wysiwyg API development and support happen in #drupal-wysiwyg.
The current status, progress, and roadmap of all efforts are summarized on a special page:
WYSIWYG image solutions
After a long while of messing with different WYSIWYG editors I've come to the conclusion that pretty much everyone seems to come to : use either FCKEditor or TinyMCE.
However, I still don't have a standard solution for providing image uploading capabilities in these editors. What is everyone else using? IMCE and IMCE WYSIWYG Bridge? What other solutions are available? Anything a bit slicker than the multiple clicks needed with these (very useful) modules?
Detect changes in Wysiwyg textares/iframe inside form
I'm trying to check forms for changes. In IRC #jquery the idea came up to use serialize() a form on .ready and compare serialize() it at a certain point to detect changes...
As soon as a wysiwyg editor (fckeditor in our case) is present, changes won't be tracked in that field. It shows that editor content is no more part of the form DOM.
I'm strongly looking for documentation about how to talk to wysiwyg api to check for changes in the editor. I didn't find the correct way to identify the wysiwyg editor instance, given the form element.
Google Closure
Today Google announced general availability of it's set of javascript tools called Closure. The set includes a Javascript compiler, library and template engine. In the javascript library they include an api for using their text editor. This is the same text editor used in many of Google's web applications like Google Docs, Google Wave, and Gmail... apparently.
Testing the editors
I created a test book in D6 for FCKeditor, NicEdit, TinyMCE, Whizzywig, YUI, jWYSIWYG, and markItUp (and now I see I need to do more, from this thread) for users to experiment with. Hope this is useful -- and doesn't duplicate the work of somebody I should have joined forces with!
Plans for determining which fields get editor
The biggest hindrance at the moment to adoption of WYSIWYG is that i don't think there is any current viable solution for controlling which fields get which editor instance assigned to them. I recall this being such a huge PITA back in 4.7 days and when D5 came along and FCK editor had a decent option for this it was all i needed to drop Tiny as my editor of choice and go with FCK.
But now we are at D6 and, if getting on the wysiwyg bandwagon, are taking a step backward to 4.7 days. I don't see much discussion about this on the forum; so thought it needed to be brought up.
Elaborating markItUp options
I am adding the structure necessary to make use of more HTML elements than provided by default for markitup in WYSIWYG API 2.0
This is fairly easy and repetitive but I am coming up against a small problem. I'd like block elements to end with a newline at the end of the closing tags and some block elements could use a newline after the opening element too. I tried shoehorning a \n in but that is just outputting \n.
In any case, I am happy to submit the expanded options for markup, H3-h6, p, dl, dt, dd, ul, li, ol as well as any others people call for.
Installation problem in 7.x
I've just downloaded the latest version on Drupal 7.x and the Wysiwyg module for 7.x. Installing the module and visiting
Home › Administer › Configuration and modules › Content authoring
give this error :
Notice: Undefined offset: 0 in wysiwyg_profile_overview() (line 382 of /drupal7/sites/all/modules/wysiwyg/wysiwyg.admin.inc).
Does that mean Wysiwyg is not yet ready for Drupal 7 ?
Can anyone help fit Autosave into WYSIWYG?
Hey gang,
I am (more or less) the maintainer of the Autosave module. I think this is pretty important module for anyone using Drupal for any sort of web based publishing system. Surprised not more people stressing that i haven't ported to Drupal 6 yet.
[FYI - Autosave saves your node edit form in the background in case your browser dies you don't lose your work. When you return to edit; if there was a saved copy it will ask if you want to use that or keep the last submitted copy]
CKEditor module launched!
To satisfy the urgent need of having CKEditor into Drupal, we've just launched the CKEditor module. This is supposed to be the immediate upgrade solution for FCKeditor module users, a well as the current best option for those willing to have this editor into their Drupal sites.
Wysiwyg cleaner : a module to create custom content cleaning buttons for the Wysiwyg module
Using the Wysiwyg cleaner module, you can create content cleaning buttons for Wysiwyg editors using jQuery / Regular expressions rules. It uses the Wysiwyg plugin API. Visit the project page for more information.
I thought the group might want to know about it ;)
Role-based profiles as in TinyMCE Module
TinyMCE Profiles (which allow to configure different user profiles based on the roles) are not accessible from WYSIWYG module. Instead, WYSIWYG module provides its own profiles that are related to Input Formats.
The problem that I have appears with Input Formats permissions when trying to access the node from role which is not allowed in the Input Format. Here is the example.
(Role – Input Filter)
Editor – Simple TinyMCE (less buttons)
Moderator – Advanced TinyMCE (more buttons)
Can w-api manage editor's detailed settings?
I am just starting to familiarize myself with w-api's way of doing things and i like it's approach of piggy-backing on to input formats.
I get that the idea of w-api is to prevent developers from duplicating each feature in an editor specific module; but am wondering if it has got up to the existing modules as far as feature support.
Back in Dr5 days we required the need to assert specific Tiny "themes" to specific fields. Please keep in mind that a Tiny theme is NOT css but is a configuration definition for Tiny which includes more than just which plugins are enabled.
The version of TinyMCE could not be detected.
I have installed Wysiwyg and tried both the TinyMCE and FCKEditor as editor libraires but the error messages I get are:
"The version of TinyMCE could not be detected" & "The version of FCKeditor could not be detected."
Any ideas?
I have tried reinstalling Wysiwyg but no luck.
What does Wysiwyg module do for me?
Hey, sorry if there is a post somewhere that describers this but i couldn't see it (likely should be on project page??).
What is the value that the wysiwyg module provides for us over a solution like the fck module paired with fck?
We have a large publishing system that currently uses the combination of Dr5, TinyMCE module and TinyMCE. We are beginning work to convert this system of around 160 modules over to Dr6 and i have come across the dilemma that the TinyMCE module has been deprecated and we are trying to sort out which way to go as far as a WYSIWYG editor.
Drupal 7 Status
Hi All -
I spent the last hour researching WYSIWYG API for Drupal7 and my head is spinning with both joy and pain. What is the current status, and how can I help out? (other than donating, which I already did). Will D7 support either TinyMCE or FCKEditor when it's released?
Tiny MCE not using theme CSS even though it's set to
I'm using Drupal 6.13 with the WYSIWIG module and tinyMCE.
I have used WYSIWIG module's profile>configure dialogue to set tinyMCE to "Use theme CSS". When inputting data using tinyMCE, the style is not the site's themed style, however the resulting node displays to the correct css. Is this the way it is supposed to work or should the text I'm typing into the editor be using the site's theme css as I type?
I posted this question in the forums and it got buried with no responses. Thanks for any help with this!
Weird behaviors with teaser break code inserted by TinyMCE
I posted this in the forums but it was buried with no response, so I'm hoping to find some answers here.
I'm using Drupal 6.13, and have installed TinyMCE using the WYSIWIG module. Everything works great with the editor, but I'm confused about some issues I'm having with the teaser breaks:
FCK editor is now CK editor...
Greetings! I'm a new installer/user of WYSIWYG and absolutely loving it.
It looks like the WYSIWYG install panel could be updated to look for the ckeditor library folder and ckeditor.js for the new version. Must be something to do the name looking too much like a swear word? ;)
Can not change editor at /admin/settings/wysiwyg
at the wysisyg configuration page (/admin/settings/wysiwyg) I have 2 profiles associated with 2 different editors, like this:
Filtered HTML FCKeditor Change Delete
Full HTML TinyMCE Change Delete
Both editors work as expected when processing content.
fckEDITOR WITH wyswig only working for administrator role
Hi All,
I am a newbee and installed wysiwig along with FckEditor, and made FckEditor default for all the filters. How ever when I go to the create content page of any node, The Editor appears in case of administrator, where as for any other authenticated users the editor doesn't show up.
Please provide me with a solution as it is a very time critical application.
Drupal 6.13
PHP 5.2.9
MySQL database 5.0.81
Wysiwyg 6.x-2.0
FckEditor
This is the working group to discuss and coordinate the integration of client-side editors in Drupal core.
Developers and maintainers of client-side editors (aka. WYSIWYG) integration modules and other interested people are invited to join in and share their ideas and participate in the current efforts to build a Wysiwyg API that seamlessly integrates with Drupal core.
More information on the current status of the module can be found on the Wysiwyg API project page.
Live discussions on Wysiwyg API development and support happen in #drupal-wysiwyg.
The current status, progress, and roadmap of all efforts are summarized on a special page:






