Support #wysiwyg FAPI attribute [#327184]

Problem/Motivation

Often contrib modules need a way to indicate a settings textarea should never be WYSIWYG or have HTML code at all. This is very difficult to accomplish with BUEditor.

Proposed resolution

The de facto solution, implemented by the WYSIWYG module, is to support a #wysiwyg attribute on FAPI elements. If a textarea has #wysiwyg set to FALSE, then all editors should be suppressed on that element.

API changes

A simple check for #wysiwyg attribute in the _bueditor_textarea() function can bypass the editor for a specific field.

Original report by thePanz

Hi, will BUEditor support upcoming FAPI #wysiwyg setting?
Regards

Comment	File	Size	Author
#8	wysiwyg-fapi-fix-327184-8.patch	558 bytes	jstoller
#2	bueditor-pre_D7_FAPI_wysiwyg_fix.patch	693 bytes	thePanz
#1	bueditor-pre_D7_FAPI_wysiwyg_fix.patch	691 bytes	thePanz

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

thePanz CreditAttribution: thePanz commented 2 December 2008 at 21:23

Component:	User interface	» Code
Status:	Active	» Reviewed & tested by the community

File	Size
bueditor-pre_D7_FAPI_wysiwyg_fix.patch	691 bytes

This patch implements this features...
I'm still asking myself if this module is still maintained anymore...

Comment #2

thePanz CreditAttribution: thePanz commented 5 March 2009 at 13:15

File	Size
bueditor-pre_D7_FAPI_wysiwyg_fix.patch	693 bytes

Re-Rolled against latest -dev (February) release.

Comment #3

ufku CreditAttribution: ufku commented 5 March 2009 at 17:00

Status:

Reviewed & tested by the community

» Closed (won't fix)

this won't go in because;
1- For 6.x there is no such api. It may be for 7.x
2- BUEditor is not a wysiwyg editor. There are usecases for plain-text fields where for example some characters not available on user's keyboard or some predefined phrases need to be inserted.

Comment #4

thePanz CreditAttribution: thePanz commented 4 April 2009 at 07:32

Status:

Closed (won't fix)

» Postponed

Hi, thank you for your reply.

1. I know that a some modules still use this feature in D6 (I don't remember if FCK or other editors still do that), so why don't do BUEditor?

2. You're right, so maybe BUEditor (for predefined phrases) will have to filter available buttons? I mean, inserting an IMG tag where the textarea is only for plain text isn't right..

Regards

Comment #5

Dave Reid

he/him

English

Nebraska USA

CreditAttribution: Dave Reid commented 16 February 2010 at 17:33

Issue tags:

+#wysiwyg

@ufku: I'd really like you to re-consider this. A *LOT* of contrib modules are already using this as an easy way to indicate a settings textarea should never be WYSIWYG or have HTML code at all.