I've been trying to add a CKEditor plugin (http://ckeditor.com/addon/strinsert) to the editor toolbar in Full HTML text format. The widget placeholder is present in the configuration page, but the widget itself is never rendered in CKEditor instances.

Steps to reproduce:
- Install module
- Go to admin/config/content/formats/manage/full_html
- Drag the "Insert snippet" combobox placeholder to anywhere in the toolbar
- Save configuration
- Go to node/add/page and select "Full HTML" text format

Expected behavior:
A select list with four options should appear in the toolbar

Actual behavior:
No select in toolbar. The library is loading (first console.log() is firing) but the init() method of CKEDITOR.ui.addRichCombo() does not run.

Am I missing some required files/steps to make this work?

UPDATE: Steps to reproduce issue have been updated to run the test in Full HTML mode per Wim Leers suggestion, to rule out ACF interference.

CommentFileSizeAuthor
plugin_test.tar_.gz1.69 KBkaldimar

Comments

kaldimar created an issue. See original summary.

wim leers’s picture

Can you add it to Full HTML and report back whether that works?

kaldimar’s picture

Same with Full HTML, so ACF is not to blame. Combobox placeholder shows up in configuration page but not in actual CKEditor instance, despite plugin code being loaded.
The symptoms look very similar to this issue, I wonder if the underlying cause is the same.

kaldimar’s picture

Issue summary: View changes
wim leers’s picture

Status: Active » Postponed (maintainer needs more info)

Agreed. Can you read the feedback in that issue, especially that of mlewand from the CKEditor team?

kaldimar’s picture

I don't think mlewand's comments apply here:

3. The toolbar element does not show up even for Full HTML (no ACF) nor even after setting the content to insert to <p> or other allowed tags, free of attributes.

4. .addButton() is not used by this plugin because it does not implement a button but a richcombo.

Something is missing on my plugin -or maybe beyond, I can't tell yet- preventing the richcombo to be rendered in the CKEditor toolbar. It'd be great if somebody has successfully implemented this and wants to share the code, or care to review the code attached to the first post.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

p.kasianov’s picture

Subscribe.

Hi, kaldimar.

Any news about your problem?
I got the same problem on D7, ckeditor 4.5.11 with my custom plugins that uses addRichCombo.

Update.
I was fixed it for D7 + ckeditor 4.5.11.
So, name of button (button from hook_ckeditor_plugin) and name of richcombo element from 'addRichCombo' should be the same.

I hope it help you.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

rulley’s picture

I ran into this issue when using the strinsert plugin.. I got this to work by going into the ckeditor configuration page and clicking edit on the CKEditor Global Profile. I then disabled the drag and drop toolbar feature. Then, edited Full Html and inserted the button 'strinsert'. The dropdown/richcombo is now showing...

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

icicleking’s picture

"...disabled the drag and drop toolbar feature..." ugh.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
cilefen’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

I am closing this support request because there have been no recent comments.