- Issue created by @trackleft2
- 🇺🇸United States trackleft2 Tucson, AZ 🇺🇸
We should consider just creating a documentation page and then linking to it instead of cluttering the project page with upgrade advice.
There isn't currently any advice on this module's project page for how to upgrade from the Drupal 7 version of this module to the current version (2.1.0 right now).
Add some advice to the project page in order to help people navigate the upgrade.
I took the liberty of collaborating with Chat GPT to create this small guide.
<h2>Upgrading from the 7.x-1.5 version to a 2.1.x version.</h2>
<p>When upgrading from the Drupal 7 version of the User Expire module to the Drupal 8/9/10/11 version, several new features and improvements are available in version 2.1.0 and greater.</p>
<h3>Key enhancements include:</h3>
<ul>
<li>
<strong>Configurable Warning Email Timing:</strong> Administrators can now define the time period between when a user's account is set to expire and when the warning email is sent. This feature, introduced in response to
issue
#3261317: Force a delay between notification and user expiration →
, offers greater flexibility in managing user notifications.
</li>
<li>
<strong>Customizable or Disabling Email Notifications:</strong> The module now allows you to customize the warning email content or disable the notification entirely. This ensures you can tailor the messaging to fit your site’s needs or omit it if email notifications are not required. See
✨
Disable or customize expiration email
Needs work
[#]
</li>
<li>
<strong>No Longer Requires the Date Contributed Module:</strong> In Drupal 7, the User Expire module relied on the Date contributed module. However, starting with Drupal 8, the module takes advantage of the <code>datetime
form field type provided by Drupal Core, eliminating the need for additional dependencies.
When upgrading from 7.x-1.5, review your current settings and update the configuration in the 2.1.x version to take advantage of these new features. Be sure to test the email notification functionality and make any necessary adjustments to align with your site’s requirements.
Publish
Active
2.0
Documentation
We should consider just creating a documentation page and then linking to it instead of cluttering the project page with upgrade advice.