Wysiwyg

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!

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.

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]

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 ;)

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.

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.

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!

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? ;)

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