[D7] CKEditor Doesn't Load on 'Long Text' CCK Field [#1361846]

Hello,

This issue is very similar to this post, but those requests are geared to the 'text field' CCK type. I'm having a slightly different problem...

I have installed Drupal Commerce (using the manual install method)
I'm now working with the default 'Product" content type (at /admin/commerce/products/types)
Following these instructions, I've added a CCK field for "Long Text" to facilitate a product description
In the settings for my "Long Text" field, under 'Text processing' I have selected: Filtered text (user selects text format)

Given these settings, I'd expect when I go to create a new product, the rich-text editor would be available. Instead, it defaults to "Plain text" (a seemingly separate issue)...

But when I click "Full HTML", nothing happens (the same is also true when I select Filtered HTML).

This strikes me as a fairly large issue, because Drupal Commerce requires adding a CCK field for text descriptions (which most products will have). Not being able to use the CKEditor rich-text editor for these descriptions presents problems...

Thanks for any help on this!

- Jim

Comment	File	Size	Author
#3	ckeditor_fix_custom_fields-1361846-2.patch	571 bytes	mrsimonelliott
#3

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

mkesicki CreditAttribution: mkesicki commented 6 December 2011 at 09:45

Status:

Active

» Postponed

We try check this. Patch is nice welcome :)

Comment #2

mrsimonelliott CreditAttribution: mrsimonelliott commented 7 December 2011 at 17:09

Status:

Postponed

» Active

I confirm this behaviour.

On a custom text field on which a user can select from multiple text formats, the wysiwyg will *not* load on the edit/create if the text format was not set to a wysiwyg enabled text format when you opened the create/edit form.

You can partially get around this by adjusting the weights of your input formats here admin/config/content/formats. If you ensure a wysiwyg enabled input format is at the top of this list, then you won't have the problem on node create forms.

The problem will still exist if you are editing an existing node where fields have been saved in a text format that is not wysiwyg enabled.

Comment #3

mrsimonelliott CreditAttribution: mrsimonelliott commented 8 December 2011 at 13:38

Status:

Active

» Needs review

File	Size
ckeditor_fix_custom_fields-1361846-2.patch	571 bytes

I've had chance to look at the problem today and the wysiwyg is always available for "longtext & summary" fields but only available for "longtext" fields if the field has been previously saved in a wysiwyg format or on content creation, the filed defaults to a wysiwyg format.

See attached patch for proposed fix.

Comment #4

mkesicki CreditAttribution: mkesicki commented 9 December 2011 at 08:00

@mrsimonelliott thank you for your patch . We will check it. Please be patient.

Comment #5

jaymallison CreditAttribution: jaymallison commented 20 December 2011 at 08:37

Status:

Needs review

» Reviewed & tested by the community

Can confirm the patch in #3 fixed this pesky issue for me. Thanks for the patch!

Comment #6

mkesicki CreditAttribution: mkesicki commented 21 December 2011 at 07:58

@jaymallison
thank you for review

Comment #7

dczepierga CreditAttribution: dczepierga commented 9 January 2012 at 12:29

Title:	CKEditor Doesn't Load on 'Long Text' CCK Field	» [D7] CKEditor Doesn't Load on 'Long Text' CCK Field
Status:	Reviewed & tested by the community	» Fixed

Really thx for patch and review.

I commit patch to GIT (diff), so pls update to last DEV version.

Greetings