You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hadn't looked at that part of the code to see how you're handling it, but it'd be a pretty easy switch and a little more like how WP handles things like this.
Anyway, it's an enhancement suggestion that might be worth considering at some point, particularly if you start adding more theme-supported features.
The text was updated successfully, but these errors were encountered:
Thank you for this suggestion. I will give it some consideration. I recommend people explicitly define which taxonomies and fields their theme will use so if a new one is added to the plugin, it is not automatically revealed to the theme users (since the theme likely won't support it right away).
I would have to consider how to make a change like this backwards compatible.
My apologies for such a late response. I need to figure out how to get GitHub to email me when new issues are opened. For months I was thinking nobody had contributed yet. Just merged in the first pull request into the framework today, which felt great.
A feature suggestion for theme support. Instead of doing this:
You could consolidate this into a single theme support call:
This would be similar to how WP handles post formats:
I hadn't looked at that part of the code to see how you're handling it, but it'd be a pretty easy switch and a little more like how WP handles things like this.
Anyway, it's an enhancement suggestion that might be worth considering at some point, particularly if you start adding more theme-supported features.
The text was updated successfully, but these errors were encountered: