-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to Drupal 9 #36
Comments
All of our custom modules need to at least be flagged as compatible with Drupal 9. A few of them need some code changes, due to deprecated and removed functions. |
Drupal 9 has a new rewritten Media system in core. This is different from, and replaces, the old Media modules. The new Media system also replaces the functionality of the custom "Video Embed" module we have been using in Drupal 8. We used the old Media modules, along with custom "Entity Reference" modules to create a way for staff to browse and select existing Media to attach to pages as a "Cover Image" and "Content Image". MigrationThere is a way to migrate the content from the old, custom Media modules to the new, core Media system. However, this does not update the content fields to use the new Media library for adding and selecting existing Media in the site. So, we migrated all the images from the old Media module to the new Media - and pages on the site still have "Entity Reference" fields that point to the correct Media. However, staff cannot change them or upload new Media for the "Cover Images" or "Content Images". This is because the field definition for "Cover Images" and "Content Images" is the obsolete "Entity Reference" field type, instead of the new "Media Reference" field type. This is what's triggering the need to drop the "Cover Image" and "Content Image" fields and recreate them as "Media References". Then, staff will be able to use the new "Media Library" to browse and select existing Media that's been uploaded to the site. |
https://www.drupal.org/about/9
https://www.drupal.org/about/9/from-8
The text was updated successfully, but these errors were encountered: