Download the PHP package pivvenit/acf-pro-installer without Composer

On this page you can find all versions of the php package pivvenit/acf-pro-installer. 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-pro-installer

ACF PRO Installer

PackagistPackagist Dependabot Coverage Status

A composer plugin that makes installing ACF PRO with composer easier.

It reads your :key: ACF PRO key from the environment or a .env file.

:warning: Deprecated. Supported till 1st of June 2023 :warning:

This plugin is deprecated, since Advanced Custom Fields has released native composer support. We actively encourage users to switch to their solution. This composer plugin will be updated/maintained till 1st of June 2023. Afterwards we will mark this repository as archived, and shutdown the repositories mentioned below.

Usage

This plugin is compatible with Both Composer 2.x (latest) and 1.x

1. Add our Advanced Custom Fields Composer Bridge repository to the repositories field in composer.json

This repository simply provides a periodically updated packages.json, that redirects composer to the ACF provided downloads. Note that this repository does not provide any Advanced Custom Fields Pro packages itself, it only tells Composer where it can find ACF Pro packages. Secondly it is important to note that your license key is not submitted to the repository, since the installer downloads the Advanced Custom Fields Pro zip files directly from ACF's servers.

Why this repository?

Since it enables you to use advanced-custom-fields/advanced-custom-fields-pro package with version constraints like any normal Packagist package. You no longer have to update the version manually as you had to with philippbaschke/acf-pro-installer (and tools like dependabot will also work for ACF).

This installs the package as wordpress-plugin type, in case you want a different type, use the following URL:

wordpress-muplugin:

https://pivvenit.github.io/acf-composer-bridge/composer/v3/wordpress-muplugin/

wpackagist-plugin:

https://pivvenit.github.io/acf-composer-bridge/composer/v3/wpackagist-plugin/

library:

https://pivvenit.github.io/acf-composer-bridge/composer/v3/library/

2. Make your ACF PRO key available

There are 3 ways to make the ACF_PRO_KEY available:

Select the one that best matches your setup:

2.a Using the ACF_PRO_KEY Environment variable

Set the environment variable ACF_PRO_KEY to your ACF PRO key.

2.b Use a .env file

Alternatively you can add an entry to your .env file:

2.c. Setting the key in $COMPOSER_HOME/config.json

You specify the acf-pro-key in the config section of your $COMPOSER_HOME/config.json

$COMPOSER_HOME is a hidden, global (per-user on the machine) directory that is shared between all projects. By default it points to C:\Users\<user>\AppData\Roaming\Composer on Windows and /Users/\<user\>/.composer on macOS. On nix systems that follow the XDG Base Directory Specifications, it points to $XDG_CONFIG_HOME/composer. On other nix systems, it points to /home/\<user\>/.composer.

3. Require ACF PRO

All versions of acf-pro-installer with dependencies

PHP Build Version
Package Version
Requires php Version ^7.3||^8.0
composer-plugin-api Version ^1.1||^2.0
vlucas/phpdotenv Version ^2.0 || ^3.0 || ^4.0 || ^5.0
ext-json Version *
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 pivvenit/acf-pro-installer contains the following files

Loading the files please wait ....