contemplate.module requires fckeditor to me shut off so that the fields can be populated properly.

contemplate has two text areas edit-body and edit-teaser. if i exclude fckeditor from edit-body, its removed from every edit body.

what to do so that fckeditor and contemplate can be used in harmony ?

Comments

vm’s picture

After closer inspection I see where there isnt much that can be done about this issue.

How about a fckeditor toggle, like that of tinymce so that it can be shut off on the fly for offending fields where it can't be used, while not removing it from all fields of the same name?

ontwerpwerk’s picture

It's an intriguing idea, I will try to implement it sometime. I hope it's possible with the way the FCKeditor works.
At the moment it is the other way around though, you can use the FCKeditor as a popup.

ontwerpwerk’s picture

Title: Not completely compatible with contemplate.module » On the fly enabling and disabling for fckeditor
Category: bug » feature
Status: Active » Postponed

more accurate title and category

--

the idea is to change the way fckeditor is enabled by a link next to the textarea similar to tinymce

first: check if fckeditor might be loaded dynamically
at the moment that looks a little bit complicated, and other things like teaser breaks and image- and filemangement are more important

denney’s picture

Any updates on this?

Subscribing to issue.

heimstein’s picture

Version: 4.7.x-1.1 » 5.x-1.1

her is a dirty solution for making FCKeditor peacefully co-exist with the contemplate-module
(to great modules, which HAVE TO WORK TOGETHER!)

find in fckeditor.module approx line 205:

function fckeditor_process_textarea($element) {
  $exclude = preg_split("/[\s,]+/", strip_tags(variable_get("fckeditor_exclude", '')));

  if (($element['#rows'] > variable_get('fckeditor_minimum_rows', 5))
                  && !fckeditor_idsearch($element['#id'], $exclude)) {
    // only replace textarea when it has enough rows and it is not in the exclusion list

and replace this by

function fckeditor_process_textarea($element) {
  $exclude = preg_split("/[\s,]+/", strip_tags(variable_get("fckeditor_exclude", '')));
  if (($element['#rows'] > variable_get('fckeditor_minimum_rows', 5))
    && !fckeditor_idsearch($element['#id'], $exclude)
    && !(
           $element['#title']=='Teaser Template'
        || $element['#title']=='Body Template'
        || $element['#title']=='RSS Template'
    )              
  ) {
    // only replace textarea when it has enough rows and it is not in the exclusion list

if you used translation, you have to adjust this to match the titles, of course

thanks all for FCKeditor and contemplate!

jasonwhat’s picture

One option might be to be able to set the path where fckeditor is exluded. If fckeditor is enabled I can't use contemplate's admin interface, so I have to disable it. I'm also seeing the same problem with the views modules text fields. A simple solution would be a setting that let's you specify paths to exclude fckeditor such as "admin*" so it doesn't show on any admin pages. It would be great to extend this feature to exclude text fields by cck rendered id as well.

ontwerpwerk’s picture

jasonwhat: the option to exclue paths exists in the latest develoment version of the module... please test that first

Duplika’s picture

Version: 5.x-1.1 » 5.x-1.2

Am I wrong or you can only specify which URL's to display FCKeditor? Because it would be awesome to specify where to disallow it instead of where to allow it.

wwalc’s picture

Status: Postponed » Fixed

It is now possible to use toggle to turn on/off FCKEditor on the fly (+ I have added a couple of other new options).
Please check fckeditor 5.x-2.x-dev release.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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

SamRose’s picture

(sub)