Format for expires field is not stored consistently

Created on 28 April 2025, about 1 month ago

Problem/Motivation

The date format of the expires field is not stores consistently in the database.
I've came across this issue where my custom notifications are removed on cron, despite not having an expiration value.

Steps to reproduce

  1. Install the module
  2. Enable the module to keep the read status in the database
  3. Add a couple notifications, some with an expiration date, some without
  4. Run the cron
  5. See all notifications without an expiration date are removed

Proposed resolution

Update the format of the default value for the expires field, since the cron hook already verifies for a datetime format.

Remaining tasks

Verify the cron doesn't accidentally remove notifications that do not have an expiration date

User interface changes

None.

API changes

None.

Data model changes

None.

🐛 Bug report
Status

Active

Version

2.0

Component

Code

Created by

🇧🇪Belgium blacksnipe

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024