Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I have CKEditor 3.1 and the icon displayed for the teaser break plug in is a default icon - if I look at the code in Firebug it's displaying the regular icon image with no offset. Looking at the html in firebug there is no background image set in the inline style for the button (which is where I would expect it having looked at the CKEDITOR.ui.button.prototype function in the api docs).
Anyway - I'm very stuck and have looked at this quite a while. Probably a silly mistake on my behalf, but I can't find it...
Comments
Comment #1
gaellafond CreditAttribution: gaellafond commentedI have the Teaser button working on Article Body field. I'm trying to activate it on a custom Textarea field that I made for a custom node type. Unfortunately, it's seem to work only for Body. I can NOT find a way to activate the Teaser feature on a different field.
On which field are you trying to add the teaser button? Is it on the Body or some other field?
Did you find any solution yet?
[edit]
I decide to use the body field for my custom Textarea field and I migrate the data to that new field with a SQL query. Now, I have the teaser button working for that new Body field. Since we can NOT have more than one teaser per node (I'm not 100% sure of that actually), I think it is logical to have the teaser working only on the Body.
This is probably totally not related to your problem, but I found this interface to select what fields are used for the Teaser:
Ensure the column Teaser is not set to Hidden and the Exclude is not checked for the fields you want to see on the Teaser.
[/edit]
Comment #2
richardtmorgan CreditAttribution: richardtmorgan commentedI've got the teaser break on the body field. The break works, but the icon doesn't show - I get a default icon instead.
Comment #3
dczepierga CreditAttribution: dczepierga commentedUpdate your CKEditor module (to last DEV version) and plugin to 3.4 version. It was fixed earlier.
Comment #4
dczepierga CreditAttribution: dczepierga commented