Custom field types for WordPress
PHP JavaScript HTML CSS Shell
Switch branches/tags
Latest commit 550f748 Nov 5, 2017 @mboynes mboynes Merge pull request #669 from alleyinteractive/phpcs-updates
Updates per latest phpcs standards
Permalink
Failed to load latest commit information.
bin Update `install-wp-tests.sh` May 1, 2017
css Merge branch 'master' into 477-update-chosen Oct 11, 2017
docs-src/templates/bootstrap adding apigen template to git. Sep 28, 2013
images Delete unnecessary DS_Store file Jan 3, 2017
js Fix sortable bug with mixed sortable nested groups Oct 25, 2017
php Updates per latest phpcs standards Nov 4, 2017
templates Prefix variables created in checkboxes and radios templates Oct 17, 2017
tests Merge branch 'master' into add/term-datasource-hierarchy-constraints Oct 26, 2017
.editorconfig Add `.editorconfig` for consistent formatting standards between editors Feb 20, 2016
.gitignore First pass at hooking up PHPCS for coding standards sniffs Feb 20, 2016
.travis.yml Increase minimum supported WP version to 4.7 Oct 11, 2017
Gruntfile.js Bump WordPress core versions tested in QUnit Sep 14, 2016
README.md Increase minimum supported WP version to 4.7 Oct 11, 2017
apigen.neon beginning work on templating system to refactor out all the sprintf()… Apr 22, 2013
composer.json Update composer.json Oct 19, 2016
credits.txt Fittingly adding Daniel Bachhuber to credits list to test Travis build Mar 13, 2014
fieldmanager.php Correct spacing around @return docs Oct 7, 2017
license.txt initial sync with vip Aug 27, 2014
multisite.xml Ensure `multisite.xml` is present to run multisite tests Feb 20, 2016
package.json Bump working version to 1.2.0-alpha Oct 6, 2017
phpcs.ruleset.xml Set minimum supported WordPress version for use of deprecated code Oct 17, 2017
phpunit.xml * Updating README Sep 28, 2013

README.md

Fieldmanager

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 Fieldmanager.org. There is also a demo plugin which illustrates a lot of what you can do with Fieldmanager.

Requirements

  • 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 api.fieldmanager.org, 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.