sc0ttkclark/wordpress-fields-api

Implementation: Settings API

sc0ttkclark opened this issue · 4 comments

sc0ttkclark commented
  • Map Settings API functions over to Fields API for backwards compat
  • Display sections
  • Display fields for each section
  • Settings save integration to process through Settings API
  • Backwards compat control types?
  • Extend (?) Control Type for Page Settings
  • Control "Group" to allow more than one type of control per "field". (e.g. thumbnail sizes)
NateWr commented

Is there any plan to support the tab pattern that seems to be widely adopted by WP plugins?

tabs

sc0ttkclark commented

#30 will allow for this type of behavior, though it won't be implemented in core (or at least hasn't been yet)

NateWr commented

👍

holisticnetworking commented

Question, in terms of WordPress' overarching strategy going forward:

My understanding has been that the Customizer was implemented, at least in part, as a means to eliminate other types of customization screens. My understanding was that they wanted everything to be eventually pushed over to the Customizer.

With this in mind, does updating the Settings API make sense? I'm only too happy to see this behemoth go the way of the dodo. But I'm just wondering if effort could be better-used in other areas?