PHPackages                             pxlrbt/acf-configurator - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. pxlrbt/acf-configurator

AbandonedArchivedLibrary[Utility & Helpers](/categories/utility)

pxlrbt/acf-configurator
=======================

Wrapper for easy local ACF configuration in php.

0.3.2(5y ago)93422GPL-3.0-or-laterPHP

Since Dec 17Pushed 4y ago1 watchersCompare

[ Source](https://github.com/pxlrbt/acf-configurator)[ Packagist](https://packagist.org/packages/pxlrbt/acf-configurator)[ RSS](/packages/pxlrbt-acf-configurator/feed)WikiDiscussions main Synced yesterday

READMEChangelog (3)DependenciesVersions (10)Used By (0)

ACF Configurator
================

[](#acf-configurator)

**A wrapper for easy local Advanced Custom Fields configuration in php.**

ACF Configurator comes into play when you want to define Advanced Custom Fields groups in PHP and not via database. Since ACFs standard way of configuration is a long multidimensional array, it gets confusing very fast. ACF Configurator provides an easy, intuive way to configure ACF groups and fields. It uses a short, OOP oriented syntax for configuration.

Why not use the Advanced Custom Fields GUI?
-------------------------------------------

[](#why-not-use-the-advanced-custom-fields-gui)

The Advanced Custom Fields plugin provides a nice interface which is convenient for managing groups and fields in WordPress. Even clients can easily edit field with little knowledge. But configuration via PHP has some advantages:

- **No loading from database.** Configuration is not stored in database anymore and does not need to be fetched every time the page loads.
- **Couple code and configuration.** Configuration does not belong into a database. Custom fields and the themes codebase are usually coupled together tightly. Changing fields without updating the code will probalby break things.
- **Easier migration.** If a theme needs an update you usually test it in an development environment first. Transferring all the changes you made to your live site before deploying your new code, can break things, or at least is really annoying.

Installation
------------

[](#installation)

Install this package via Composer:

```
composer require pxlrbt/acf-confgurator

```

Usage (Example)
---------------

[](#usage-example)

Just import ACF Configurator and start configuration. Group class takes care of registration.

```