Skip to content
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Fieldmanager is a comprehensive toolkit for building forms, metaboxes, and custom admin screens for WordPress.

Build Status

Using Fieldmanager in your WordPress Project

Fieldmanager is a powerful library which can make the development of sophisticated features a breeze. To get started, simply download and install this plugin into your plugins directory and activate it on the plugins screen. To learn how to use Fieldmanager's API, visit the project's official website at There is also a demo plugin which illustrates a lot of what you can do with Fieldmanager.


  • WordPress: 4.7+
  • PHP: 7.0+

Fieldmanager is tested down to and works on PHP 5.3-5.6, but we don't officially support PHP5. We strongly encourage using PHP7.

Downloads and Versioning.

You can view Fieldmanager's official releases here.

The master branch on GitHub is the "bleeding edge" release. As of 1.0, Fieldmanager will maintain a typical release cycle, with alpha, beta, and RC releases, and we hope to move through "minor" versions pretty quickly. While we encourage everyone to develop with and test on early releases and help us find the bugs, stable releases are recommended for production.

Contributing to Development

Development of Fieldmanager happens on Github. Bugs with Fieldmanager should be addressed in the Github issue queue, and enhancements or bug fixes should be submitted as pull requests, which are always welcome.

Generating Documentation

To build Fieldmanager's API documentation, the latest version of which is available at, you need apigen installed. Once you've got that, you can generate the entire documentation tree as follows:

apigen -c apigen.neon

Running QUnit tests

Fieldmanager uses QUnit for JavaScript unit tests. To quickly check the status of the tests, open /tests/js/index.html in your browser. You can also run the tests from the command line: Install the dependencies with npm install, then use grunt qunit:latest to run the tests against WordPress trunk or grunt qunit:recent to run the tests against trunk and the last two major releases.

You can’t perform that action at this time.