Jump to content

How to add CKEditor plugins?


dragan
 Share

Recommended Posts

I wanted to install the CKEditor accessibility checker on one of my sites (latest PW 3 dev).

I downloaded the two required folders and put them in the correct folder

(as per the helptext To add more plugins, place them in /site/modules/InputfieldCKEditor/plugins/[name]/, replacing [name] with the name of the plugin.)

I checked those two plugins in the body field (which means PW recognises them) under edit field > input.

I even tried to put the plugins in wire/modules/Inputfield/InputfieldCKEditor/plugins - which of course is stupid, but hey... worth a try. And I made sure i hit "refresh modules" a couple of times as well...

Does anyone know why that new plugin still doesn't show up in my field?

Link to comment
Share on other sites

3 hours ago, dragan said:

Does anyone know why that new plugin still doesn't show up in my field?

Under Edit field > Input > CKEditor Settings > CKEditor toolbar, you need to add the button:  A11ychecker

Save, then you should see the new button ;)

  • Like 4
Link to comment
Share on other sites

  • 1 year later...

I've just added this plugin successfully: https://ckeditor.com/docs/ckeditor4/latest/guide/dev_colorbutton.html

Unfortunately it seems that the field's settings do not have any effect ? I tried several versions:

{"colorButton_colors": "FFB400", "colorButton_enableAutomatic": false}
{"config.colorButton_colors": "FFB400", "config.colorButton_enableAutomatic": false}
colorButton_colors: "FFB400"
config.colorButton_colors: "FFB400"

It still shows all the default options:

OrOnoL5.png

Can anybody help me, please?

Link to comment
Share on other sites

15 hours ago, bernhard said:

Can anybody help me, please?

This worked for me:

2018-11-07_124901.png.af33f2ef6088441df2d0505d5dee9d81.png

Alternatively this also worked, in /site/modules/InputfieldCKEditor/config.js:

CKEDITOR.editorConfig = function( config ) {
	config.colorButton_colors = 'CF5D4E,454545,FFF,CCC,DDD,CCEAEE,66AB16';
};

 

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

Thanks robin, using the config.js file it worked as expected. It still does not work using the inputfield settings... I used the exact same string that you have in your screenshot... No idea. But it's fine for me now that the workaround is in place.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...