101 lines
5.2 KiB
YAML
101 lines
5.2 KiB
YAML
uuid:
|
|
- value: f5a54b2e-58c3-45e8-8e0f-00fd61db9f27
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T09:00:38+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: |
|
|
Should you upgrade from Drupal 7 to Drupal 10?
|
|
created:
|
|
- value: '2023-06-19T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:38+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2023/06/19/should-you-upgrade-from-drupal-7-to-drupal-10
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>If you're stuck on Drupal 7, why should you upgrade to Drupal 10 instead of moving to another platform?</p>
|
|
|
|
<h2 id="familarity">Familarity</h2>
|
|
|
|
<p>Although there is a new admin theme, it works in the same way as it did in earlier versions of Drupal, so it will be familiar to anyone who is used to using or developing in it.</p>
|
|
|
|
<p>And whilst there have been differences since Drupal 8, creating modules and themes should seem familiar too with similar concepts such as <code>.info</code> files (now <code>.info.yml</code> files), hooks, preprocess functions and templates.</p>
|
|
|
|
<h2 id="code-reuse">Code reuse</h2>
|
|
|
|
<p>If you have existing custom modules, you should be able to reuse some of its code in newer versions of Drupal. It might need to be restructured or refactored and will depend on how tightly coupled your business logic is to your Drupal code, but if, for example, you have a custom module that creates a node programmatically, the same can be done in newer Drupal versions.</p>
|
|
|
|
<h2 id="built-in-migration-tools">Built-in migration tools</h2>
|
|
|
|
<p>Whilst you do need to migrate your data from Drupal 7 into Drupal 10, the newer versions come with built-in migration tools that recreate your content types etc first as well as moving the data so you don't need to start from scratch.</p>
|
|
|
|
<h2 id="new-versions-of-existing-modules">New versions of existing modules</h2>
|
|
|
|
<p>Many modules and themes you use in Drupal 7 will either have equivalent versions for Drupal 10 or a nominated alternative (such as Field Collection to Paragraphs), so you don't need to look for a new solution if there's an updated version of something you already use.</p>
|
|
|
|
<h2 id="conclusion">Conclusion</h2>
|
|
|
|
<p>These are the initial things that I thought of, but there are many other reasons to upgrade to Drupal 10 instead of moving to something else.</p>
|
|
|
|
<p>TLDR - you don't need to start from scratch if you can re-use parts of your existing code, and you can use the built-in modules to handle the data migration.</p>
|
|
|
|
<p>If you have a reason, reply to let me know, and I'll post another list.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>If you're stuck on Drupal 7, why should you upgrade to Drupal 10 instead of moving to another platform?</p>
|
|
|
|
<h2 id="familarity">Familarity</h2>
|
|
|
|
<p>Although there is a new admin theme, it works in the same way as it did in earlier versions of Drupal, so it will be familiar to anyone who is used to using or developing in it.</p>
|
|
|
|
<p>And whilst there have been differences since Drupal 8, creating modules and themes should seem familiar too with similar concepts such as <code>.info</code> files (now <code>.info.yml</code> files), hooks, preprocess functions and templates.</p>
|
|
|
|
<h2 id="code-reuse">Code reuse</h2>
|
|
|
|
<p>If you have existing custom modules, you should be able to reuse some of its code in newer versions of Drupal. It might need to be restructured or refactored and will depend on how tightly coupled your business logic is to your Drupal code, but if, for example, you have a custom module that creates a node programmatically, the same can be done in newer Drupal versions.</p>
|
|
|
|
<h2 id="built-in-migration-tools">Built-in migration tools</h2>
|
|
|
|
<p>Whilst you do need to migrate your data from Drupal 7 into Drupal 10, the newer versions come with built-in migration tools that recreate your content types etc first as well as moving the data so you don't need to start from scratch.</p>
|
|
|
|
<h2 id="new-versions-of-existing-modules">New versions of existing modules</h2>
|
|
|
|
<p>Many modules and themes you use in Drupal 7 will either have equivalent versions for Drupal 10 or a nominated alternative (such as Field Collection to Paragraphs), so you don't need to look for a new solution if there's an updated version of something you already use.</p>
|
|
|
|
<h2 id="conclusion">Conclusion</h2>
|
|
|
|
<p>These are the initial things that I thought of, but there are many other reasons to upgrade to Drupal 10 instead of moving to something else.</p>
|
|
|
|
<p>TLDR - you don't need to start from scratch if you can re-use parts of your existing code, and you can use the built-in modules to handle the data migration.</p>
|
|
|
|
<p>If you have a reason, reply to let me know, and I'll post another list.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|