Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add Customizer context #399
This is a work-in-progress PR to add a Customizer context. If you want to take it for a spin, try the standalone plugin: https://github.com/dlh01/fieldmanager-beta-customize/.
What's included so far covers most of Fieldmanager's fields and their features, but questions about the implementation and known bugs are below.
Suggestions and feedback are appreciated!
The last round of changes to this PR should have fixed
I've answered this question for now as "yes" and added a
referenced this pull request
Dec 4, 2015
0795c83 updates the behavior in
At the moment, there doesn't seem to be a standard way to alert users to errors while saving changes in the Customizer.
There also doesn't seem to be a great a way to send a message when an error occurs while previewing a setting change. Failing validation will still stop the preview from using invalid values, but it does so silently. Suggestions welcome here, too.
added a commit
this pull request
Oct 12, 2016
The proposed Customize context is now available as a standalone plugin that you can use alongside a stable version of Fieldmanager: Check out Fieldmanager Beta: Customize (props @jameswburke for reviewing the initial pull request).
Screenshots, installation instructions, details about how the plugin integrates with Fieldmanager, and steps to activate a demo are all available in the README.
If you're interested in using the Customize context, please try the plugin. Feedback, bug reports, and pull requests are all welcome at the repo.
Plugin development will continue much like a feature plugin in WordPress core. Improvements to the plugin based on testing will, hopefully, strengthen this pull request in turn.