• 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.

This extension for Advanced Custom Fields that makes it possible to manage your field-groups through the console of wp-cli. The goal of this project is to make life easier for developers who working on Wordpress projects that use Advanced Custom Fields and love the WP-CLI command line tools.

• Advanced custom fields did not interface with WP-CLI
• Sharing field-groups through XML or PHP code caused problems with differences between development, test, staging and production enviroments when shared with XML.
• No direct SVN or GIT support without manually putting the exported PHP or XML into a versioned directory.
• Naming convention for XML files was always the same, resulting in renaming hassle.
• Only using the generated field-groups on runtime through PHP code in functions.php disables the editing mode (which is an awesome UI that we require). So importing should be possible.

• Advanced Custom Fields plugin
• wp-cli http://wp-cli.org/

This project adds the acf command to wp-cli with the following subcommands:

• wp acf: Default test and prints the help overview.

• wp acf status: provides a list of found field-groups in the current database of your Wordpress project.

• wp acf export:

  • creates a field-group directory into your current theme's directory.
  • creates a directory with the field-group name for each fieldgroup.
  • creates a data.php and data.json for each field-group inside their respective folders.
  • use wp acf export all to export everything without prompting

• wp acf import: imports the XML(s) from active-theme/field-groups/{field-group_name}/data.xml`

  • When using wp acf import a selection menu apears to choose which field-group to import

• wp acf clean: cleans up the database from all found ACF post types and their coupled post_meta values, use this after you've edited the field-groups in the UI and used export to generate the new data.php files. Watch out: cannot be undone.

1. install wp-cli http://wp-cli.org/
2. clone this repo as advanced-custom-fields-wpcli in your plugins directory
3. activate advanced-custom-fields-wpcli plugin through "wp plugin activate advanced-custom-fields-wpcli" (or activate in the plugin menu)
4. open a terminal and go to your wordpress directory
5. type wp (and see the acf commands if installed correctly)
6. type wp acf to test the acf-wpcli extension
7. start using the commands as explained in "Commands"

When the plugin is enabled, any exported field groups found on the filesystem in your registered paths will be added to Wordpress at runtime.

If you would like to disable this behaviour you can remove the acf_wpcli_register_groups action:

  remove_action('plugins_loaded', 'acf_wpcli_register_groups');

• acfwpcli_fieldgroup_paths By default ACF-CLI will search 2 paths for field-groups. The active_theme and active_child_theme. The acfwpcli_fieldgroup_paths gives you the ability to add more paths where ACF-CLI should load/export from/to. Example:

  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;
  }

• make acf-wpcli extension update-proof
• release this plugin as official WordPress plugin