Many people have requested this feature form your guys, and I've now hit a roadblock trying to find a proper solution, so I'm opening this as a suggested improvement as well, with as much detail and reasoning as I can provide:
The community needs a way to create One-off Options Pages for Global Site-Specific Options, for admins and/or clients to change that are not specific to the Theme itself. This is where the Theme Customizer is not appropriate. An example might be social media network URLs or client phone/email to be used throughout the site.
Toolset Types already has an entire Fields API built in, so it's inappropriate to introduce yet another fields framework into our sites, adding a ton of bloat and potential incompatibilities. Doing so enqueues Javascripts, Field Classes, Styles, etc for dozens of field types for 2 similar Field Frameworks. WordPress already has an API for creating settings pages, so I don't see a reason why Toolset doesn't have the option to create Options Pages and attach Fields to them. In fact, it seems like this would be useful for your own settings pages as a base framework.
Advanced Custom Fields plugin allows this exact thing alongside their Fields API, but it is not an acceptable option to install both Toolset Types and ACF, as they do almost the same thing.
Options Framework plugin has had a lot of complaints about site breakage upon upgrade, and many people are afraid to use it, not to mention the same bloat issue mentioned above.
So I see 2 potential routes here:
1. Will you guys consider adding Custom Options Pages support to Types?
and/or
2. Can you point developers in the direction of how we might go about using Types' Fields API to add Types Fields to a WP Options Page ourselves? (is this possible?)
As always, thanks for your help.
Other threads I've found so far asking for this behavior:
- https://toolset.com/forums/topic/create-options-page-with-global-attributes/
- https://toolset.com/forums/topic/feature-requests-options-page-and-related-fields/
Other thoughts:
1. It may even be helpful to store Type Options Pages data as a hidden Custom Post Type if it fits more easily within your framework. Not sure if the WP Community would be in line with that route, but it's an option.
