So migrating to Drupal 8 first makes a lot of sense because you can start incorporating changes into your site directly, without having to wait for a move away from Drupal 7. That’s where the big “under-the-hood” structural changes in Drupal 8 come in, upgrading from Drupal 8 to later versions will be extremely easy and not require a full migration! This makes the move from Drupal 7 to 8 an exception, once you are on Drupal 8 upgrading can more or less be done with the click of a button! Since that is less than half a year away, it might seem better to wait a bit and move from Drupal 7 to Drupal 9 directly. The upgrade provides an opportunity to think about what content you want to keep and how you can put it to it’s best use! Drupal 9 will be released in 2020, do I have to do all this again? Should I postpone?ĭrupal 9 will be released on June 3rd 2020. The same goes for migrating your content. If you now start to plan for incorporating these changes into the Drupal 8 version of the site, you still have plenty of time to thoroughly discuss these changes and efficiently spend your budget when the time comes to actually perform the upgrade. It doesn’t make sense to make big changes to your Drupal 7 site when you know that it’s official life will come to an end in 2021. Upgrading therefore provides a chance to perform structural and visual changes to your site that you have in mind anyway. It is a very stable and mature piece of software with a wide adoption worldwide.Īs mentioned earlier, “under-the-hood” Drupal 8 changed significantly compared to Drupal 7. Drupal 8 was released in November 2015, so it has been in production use for over 4 years now. The sensible thing to do is to start thinking about what steps are necessary to perform an upgrade to Drupal 8. Depending on the size of your site the time needed may vary, but to wait until the EOL date arrives is obviously not a good idea. Performing a migration and re-developing the theme mean that this needs to be discussed and planned well in advance. The massive structural changes of the inner workings of Drupal are the cause of this, highly inconvenient but certainly necessary to keep Drupal the modern framework we all need it to be. This only holds true for this specific upgrade and not for later upgrades from Drupal 8 to Drupal 9 for instance, more on that later. The theme that is used to display the content on the site will also have to be re-developed. Upgrading your site from Drupal 7 to Drupal 8 means that you have to also migrate all content that is present in your site. A number of partners will be selected to provide paid security support for several years and there will always be members of the community who are prepared to do some work on unsupported contributed modules. I knowingly say ”impact” because the robustness of the Drupal project prevents a full stop of support even after the EOL date. Security, flexibility and scalability are often reasons why Drupal was chosen for a project and this clearly has an impact. The Drupal Association will no longer provide security releases for Drupal 7, no further development on the core framework will be done and development on the Drupal 7 version of most contributed modules will stop. This does certainly not mean that your site will come to a grinding halt on that day, but it does mean that Drupal’s strong points will start to fade going forward. Active development of Drupal 7 stops on the EOL date. There are two things you should be aware of:ġ. In you role as a project- or site owner you might not be aware of the implications the “End of Life” announcement has if your site is running on Drupal 7 right now. That’s nice, now why are you telling me this?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |