![]() If you experience issues using composer why-not drupal/core ^10 should help you get to the bottom of them.įinally, run database updates and update your config export, and you should be finished. Then run: composer update -with-all-dependencies Also, update any contrib module versions if they have releases that are only for Drupal 10 and above. First, in composer.json update your core version: "drupal/core": "^10". You should now be ready to update to Drupal 10. Though that is EOL before 2024, so you'll need a plan for this in the near future. ![]() If you've got a lot of custom editor integration, you might consider using the CKEditor 4 contrib module. The upgrade path should be smooth if your site uses a fairly standard editor configuration. Going forward, as you update your module with Drupal 11 compatibility, you shouldn't need to change this again: core_version_requirement: '>=10' CKEditorĬKEditor in Drupal 10 has received a lot of work and is built on CKEditor 5. You can then specify your custom modules are compatible with Drupal 10 and above. protected function setUp(): void, and test $modules visibility should be protected (i.e.
0 Comments
Leave a Reply. |