WordPress.org

Make WordPress Core

#24335 closed defect (bug) (invalid)

Structured format support should be tied to format-specific sub-UI's

Reported by: DrewAPicture Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.6
Component: Post Formats Keywords:
Focuses: Cc:

Description

Since we're now making all 9 formats accessible to users regardless of theme support, all of the sub-UI's such as the meta field groups and media insertion workflows are also accessible regardless of declared theme support.

At this point, declaring structured-post-formats support really only serves to short-circuit core output for a select few of the formats. And so, if a theme isn't supporting structured data for some of the formats, users will be adding structured data that likely won't be handled by their theme, creating confusion.

We should tie declared support for structured formats to their respective sub-UI's.

IMHO, I think the best solution is to keep the sub-UI's visible but have some kind of obvious notation that the theme doesn't support handling structured data for that format with maybe a reference link for extending their theme to support it.

Change History (3)

comment:1 DrewAPicture11 months ago

  • Keywords ux-feedback added

comment:2 follow-up: johnbillion11 months ago

I might be missing something, but is this not the point of #23347? If your theme doesn't support a given format, it'll still be outputted in a formatted manner by core (via a hook on the_content).

comment:3 in reply to: ↑ 2 DrewAPicture11 months ago

  • Keywords dev-feedback ux-feedback removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Replying to johnbillion:

I might be missing something, but is this not the point of #23347? If your theme doesn't support a given format, it'll still be outputted in a formatted manner by core (via a hook on the_content).

Actually yes, post_formats_compat() handles that output for everything but status, aside, chat and gallery which use the editor.

Note: See TracTickets for help on using tickets.