Note: This fork of ACF WP-CLI makes it possible to install it as a WP-CLI package instead of a WordPress Plugin
WP-CLI for Advanced Custom Fields helps you manage your field-groups through WP-CLI. The reason we started this project is to make life easier for developers working on Wordpress projects using the Advanced Custom Fields Pro plugin. Fields can now easily be imported, exported and shared over SVN, GIT or comparable systems.
- Advanced Custom Fields 5 Pro plugin
wp-clihttp://wp-cli.org/
Install WP-CLI as described on http://wp-cli.org/
Then install this package using WP-CLI:
wp package install EP4/advanced-custom-fields-wpcli
Go the wordpress directory in your terminal and run:
wp acf
To see if everything is working correctly.
This project adds the acf command to wp-cli with the following subcommands:
wp acf
Prints the help overview and can be used as a default test to see if the plugin is working.
Export a field-group to a json file in the directory set by a filter.
wp acf export
For testing purposes, etc. you can also define a export directory explicitly without applying the filter by using the --export_path parameter.
wp acf export --export_path=acf-exports/
You want to export all field-groups all at once you can use:
wp acf export --all
wp acf import
Import all or specific fields from a option menu,
wp acf clean
Delete all Advanced Custom Fields Records from the database. Do this after you have edited fields-groups from the UI and exported the changes. Warning: This can not be undone, please use carefully
The acfwpcli_fieldgroup_paths gives you the ability to add more paths where ACF-CLI should load/export from/to. You should always add at least one path to this filter.
add_filter( 'acfwpcli_fieldgroup_paths', 'add_plugin_path' );
public function add_plugin_path( $paths ) {
$paths['my_plugin'] = MY_PLUGIN_ROOT . '/lib/field-groups/';
return $paths;
}
To test changes to the plugin you can use unit testing. Start by making sure all the necessary dependencies are installed, if not run:
composer install
You will need a new Wordpress installation to make sure the tests run independent from your Wordpress installation and database. To create a wordpress installation for testing run the following command:
bash bin/test_wp_install.sh wordpress_test db_username db_password localhost latest
Where 'wordpress_test' is the name for the database used to run the tests. Make sure this database doesn't exist or can be deleted. When the database already exists the script will ask you if the database can be deleted. 'Latest' can be changed if you want to test with a specific version of Wordpress, 3.6.2 for example.
After you installed you can start running tests using the follow command:
vendor/bin/behat
This will run all test. These tests include an import and export of all types of fields, cleaning, multiple fields in one field-group and tests for the menu options. If you want to run one specific test you can do this by running:
vendor/bin/behat features/testname.feature
If you need a different test you can create your own by added it to the features in the features folder.
- Make sure you import all your custom fields before updating.
- Make sure you are you using ACF5, ACF4 is not supported.
- Update the plugin
- Add the filter to your project (see Filters)
- Export you fields
- Remove unnecessary files like your old import directory, php files and json files.
- Bugfix: Import no longer created duplicates
- Add unit testing with behat and PHPUnit
- Removed uniqid feature (no longer needed).
- Bugfix: database fieldgroups are now prefered over exported fieldgroups.
- Cleaned up legacy xml import/export libraries.
- Add namespaces.
- Cleaned up all alternative notation uses.
- Multisite now correctly makes use of the global --url parameter.
- Added more comments and versioning.
- Removed dependency of wp-importer.
- Added support for composer installs.
- Dropped XML support, hello Json.