Since there is no longer Include/Exclude fields in the CKEditor config, how do I turn off CKEditor on non-node textarea fields? Since the Taxonomy Term field is a core field, I cannot alter the input filter on that field. Is it still possible to exclude fields like this by default in CKEditor? :)

I know that I can simply click "Switch to plain text editor" or change the input format, but I'd rather turn off CKEditor by default for these "system" textarea fields, rather than having to disable it every time I add a new term.

Thanks everyone!

-Kevin

PS to pre-answer any recommendations on changing my workflow, I do not have an express reason to set the default input format as "Plain text" for all user roles, because I'd love to use CKEditor's new system of attaching to custom/body fields via the input filter. I just don't want this behavior to exist for system/config/admin fields that I cannot turn off by default. :)

Comments

kabojnk’s picture

Priority: Normal » Minor

By the way, I realize this is very nit-picky, so I set the priority to low.

hexabinaer’s picture

The issue title could be more general.

My team liked the option of including/excluding fields, too. Thus: subscribing.
Since we can only set custom fields to "plain text" resp. "let choose" I see many upcoming issues about either CKEditor throwing itself in where unwanted or users/editors complaining about the missing auto-load.

How about an "advanced options" override?

dczepierga’s picture

Status: Active » Fixed
StatusFileSize
new615 bytes

I make quick patch for you that disable CKEditor in Taxonomy module.
Asap it will be 2.x version of CKEditor module where we add include/exclude option...

For now i close this issue. If u had more questions pls reopen it.

Greetings

dczepierga’s picture

StatusFileSize
new615 bytes

I attach patch again because with # in the beginning not work :)

kabojnk’s picture

Thanks, can't wait to try it out!

Status: Fixed » Closed (fixed)

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

tangamampilia’s picture

Actually is still happening in the edit section. Here is the complete patch:

   if (arg(2) == 'taxonomy' || (arg(0) == 'taxonomy' && arg(3) == 'edit')) {
        return $element;
    }

Thanks.

azielinsky’s picture

What if i want the exact opposite thing? I really need Ckeditor whe the description term is being localized but not translated.

andrew_mallis’s picture

under /admin/config/content/formats you will see that input formats are re-orderable. The input format that sits at the top of this list is what sets the default on taxonomy term description fields. Of course, a user needs to have rights to that format.