Better integration with Drupal's text formats and filters [#1040236]

I used tinymce under wysiwyg module for long, but after a quick try to bueditor convinced me that this is the best editor outta there for drupal.

The only issue i have with it is that is not possible to associate an editor to a specific input filter, but just to user roles and restrict visibility via url wildcards.

Comments

Comment #1

LarsKramer commented 31 July 2011 at 17:47

Title:	Add per input-filter selection	» Better integration with Drupal's text formats and filters
Version:	7.x-1.0	» 7.x-1.x-dev

If I have two text formats enabled (for example Filtered HTML and Textile), I can set up an editor for each of them, but on the node edit form only one of these editors can be used (the one assigned as default to my role). This is a problem because with Textile I need the "B"-button to insert *%TEXT%* and with Filtered HTML I need it to insert <strong>%TEXT%</strong>.

In practice, this means that I am forced to decide on only one text format for my users if I also want to use BUEditor (or at least the text formats should use the same tags and filters).

It would make more sense to assign a default editor to each text format, and when the user changes text format on the node edit form, the editor also changes (or disaapears if no editor has been assigned to that format). What do you think of this, and would it be possible to implement?

Comment #2

ufku commented 3 August 2011 at 05:07

It sure is possible but i'm not very into implementing it as i want the editor stay as simple as possible. Still, i can review patches that do not introduce much complexity.

Comment #3

LarsKramer commented 3 August 2011 at 22:10

Hi ufku, thanks for being open about this. I'll not go into it either at the moment but may get back later with some ideas for implementation. So you might want to change status to postponed.

Comment #4

Jamie Holly commented 23 September 2011 at 00:56

I just released a module on GitHub today that does just this. It overrides the default per role settings and instead you create "profiles". You then assign the profiles to individual fields (you can even set a global profile). On top of that it sets editors per input format and if you change the input format while working on a post, it will change the editor to the one assigned to that profile.

It was all done with hooks, so no modifications to the core BUEditor had to take place.

I got it listed as being in beta right now. I've been using the same basic principal on Drupal 6 on crooksandliars.com for 3 years now without any problems. I just updated it and made it work with fields, which is a lot better than how I had to do it on Drupal 6.

https://github.com/HollyIT/bueditor_plus