The forum operates in read-only mode. Please head to StackOverflow for support.

Fri, 09/13/2013 - 10:51

Joined: 13/09/2013

Posts: 4

<SOLVED> Major problem with ACF

First off, I have read the documentation, but nothing there seems to help. I am using CKEditor with Drupal 7 via the http://drupal.org/project/ckeditor module.

I try to add the following to a document :

Or click <a class="btn btn-primary btn-small" role="button" href="contact-us" style="margin: 0 10px 0 10px;">Contact</a> to send us an email.

and the tag and the class that goes with it get stripped.

I have tried all of the following:

config.allowedContent = true;

config.allowedContent = 'true';

CKEDITOR.config.allowedContent = true;

CKEDITOR.config.allowedContent = 'true';

Each of the above in ckeditor/config.js and in the ckeditor.config.js supplied by the Drupal module. Both browser cache and Drupal cache have been flushed multiple times to no avail. I'm getting desperate now hence my post here as well as the Drupal module's issue queue as I'm getting no response from there.

What simple thing is it that I'm missing? Ideally I want to use config.extraAllowedContent to only let certain tags through.

Thanks

PS. If I simply save the document without switching from source mode to design mode, the tags are left alone, but this is not ideal behaviour.

Mon, 09/16/2013 - 10:56

reinmar

Joined: 24/08/2012

Posts: 631

Have you modified Drupal's

Have you modified Drupal's filters too? In Drupal 7 there's no automatic synchronization between filter. It will be added in Drupal 8.

Piotrek (Reinmar) Koszuliński
CKEditor JavaScript Developer
--
CKSource - http://cksource.com
--
Follow CKEditor on: Twitter | Facebook | Google+

Mon, 09/16/2013 - 14:19

(Reply to #2) #3

Sangahyando

Joined: 13/09/2013

Posts: 4

Hi and thanks for responding.

Hi and thanks for responding. Yes I have disabled all of Drupal's own content filtering.

Mon, 09/16/2013 - 14:34

reinmar

Joined: 24/08/2012

Posts: 631

Oups, sorry. I haven't

Oups, sorry. I haven't noticed that you meant that CKEditor removes empty inline elements. This is completely unrelated to ACF or Drupal's filter.

Anyway, there are at least 3 options how you can solve this problem. You can find short descriptions here: http://stackoverflow.com/questions/18250404/ckeditor-strips-i-tag

Piotrek (Reinmar) Koszuliński
CKEditor JavaScript Developer
--
CKSource - http://cksource.com
--
Follow CKEditor on: Twitter | Facebook | Google+

Mon, 09/16/2013 - 14:54

(Reply to #4) #5

Sangahyando

Joined: 13/09/2013

Posts: 4

Excellent, this did the trick

Excellent, this did the trick:

// ALLOW <i></i>
config.protectedSource.push( /<i[\s\S]*?\>/g ); //allows beginning <i> tag
config.protectedSource.push( /<\/i[\s\S]*?\>/g ); //allows ending </i> tag
// ALLOW <i></i> 
config.protectedSource.push( /<i[\s\S]*?\>/g ); //allows beginning <i> tag 
config.protectedSource.push( /<\/i[\s\S]*?\>/g ); //allows ending </i> tag

Thank you for the quick responses, I can see this information being useful in the future also.

// ALLOW <i></i>
config.protectedSource.push( /<i[\s\S]*?\>/g ); //allows beginning <i> tag
config.protectedSource.push( /<\/i[\s\S]*?\>/g ); //allows ending </i> tag

// ALLOW <i></i>
config.protectedSource.push( /<i[\s\S]*?\>/g ); //allows beginning <i> tag
config.protectedSource.push( /<\/i[\s\S]*?\>/g ); //allows ending </i> tag

// ALLOW <i></i>
config.protectedSource.push( /<i[\s\S]*?\>/g ); //allows beginning <i> tag
config.protectedSource.push( /<\/i[\s\S]*?\>/g ); //allows ending </i> tag

// ALLOW <i></i>
config.protectedSource.push( /<i[\s\S]*?\>/g ); //allows beginning <i> tag
config.protectedSource.push( /<\/i[\s\S]*?\>/g ); //allows ending </i> tag

Mon, 09/16/2013 - 14:55

(Reply to #5) #6

Sangahyando

Joined: 13/09/2013

Posts: 4

Not sure what happened there,

Not sure what happened there, pasting the code didn't appear to work the first few times, so sorry about the multiple copies.

Tue, 09/23/2014 - 20:43

publicradio

Joined: 23/09/2014

Posts: 9

Solution works, but not completely.

Hi, I was able to add the lines above to get i tags to work. I can also get aside tags to work this way. However, there are two problems:

I'm using HTML Buttons to input snippets of HTML, and after adding these lines, the editor will actually wrap p tags around the new opening and closing tags. so if my HTML snippet has an aside tag in it, the button will drop in

<aside>
content
</aside>
When I use a tag like aside, the rich text editor won't show this tag. Instead it will output something like this:



So users can't really preview how it should look.

Could someone help me resolve these issues? I am using Drupal and putting these lines in /sites/all/modules/ckeditor/ckeditor.config.js. Like the OP, putting any variation of config.allowedContent in this file changed nothing.

Wed, 09/24/2014 - 22:52

(Reply to #7) #8

publicradio

Joined: 23/09/2014

Posts: 9

1) is solved

I have this in my config file:

config.autoParagraph = false;

I don't know if this did it specifically, but I have noticed that my aside tags aren't getting wrapped anymore. Hopefully this will work for others.