Mark a field as deprecated

[ryanleichty]

This is another idea coming from Sanity where you can mark a field as deprecated.

• Mark the field as deprecated
• Add a reason for the deprecation (“Use the body field instead”).
• Optionally make the field read only

Quick mockup using existing elements:

[mmikkel]

I like this idea, but I think the ability to add warnings and tips to custom fields would cover the use case (aside from the read-only thing), and would probably be more useful vs. a dedicated feature to "deprecate" fields. I suggested this a while back: #12821

That said, if it was possible to make custom fields read-only in field layouts (perhaps even conditionally), that would also be really cool. (FWIW, the Incognito Field plugin can currently be used to create text fields that are conditionally read-only, hidden or disabled.)

[ryanleichty]

Yeah, I feel like it would for sure have to be within a field layout at minimum. Perhaps the warning or tip is included in a tooltip on top of a badge:

[brandonkelly]

Just added the ability to set tips and warnings on fields within field layout designers, for Craft 5.4 (1d3658d).

I think this makes more sense than an explicit “deprecated” field concept for a couple reasons:

• More versatile (there are a number of reasons you may want to warn authors about a particular field).
• “Deprecated” is developer lingo. Kindof doubt most authors would understand what it means, and there’s no good reason to start teaching them, when a more verbose explanation is likely needed anyway.

Here’s an example, combined with a condition that hides the field entirely when it doesn’t have a value:

[mmikkel]

Hooray! 👏 👏

[ryanleichty]

That was fast! 🚀

[brandonkelly]

Craft 5.4.0 is out with those new settings.