Problem/Motivation
After updating to the latest version, the following error appears: The filter_ckeditor_media_embed plugin does not exist. Valid plugin IDs for Drupal\filter\FilterPluginManager are: ace_filter, blazy_filter, ckeditor5_premium_features_collaboration_filter, filter_resize_media, editor_file_reference, entity_embed, filter_html, filter_html_image_secure, filter_image_lazy_load, filter_autop, filter_html_escape, filter_null, filter_htmlcorrector, filter_caption, filter_url, filter_align, linkit, media_embed, filter_pathologic, slick_filter, token_filter."
Steps to reproduce
Update the Drupal version to the latest release. Then, try running drush cr or open the website to verify.
Proposed resolution
Attempt to synchronize the .info.yml file with composer.json so that both specify the same Drupal core version.
Remaining tasks
- ✅ File an issue
- ✅ Addition/Change/Update/Fix
- ✅ Testing to ensure no regression
- ➖ Automated unit testing coverage
- ➖ Automated functional testing coverage
- ➖ UX/UI designer responsibilities
- ➖ Readability
- ➖ Accessibility
- ➖ Performance
- ➖ Security
- ➖ Documentation
- ✅ Code review by maintainers
- ✅ Full testing and approval
- ✅ Credit contributors
- ✅ Review with the product owner
- ✅ Release notes snippet
- ✅ Release ckeditor_media_embed-2.0.5
API changes
- N/A
Data model changes
- N/A
Release notes snippet
- fix: #3558095 Synchronize the
.info.ymlfile withcomposer.jsonto ensure both require the same Drupal core version By: @qusaitaha
Issue fork ckeditor_media_embed-3558095
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
qusai taha commentedComment #4
rajab natshahComment #6
rajab natshahComment #7
rajab natshahComment #9
rajab natshahComment #10
rajab natshah✅ Released ckeditor_media_embed-2.0.5
Comment #11
elc commentedThe drupal core requirement information is automatically included in the composer file by the drupal composer handling. It is not required to explicitly set it as it just introduces a point of failure for the future when it falls out of sync again.
Here is a snippet the information composer keeps in the lock file, as per version 2.0.4 which doesn't have the explicit requirement set but instead it bases the drupal/core requirement from the module's .info.yml file.
Whatever the original problem, this is not it.