Looking at other CKEditor plugin modules and some of the documentation on drupal.org, it seems to be a defacto standard to have ckeditor plugins in libraries/ckeditor/plugins/pluginname.
This makes sense since it removes the risk of confusion and conflicts with non-ckeditor libraries that might have the same name and CKEditor's default instructions are to put plugins in a plugins sub-directory, which is what Drupal core does with its default CKEditor plugins.
If we can get consistency with where CKEditor plugin modules store their libraries it also makes it easier to manage all CKEditor plugins in a uniform manner.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 3046778-support-additional-libraries-locations-3.patch | 2.93 KB | mark_fullmer |
Comments
Comment #2
mark_fullmer+1 for this. I also think that additional
librariespath locations should be supported, such as such asprofiles/[profilename]/librariesorsites/default/librariesSee companion issue for the CKEditor A11yChecker at #3068819: Support alternate libraries path
Patch forthcoming...
Comment #3
mark_fullmerThe attached patch is based largely on the Libraries module, though it does not require the Libraries module as a dependency. It will look in the following locations for the a11ychecker plugin:
- libraries/
- profiles/[activeprofile]/libraries
- sites/default/libraries
- sites/all/libraries/ (backwards-compatibility)
- libraries/ckeditor/plugins
- profiles/[activeprofile]/libraries/ckeditor/plugins
- sites/default/libraries/ckeditor/plugins
- sites/all/libraries/ckeditor/plugins (backwards-compatibility)
Comment #4
pifagorComment #6
pifagor