Install CKEditor 5įirst, you'll need to install CKEditor 5. To upgrade CKEditor there are a few steps. If you are unsure you can do the upgrade in Drupal 10. Also, a lot of the contributed CKEditor modules that add extra functionality are fully upgradable too so if you know you won't end up with broken HTML in your WYSIWYG text editors then proceed. Upgrading CKEditor to CkEditor5Īs mentioned above, this isn't an issue for a basic CKEditor upgrade with no add-ons. Okay, let's continue with the steps for upgrading a basic CKEditor. I am also going to leave out the theme upgrade work as it didn't turn out exactly how I thought, it possibly could but I hit some other issues so decided to reverse the work and I'll do it after the upgrade. Related: Upgrading CKEditor4 to CKEditor5 with contributed modules (Coming soon)Īs stated the above was written before the upgrade so I will now review what I did with post-upgrade notes. If you use a customized CKEditor(4) set-up using contributed modules then pop over there and see what I had installed and the path for the upgrade. However, I have tested the Media module and other contributed modules, such as Linkit and Code Snippets, work in CKEditor 5 on another site that uses them. This shouldn't be a big issue as I am not using any contributed modules on this site yet. I will switch out CKEditor for CKEditor 5. For this reason, I have removed this step from this article to keep it shorter. I wrote a plan to do this on Drupal 9 but in the end, it worked out easier to do this after the upgrade and before the database updates were run. The last things I needed to do were deal with the themes, namely Stable and Classy, and CKEditor. I include here more so you can see the full process and that researching and planning are important steps. This section, Pre-upgrade Tasks and Final Checks was researched and written before I attempted the upgrade. I am also using both Classy and Stable for my custom theme so there are extra steps that I need to take. I uninstalled Bartik and Seven for now as Classy and Stable are base themes and aren't displayed on the appearance page. These are shown in Upgrade Status and also on the default status page. Next up, dealing with the deprecated modules and themes. I'll mention this again but please be aware of this that Update Status is checking your installed version but composer checks the package on the official service so when trying to upgrade it will show incompatibility. Please note that if a contributed module is patched you will need to remove the package with composer and add in it as a custom module. Īfter patching the Show Title module and fixing the custom theme info file everything checked out okay. A simple case of adding 10 to the core version requirements in the theme info file. You can also contribute back your work if you can do it. If a module you are using isn't Drupal 10 ready you may need to do this. The Upgrade Status module has an excellent overview of your site's upgrade health. Upgrade Status gives you a good overview of what needs to be done, so it's a good idea to install it. Install Upgrade Status ModuleĮven though I knew that all the modules were up to date, I still installed the Upgrade Status module to see what it suggests. I used version 3.18 but since this upgrade, there is a new version, 4.0.0-alpha1, that is compatible with Drupal 10 so it may be better to use that. Once you know that your modules are up to date I recommend installing the Upgrade Status Module.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |