Max age settings above one day not reflected in UI when purge_ui is disabled.

Created on 16 March 2018, over 6 years ago
Updated 26 September 2023, 9 months ago

Problem/Motivation

It seems possible to set a max-age above one day via configuration. However, this value is not reflected on the /admin/config/development/performance form without the Purge UI module enabled.

Proposed resolution

Move purge_ui_form_system_performance_settings_alter() to the base purge module.

Remaining tasks

Create patch. I'm not seeing any tests related to this.

User interface changes

The additional page cache maximum age values will now be visible in the dropdown without enabling the Purge UI module. Configuration values that match an option will be reflected as well.

API changes

None.

Data model changes

None.

This is all based on the assumption that the Purge module can be used successfully without enabling the Purge UI module, assuming appropriate configuration. If that is inaccurate, please close this. Also, maybe the fact that max-age can be set to any value makes this change unnecessary. However, I suspect most users would select an option in the dropdown.

Thanks!

πŸ› Bug report
Status

Fixed

Component

User interface

Created by

πŸ‡ΊπŸ‡ΈUnited States richardbporter

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024