WordPress.org

Making WordPress.org

Opened 2 years ago

Last modified 9 months ago

#3863 new enhancement

Make plugin dependencies (suggestions) clearer in Themes Directory

Reported by: Eric3D Owned by:
Milestone: Priority: normal
Component: Theme Directory Keywords: close
Cc:

Description

More and more themes in the directory have plugin dependencies, but you don’t learn that until after you activate the theme.

I’d like to see dependencies clearly listed on each theme page, as well as having a feature filter to be able to weed out themes with dependencies.

Change History (8)

#1 @Otto42
2 years ago

WordPress does not have "plugin dependencies" built into it. If themes have that, then the themes have to have code to add it themselves.

More to the point, themes in the directory are not allowed to "require" plugins. Per the theme submission rules, themes can only suggest plugins, they must still function without them. A theme requiring a plugin to work would be a reason to use the Report button, and have the theme removed from the directory.

#2 @poena
2 years ago

I like the idea of making it easier for users to find themes that are designed for use with and (claim too) work with specific plugins.

Right now, all users can do is search for themes that have added the plugin name in the theme description. This also leads to themes trying to pack as many keywords as possible into the description.

#3 @Eric3D
2 years ago

  • Summary changed from Make plugin dependencies clearer in Themes directory to Make plugin dependencies (suggestions) clearer in Themes Directory

I usually build custom themes (from scratch or _s). When I need to get a theme from the directory these days, I find there is no way to evaluate it without installing it. A number of themes make extensive use (abuse?) of the customize feature, which now includes content as well as presentation elements. The reliance on plugins (even if not required) is another concern.

I don't have an easy fix (or even a good suggestion) for this problem. I wish I did. But a list of recommended plugins (this theme works better with XYZ) separate from the list of compatible popular plugins (tested with XYZ) would be a step in the right direction.

This ticket was mentioned in Slack in #themereview by poena. View the logs.


11 months ago

#5 @joyously
11 months ago

  • Keywords close added

This ticket was mentioned in Slack in #themereview by dingo_d. View the logs.


9 months ago

#7 @dingo_d
9 months ago

Possible solutions:

  1. On theme upload detect if the theme has the tgmpa file, and parse the data from that, store it in meta fields for a theme and display.
  1. Read the Recommended plugins: field from style.css and parse that and display only first N recommendations (similar to plugin tags) on the page.

#8 @joyously
9 months ago

I don't like encouraging plugin-specific stuff in themes. So if the readme was searchable, they could put all that in the readme.

Note: See TracTickets for help on using tickets.