Add daily email for 2024-01-03

Why you need to start upgrading from Drupal 7 now
This commit is contained in:
Oliver Davies 2024-01-03 20:00:00 +00:00
parent f7b812ce53
commit 5ac6c32725
3 changed files with 58 additions and 1 deletions

View file

@ -0,0 +1,47 @@
---
title: >-
Why you need to start upgrading from Drupal 7 now
date: 2024-01-03
permalink: archive/2024/01/03/why-you-need-to-start-upgrading-from-drupal-7-now
snippet: |
Are you still using Drupal 7? You need to start upgrading to Drupal 10 now instead of waiting until next year.
tags:
- drupal
- drupal-upgrade
- drupal7
- php
- phpc
---
{% block content %}
There's only one year before support for Drupal 7 support ends, but there are still more than 337,000 Drupal 7 websites, according to <https://www.drupal.org/project/usage/drupal>.
Even though there's a year left, if you've got a Drupal 7 website, you need to start upgrading now!
Unlike upgrading from Drupal 8 to 9 or 9 to 10, upgrading from Drupal 7 requires major changes to your code for it to be compatible. This will take time to do and test.
Most websites have some or many custom modules and at least one custom theme that must be upgraded.
Most use a large number of community-contributed modules.
Many of these are abandoned or minimally maintained as their maintainers have focused on newer Drupal versions or a module has been marked as unsupported in favour of another.
If they do have supported versions, it is likely that they haven't had a release for some time. If that's the case, they're essentially unsupported.
Because of this, there may not be the same modules available with the same functionality for Drupal 10.
Depending on the available modules, your functionality may need to change, or the old functionality will need to be written within a new custom module.
## Here's the thing
Depending on the complexity, it will take a number of months to complete an upgrade.
Rather than wait until 2025, you want to do the work now whilst Drupal 7 is still supported rather than waiting and being vulnerable to security exploits if running an outdated and unsupported version.
{% endblock %}
{% block cta %}
P.S. Are you stuck on Drupal 7? Purchase a [Drupal upgrade consulting call][call] or [upgrade roadmap][roadmap] and I'll help you on your way to Drupal 10.
{% endblock %}
[call]: https://www.oliverdavies.uk/call
[roadmap]: https://www.oliverdavies.uk/roadmap

View file

@ -6,6 +6,8 @@
{{ parent() }}
<p>- Oliver</p>
{%- block cta %}{% endblock %}
{% endblock %}
{% block content_bottom %}

View file

@ -31,13 +31,21 @@ use:
<description>
{{- email.blocks.content -}}
{% if 'P.S.' not in email.blocks.content %}
{%- if email.blocks.cta %}
<br>
<hr>
{{ email.blocks.cta }}
{% endif -%}
{% if 'P.S.' not in email.blocks.content and 'P.S.' not in email.blocks.cta %}
{% set ctas = [
'Are you still using Drupal 7 and dont know whats involved to upgrade to Drupal 10? <a href="https://www.oliverdavies.uk/call">Book a Drupal 7 upgrade consultation call</a> or <a href="https://www.oliverdavies.uk/drupal-upgrade">an upgrade roadmap</a>.',
'Need help or want another pair of eyes on your code? Book a <a href="https://www.oliverdavies.uk/call">1-on-1 consulting call</a> or an <a href="https://www.oliverdavies.uk/pair">online pair programming session</a> with a 100% money-back guarantee.',
'If you\'re creating a new Drupal module, try my <a href="https://github.com/opdavies/drupal-module-template">free Drupal module template</a>.',
] %}
<br>
<hr>
<p>P.S. {{ random(ctas) }}</p>
{% endif %}
</description>