Notice in Site Health in case revisions are disabled

[cewebdesignmunchen]

Feature request/idea: Give out a notice in Site Health in case revisions are disabled.
Feature request/idea: New setting in Settings>Writing: Limit revisions (maybe 3-300)

I've added a "Default Revision Limit" field in the Settings -> Writing page. Right now it is just HTML only which helps to store the value for revision limit. Other functionality in progress.

[tirth03]

The initial Revision limit field is added.

Now, Where should I put the function to filter for the revision limit?

I'm also working on 'class-wp-site-health.php' for test. Let me know in which priority I should add it to. I think medium suits best, yet let me know.

[SergeyBiryukov]

Hi there, thanks for the ticket!

Replying to cewebdesignmunchen:

Feature request/idea: Give out a notice in Site Health in case revisions are disabled.
Feature request/idea: New setting in Settings>Writing: Limit revisions (maybe 3-300)

I think these two ideas should be evaluated separately. A notice in Site Health would be helpful, but a new setting would go against the ​Decisions, not Options philosophy of WordPress.

For this ticket, I would suggest implementing the first idea, and then maybe creating another ticket for the second one.

[cewebdesignmunchen]

Replying to SergeyBiryukov:

Hi there, thanks for the ticket!

Replying to cewebdesignmunchen:

Feature request/idea: Give out a notice in Site Health in case revisions are disabled.
Feature request/idea: New setting in Settings>Writing: Limit revisions (maybe 3-300)

I think these two ideas should be evaluated separately. A notice in Site Health would be helpful, but a new setting would go against the ​Decisions, not Options philosophy of WordPress.

For this ticket, I would suggest implementing the first idea, and then maybe creating another ticket for the second one.

Thank you for the reply. Implementing the first idea would be great.

The second one can be ignored due to "Decisions, not Options". Thanks for the hint. That idea is not for the core than and might be (or already is?) for a plugin for users who want to control the number of revisions. Maybe an absolute limit (~10000?) in core to avoid problems? But if no one ever ran into problems, there is no need for this either?

I've added a notice in Site Health if the revision is disabled.

### If the revision is disabled

### If the revision is enabled

Trac ticket: (https://core.trac.wordpress.org/ticket/62119)