74 lines
3.2 KiB
YAML
74 lines
3.2 KiB
YAML
|
uuid:
|
|||
|
|
- value: ba009e81-1bbd-44dd-928f-21681d2dc1ff
|
|||
|
|
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:44+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: |
|
|||
|
|
Just because core is supported...
|
|||
|
|
created:
|
|||
|
|
- value: '2023-05-03T00:00:00+00:00'
|
|||
|
|
changed:
|
|||
|
|
- value: '2025-05-11T09:00:44+00:00'
|
|||
|
|
promote:
|
|||
|
|
- value: false
|
|||
|
|
sticky:
|
|||
|
|
- value: false
|
|||
|
|
default_langcode:
|
|||
|
|
- value: true
|
|||
|
|
revision_translation_affected:
|
|||
|
|
- value: true
|
|||
|
|
path:
|
|||
|
|
- alias: /daily/2023/05/03/just-because-core-is-supported
|
|||
|
|
langcode: en
|
|||
|
|
body:
|
|||
|
|
- value: |
|
|||
|
|
<p>Just because Drupal core is supported, it doesn't mean that all of the other modules your project uses are still also supported or actively worked on.</p>
|
|||
|
|
|
|||
|
|
<p>Since the Drupal 8 release in 2015, I've seen numerous examples of modules that haven't been updated for some time as maintainers focus on writing and maintaining the versions for Drupal 8 and now 9 and 10.</p>
|
|||
|
|
|
|||
|
|
<p>Whilst it isn't marked as unsupported, it isn't being updated either.</p>
|
|||
|
|
|
|||
|
|
<p>I recently explained to a client that their site uses a module last released in 2014. It’s buggy, but there’s no newer version to use and issues in the queue are no longer being fixed or triaged.</p>
|
|||
|
|
|
|||
|
|
<p>Override Node Options - a popular module I maintain - is in a similar situation. The most recent Drupal 9/10 version was in February 2023, whereas the last Drupal 7 release was in March 2018.</p>
|
|||
|
|
|
|||
|
|
<p>I don't have any official figures to support this, but feel the contribution rate for Drupal 7 projects (as in modules, themes and distributions) has been slowing for some time.</p>
|
|||
|
|
|
|||
|
|
<p>Meanwhile, Drupal 7 core is still supported, at least for now.</p>
|
|||
|
|
|
|||
|
|
|
|||
|
|
format: full_html
|
|||
|
|
processed: |
|
|||
|
|
<p>Just because Drupal core is supported, it doesn't mean that all of the other modules your project uses are still also supported or actively worked on.</p>
|
|||
|
|
|
|||
|
|
<p>Since the Drupal 8 release in 2015, I've seen numerous examples of modules that haven't been updated for some time as maintainers focus on writing and maintaining the versions for Drupal 8 and now 9 and 10.</p>
|
|||
|
|
|
|||
|
|
<p>Whilst it isn't marked as unsupported, it isn't being updated either.</p>
|
|||
|
|
|
|||
|
|
<p>I recently explained to a client that their site uses a module last released in 2014. It’s buggy, but there’s no newer version to use and issues in the queue are no longer being fixed or triaged.</p>
|
|||
|
|
|
|||
|
|
<p>Override Node Options - a popular module I maintain - is in a similar situation. The most recent Drupal 9/10 version was in February 2023, whereas the last Drupal 7 release was in March 2018.</p>
|
|||
|
|
|
|||
|
|
<p>I don't have any official figures to support this, but feel the contribution rate for Drupal 7 projects (as in modules, themes and distributions) has been slowing for some time.</p>
|
|||
|
|
|
|||
|
|
<p>Meanwhile, Drupal 7 core is still supported, at least for now.</p>
|
|||
|
|
|
|||
|
|
|
|||
|
|
summary: null
|
|||
|
|
field_daily_email_cta: { }
|