Download the PHP package freshflesh/acf-sync without Composer

On this page you can find all versions of the php package freshflesh/acf-sync. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package acf-sync

ACF Sync

Author Note : Since 5.1.5, ACF now includes its own manual syncing feature ! I recommend using this feature instead of the ACF Sync plugin for manual synchronization. ACF Sync is still relevant if you need automatic synchronization between different environments, especially on production instances where the ACF UI shouldn't be accessible to users. I will release soon a 2.0 version that will take advantage of the 5.1.5 features and will drop the manual synchronization feature

ACF Sync is a little WordPress plugin that let you keep your ACF field groups synchronized between different environments.

It ensures you to always have up-to-date fields across different development and production environments without the need to export/import your ACF fields manually.

This was inspired from this nice article from Sean Butze about deploying ACF field groups, except it has been adapted to work with ACF 5 and its new local JSON Feature.

Installation

Install this plugin along with ACF > 5.0.0.

How does it work ?

To synchronize your field groups across your dev team, you need to version the JSON files produced by ACF with GIT or any other SCM tool.

See here to learn more about the local JSON functionality and how to activate it on your website.

Auto Sync

You can automatically synchronize your field groups by defining a ACF_FIELDS_VERSION constant somewhere in your code.

It should contain your field groups version, following the version_compare php function format.

Example : define('ACF_FIELDS_VERSION', '1.0.0');

You might want to put this constant with your Custom Post Type definitions, for example :

Whenever you update your fields in the WordPress admin, update the ACF_FIELDS_VERSION constant to a new version ; for example 1.0.0 to 1.1.0.

When another developer of your team will fetch your changes and new JSON files, ACF Sync will know they are newer than the ones in database, and will automatically import them back in database when accessing the WordPress Admin.

Of course ACF Sync can also be used to synchronize fields groups between development and production environments.

Manual Sync

Aside from the Auto Sync feature, ACF Sync lets you synchronize your field groups manually if your prefer to have more control on how and when field groups should be imported.

When activated, it simply add a new option on the Import/Export setting page of ACF.

Environment based configuration

ACF Sync also optionally lets you use a WP_ENV constant to disable saving to JSON and hide the ACF UI on staging and production environment to avoid mistakes on non-development environments.

If you use the Bedrock WordPress stack, WP_ENV is already defined in the config, otherwise you can define it yourself in your wp-config.php.

Licence

MIT

All versions of acf-sync with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.0
wordpress/wordpress Version >=3.5
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package freshflesh/acf-sync contains the following files

Loading the files please wait ....