When I was working on my own module, I was trying to figure out why the WYSIWYG module didn't work for my form. After spending some time, I thought the WYSIWYG module was at fault. I found a way to "fix" it, which I described at the page linked below, but it may have been simply the way I was using filter_form(), which the module's author politely helped me to correct.

http://drupal.org/node/357080

After this incident, the author also wrote a page in the handbook on how to use filter_form(), linked below:

http://drupal.org/node/358296

I realised the views_ui.module may be having the same problem. I wasn't able to get the WYSIWYG form to show up in the view edit forms, but after modifying the code a bit, the same way I did for my module, I was able to make WYSIWYG form work with views_ui.module.

I attached a patch of my modifications. It is working for me and it is saving the values properly like it was before, but your mileage may vary.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sun’s picture

Category: feature » task
Status: Needs review » Reviewed & tested by the community

The actual developer handbook page for this is: http://drupal.org/node/358316

Putting this into my list of issues.

If you could eliminate the malformed spacing in some of the arguments you altered, that would be great. :)

remi’s picture

Thanks for the correction!

I'm attaching a new patch file. It's the same one than before, except it also eliminated malformed spacing.

sun’s picture

Status: Reviewed & tested by the community » Fixed

Thanks! Committed.

Good job.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.