TinyMCE

The Wysiwyg API is supposed to be a supermodule to replace the various WYSIWYG and non-WYSIWYG individual textarea enhancement modules such as FCKeditor, TinyMCE (whose module development has been halted in favor of Wysiwyg API), markItUp! (of which I am now the unworthy primary contributor), etc.

I feel like I'm missing something obvious but how do you get the TinyMCE break plugin to work in the WYSIWYG api?

With the full TinyMCE module you had to edit a PHP file and add a couple lines as well as copy the break folder into the plugins folder of TinyMCE. I see that there is a break folder under WYSIWYG so I copied it into the tinymce plugins folder.

I can see it as an option when I edit the permission of the filter type and I have checked it's box. However it never shows up on the editor.

What am I doing wrong?

Hi all,

I hope this is a good place to talk about this subject.

WYSIWYG editors such as TinyMCE are great, but when it comes to provide a secure method to filter what such a tool allows to users, I have the feeling that Drupal core filters do not help much.

If we use Full HTML, then we can do anything with our great WYSIWYG editor, however this is no no solution if we need to allow WYSIWYG capabilities to users we cannot trust. So, Full HTML filter might only be a valid solution for personal sites, or sites where all contributors can be trusted 100%.

I took the time to rewrite the Wysiwyg (Editor) module into a generic API over the weekend. So the primary concerns about TinyMCE-specific code all over the module are eliminated now. Also, you might have noticed, that I have added an example integration for FCKeditor already - which of course is rather a proof of concept than a fully-fledged integration (and it works cleanly 8).

So Wysiwyg has become a real API finally.

I have spent the last hours to get a first draft of FCKeditor support in Wysiwyg Editor module.
http://drupal.org/node/282717

It's still very rough and dirty, but it outlines what can be done and what needs to be done for multiple editor support in Drupal via one API module.

Now I badly need some feedback from folks that are interested in centralized Wysiwyg editor support, who know jQuery + JavaScript, and who might have ideas and suggestions on how to solve the outlined design challenges. Of course, all editor module maintainers are implicitly more than welcome.

Greetings everyone! I'm throwing in my hat for participation in the WYSIWYG discussion.

As we've noted in previous discussions, we currently have a serious problem with WYSIWYG editors not being Input Format aware. In D7 we'll get a nice luxury of #input_format (sounds awesome Gabór!), and we'll easily be able to combine the two into a single, well themed element. I've rigged up a temporary solution for D6 that I've posted to the the WYSIWYG project issue queue (patch forthcoming).

Here's a graffle of how I imagine the Input Format system working with the WYSIWYG framework.

Note: this is totally a mockup it is not a new WYSIWYG editor of any sort.

I found this screencast a great help when I was trying to configure TinyMCE on my site...

http://www.usingdrupal.com/node/11

Be warned that part of the cast won't work in 5.6 because of a bug within the core filter module so you'll need to upgrade to 5.7

Keith

The TinyMCE Defaults module: set up TinyMCE, along with secure input formats, with a mouse click.

Please give feedback on the issue: http://drupal.org/node/202062

@addisun/webchick/other GHOP admins: should I copy the task description over to the GHOP issue queue at http://code.google.com/p/google-highly-open-participation-drupal/issues/... ?

I'm "hosting" the weekly Dojo screencast this week. I will be demo'ing the TinyMCE WYSIWYG toolbar. I will be covering the installation process, the new features available in Drupal 5, and answering as many questions as time allows. I will talk a little bit about the dark days of TinyMCE and how I ended up as the maintainer, but I want to spend more time discussing what direction users what TinyMCE to go. What are the biggest problems that still need to be solved.

Anyone who has been following the TinyMCE saga knows that the module has emerged from its dark days and is once again stable with all the 4.7 features included. The Moxicode 2.1 release solved several issues for Drupal users. Nedjo banged out some great patches to re-restore customizations to TinyMCE beyond what the GUI button picker allows, but it looks like the only way to get the form based customizations (vs. modifying the actual .js theme files) to work with modules that enable additional textareas like Nodeteaser is to use JQuery... which many developers prefer anyway.