Query posts by custom fields

Account Questions

Yes. There are currently two different types of accounts:


  • Accounts – at www.advancedcustomfields.com/my-account/, and
  • Support – at support.advancedcustomfields.com

You can create a support account at any time, but you need to have purchased ACF PRO to access the Accounts area.

There are currently two different logins in the world of ACF:

  • Accounts – at www.advancedcustomfields.com/my-account/, and
  • Support – at support.advancedcustomfields.com

If you are having troubles logging in, you may be using the credentials from one side to try and login to the other. Try checking this first.

If you’re still having troubles, try resetting your password.

If you’re running into difficulties trying to reset your password, please get in touch.

With your account you can:

  • Download the latest version of ACF PRO (and all previous versions, if you wish)
  • View and upgrade your licenses
  • View and print invoices for all your previous orders
  • Edit your contact and billing details
  • View and add new support tickets

Transferring ownership of an ACF PRO license is as simple as updating the account details at your store account page. If you’ve lost your account information, or are having troubles making this happen, please let us know

Absolutely, although this is not possible through the website. Please get in touch.

Creating Fields

Creating new custom fields is a very easy process and can be done with just a few clicks of our user friendly field builder! You can create as many fields as you like, each with their own name, type and settings. Each field is added to a group which allows you to both organize your fields and specify the edit screens where they appear.

Field groups are used to organize fields and attach them to edit screens. Each field group contains a title, fields, location rules and visual settings.

To get started with your first field group, please read our Creating a Field Group guide.

Each field contains settings to customize how the field looks (its type), where its value is saved (its name) and how it functions (its settings). These field settings can be customized when editing a field group.

To learn more about field settings, please read our Field Settings guide.

Notes

Loading from a specific term

All the can be used to load values from a taxonomy term, however, a second parameter is required to target the term. This is similar to passing through a parameter to target a specific post object.

There are 3 different styles of available and are listed below.

Example Format Description
A string containing the taxonomy name and term ID
A string containing the word ‘term’ and term ID. Added in version 5.5.0
A term object. You can get a term object via many of WP’s functions such as get_term()

auto-embed

When editing a WYSIWYG field on a taxonomy term, the auto-embed functionality may not work. This is due to code within the WordPress core which limits the auto-embed functionality to posts only.

This issue carries onto the front end and prevents embed urls (youtube, vimeo, etc) from being converted to play-able embed objects.

As a current workaround for the front end, use this code at the top of your template (most likely category.php or similar). This code will set a custom post_ID and allow WP to load the embed.

Parameters

$settings

(String | Array) Array of settings or ‘id’ of a registered form.

  • id (String) A unique identifier for the form. Defaults to ‘acf-form’.

  • post_id (Integer | String) The post ID used to determine which fields to show, where data is loaded, and where data is saved. Defaults to current post ID. Can also be sent to ‘new_post’ to create a new post on submit.

  • new_post (Array) When the above attribute is set to “new_post”, this setting is used to create the post. See wp_insert_post for available parameters.

  • field_groups (Array) An array of field group IDs/keys to override the fields displayed in this form.

  • fields (Array) An array of field IDs/keys to override the fields displayed in this form.

  • post_title (Boolean) Whether or not to show the post title text field. Defaults to false.

  • post_content (Boolean) Whether or not to show the post content editor field. Defaults to false.

  • form (Boolean) Whether or not to create a element. Useful when adding to an existing form. Defaults to true.

  • form_attributes (Array) An array or HTML attributes for the form element.

  • return (String) The URL to be redirected to after the form is submitted. Defaults to the current URL with a GET parameter ‘?updated=true’. A special placeholder ‘%post_url%’ will be converted to post’s permalink. A special placeholder ‘%post_id%’ will be converted to post’s ID.

  • html_before_fields (String) Extra HTML to add before the fields.

  • html_after_fields (String) Extra HTML to add after the fields.

  • submit_value (String) The text displayed on the submit button.

  • updated_message (String) The message displayed above the form after being redirected. Can also be set to false for no message.

  • label_placement (String) Determines where field labels are places in relation to fields. Defaults to ‘top’. Choices of ‘top’ (above fields) or ‘left’ (beside fields).

  • instruction_placement (String) Determines where field instructions are placed in relation to fields. Defaults to ‘label’. Choice of ‘label’ (below labels) or ‘field’ (below fields).

  • field_el (String) Determines element used to wrap a field. Defaults to ‘div’. Choices of ‘div’, ‘tr’, ‘td’, ‘ul’, ‘ol’, ‘dl’.

  • uploader (String) Whether to use the WP uploader or a basic input for image and file fields. Defaults to ‘wp’ . Choices of ‘wp’ or ‘basic’.

  • honeypot (Boolean) Whether to include a hidden input field to capture non-human form submission. Defaults to true.

  • html_updated_message (String) The HTML used to render the updated message.

  • html_submit_button (String) The HTML used to render the submit button.

  • html_submit_spinner (String) The HTML used to render the submit button loading spinner.

  • kses (Boolean) Whether or not to sanitize all data with the function. Defaults to true.

Creating Content

With your fields created, it’s time to start editing your content! All our fields are very intuitive to use and display seamlessly with the WordPress admin style. You don’t need to trigger any event to show or edit custom fields, they will appear and function just like the WP post_title and post_content fields! Simply enter your content and update the post!

Fields are not just available for posts! You may also display fields your custom fields on the page, custom post type, user, taxonomy term, comment, media and custom options pages!

To get an idea of the different content you can edit in ACF, please look over the available .

Support Questions

We are fanatical about support, and want you to get the best out of your website with ACF. If you run into any difficulties, there are several places you can find help:

  • Our extensive documentation contains references and guides for most situations you may encounter
  • We have an active and friendly community on our Community Forums who may be able to help you figure out the ‘how-tos’ of the ACF world.
  • The support professionals on our Help Desk will assist with your more in depth, technical challenges
  • The WordPress professionals at Codeable can provide coding support if you’re starting to feel out of your depth.

Support is provided for free to everyone, without any bias to customers or beginners. Because this support service is provided for free, please take this into consideration when creating a ticket and waiting for a reply.

Please research your issue and read the relevant documentation before asking a question. This will help free up our support team and allow for faster development on the plugin which we all love.

If you have a question about ACF, our collection of documentation articles should always be your first stop.

We are constantly updating and expanding the documentation, based on your feedback, to try and anticipate any questions or difficulties you may have.

The documentation contains detailed technical descriptions and code examples for:

  • ,
  • ,
  • , and

The documentation also contains dozens of friendly , covering topics from , to how to debug your code.

If you’ve been through the documentation, and you’re looking for advice on how to use ACF to accomplish a specific task, our Community Forums would be a great next stop.

The chances are that if you’re looking to do something with ACF, someone before you has probably faced a similar challenge, and their solution may already be in the forums.

If there isn’t already a thread containing an answer to your question, you can create a new one, and one of the friendly fellow developers who hang around the forum will probably be able to point you in the right direction.

You can also use the forums to throw around new ideas, discuss ACF related plugins, and earn some good karma by sharing your knowledge with the community.

The friendly folks on the help desk will do their utmost to help you solve any problems that are ACF related, but please note, we may not always be able to help with issues that are caused by custom theme code, or conflicts and incompatibilities with other plugins.

We aim to answer your questions within 24 hours, with the exception of weekends and Australian holidays (because, mate, we’re probably throwing a shrimp on the barbie or cuddling a koala).

If you’re looking for a developer to help you write some custom code that involves ACF, we’ve been pretty impressed with the folks from Codeable. They have a roster of vetted developers who have specific expertise in WordPress and ACF.

Plus, they’re giving ACF users a USD$60 voucher (worth an hour of coding) if you get in touch through us.

Setup

With the starter-kit downloaded and extracted, the next step is to setup the basic configuring for your field type plugin.

The starter-kit uses placeholders (such as ) throughout the folders, files names and code. Use the following list of placeholders to do a “find and replace” on each file’s name and contents.

Name Description Example
Short single word used in class names to avoid conflicts. “my”
Single word, no spaces. Underscores allowed. “icon_picker”
Slug friendly version of the above used for folder and file names. “icon-picker”
Multiple words, can include spaces, visible when selecting a field type. “Icon Picker”
Unique identifier for retrieving translated strings. For best compatibility with wordpress.org, please use your plugin slug (plugin folder name). eg. acf-FIELD-NAME “acf-icon-picker”
Url to the github or WordPress repository.
Comma seperated list of relevant tags used for search results on wordpress.org
Brief description of the field type, no longer than 2 lines.
Extended description of the field type.
Name or wordpress.org username of the author
URL to author’s website

After all placeholders have been modified, you should be left with a plugin containing all the logic for a custom field type! Before diving into any code, first copy this plugin into your WordPress plugins folder (wp-content/plugins) and activate it.

Notes

Data structure

The clone field does not change the data structure when saving values to the DB. The only change comes from the ‘Prepend field name’ setting. Values are not saved as an array, but are saved as normal individual field values. This means that meta queries are possible as per normal.

Data conflicts

It is possible to create data conflicts by cloning a field with a name already used in the group. This is the same issue as creating 2 fields using the same name. Please use the ‘Prefix Field Names’ setting when appropriate to avoid this.


A good rule of thumb is to use the ‘Prefix Field Names’ setting when choosing the ‘Group’ display setting, and the opposite when using the ‘Seamless’ group setting.

Disabled field groups

It is possible to clone a field group that has is set to ‘Disabled’. Disabling a field group prevents it from being loaded on a post edit page, which is a good idea when making ‘module’ groups.

Cloning a clone

It is possible to clone a clone field. This may sound extreme, but it can be a useful feature in specific scenarios. For example, you may be creating a page builder with the flexible content field and find that each layout contains the same ‘settings’ fields. Instead of duplicating these ‘settings’ fields in each layout (and the headache of maintaining changes to these fields across multiple layouts), you could define all ‘settings’ fields in the first layout only. The second layout could use a clone field to clone these ‘settings’ fields. The third layout could use a clone field to clone the one defined in the second layout.

The benefit of this is that if you add a new ‘setting’ to the first layout, you only need to update the clone field in your second layout. All other clone fields (in layout 3, 4, etc) will mimic this and show the new ‘settings’ field!

Notes

Displaying within an AJAX modal

When displaying an ACF form within an AJAX modal (or any other dynamically appended method), please note that the page will require some extra PHP and JavaScript code.

  • PHP The following function must be run within the tags and before the “wp_footer” action. This will create a hidden WYSIWYG field and enqueue the required JS templates for the WP media popups.

  • JS The following JS must be run after the AJAX request has completed and new HTML (containing the ACF form) has been appended to the DOM. This will allow ACF to initialize the fields within the newly added HTML.

acf_form_head()

It is important to note that whilst the function will display a form, it will not process the form when submit. This task is handled by another function called . To allow the form to save data, you will need to place the function at the top of your page template before any HTML is rendered.

Security

Since version 5.6.5, ACF uses the wp_kses_post() function to sanitize content and strip out evil scripts. This sanitization can be disabled if needed by changing the form’s setting to false.

Fine Print

Modifications to this policy

If any future changes to these Terms of Service are unacceptable to you or cause you to no longer be in compliance, you must immediately stop using the ACF Service. Your continued use of the ACF Service following any revision to this Agreement constitutes your complete acceptance of any and all such changes.

Entire Agreement

These Terms, together with our other policies make up the entire agreement and supersede all prior agreements, representations, and understandings.

Nice work! You’ve reached the end. Thanks for taking the time to learn about ACF’s policies.

Updated May 21, 2018

Limitations

The clone field contains a few limitations. These limitations are found in edge cases when using clone fields within a repeater or flexible content field.

1. multiple cloned sub fields

A cloned sub field may not be able to save it’s value if it exists alongside another instance of itself. For example, imagine a repeater field (called ‘Row’) containing 2 clone fields both cloning in the same field (called ‘Cell’). Even if both clone fields use the ‘Prefix Name’ setting to make each ‘Cell’ have a unique name, they both use the same field_key, so they will override each-other during save.

2. have_rows() nested clone field

The have_rows() function will return false when loading a cloned sub field using the ‘Display = Block’ setting. Please note that using the ‘Seamless’ display setting will allow sub have_rows() loops to work as expected.

Customize

With your new field type activated and available for selection, it’s time to customize the UI and functionality.

All logic for your field’s appearance and functionality is defined in the file. This class is packed full of powerful functions which allow you to customize how data is saved and displayed! Each function is documented with internal comments, so it is best to open up the file and read it over top to bottom. Please note that most functions are commented out. This allows you to un-comment and use only the functions that you need.

Here is a quick overview of the functions:

Name Description
Initialize function which sets the field’s data such as name, label, category and defaults
Create extra settings for your field. These are visible when editing a field
Create the HTML interface for your field
Enqueue CSS + JavaScript to assist your render_field() function
Add inline CSS and JavaScript to assist your render_field() function
Add hidden inline HTML
Add inline CSS and JavaScript to assist your render_field() function
This filter is applied to the $value after it is loaded from the db
This filter is applied to the $value before it is saved in the db
This filter is applied to the $value before being returned to template API
This filter is used to perform validation on the value prior to saving
This action is fired after a value has been deleted from the db

The above are only some of the functions available in the acf_field class. Please read over the extended comments found above each function to learn more.

Features

PHP Environment

ACF blocks is a PHP framework and does not require any JavaScript. This differentiates itself from the WordPress block API which relies heavily on modern JavaScript techniques, syntax and build tools.

Simple Templating

Similar to WP theme development, ACF blocks are rendered using a PHP template file or callback function allowing full control over the output HTML.

Custom Fields Compatible

ACF blocks offer full compatibility with all field types including both the Repeater and Clone fields!

It’s a similar story for template functions too. Whether you are loading a field value via , or looping over a Repeater field using , the experience remains familiar and consistent to regular theme development.

Live Previews

Content changes, and so do block previews! When editing an ACF block, the HTML will update in the backend giving you a real time preview of your content.

Native Compatibility

Believe it or not, ACF blocks maintain native compatibility with WordPress core. This allows features such as “alignment”, “anchor” and “re-usable blocks” to work!

Type specific fields

Field settings can also be added to specific types (text, image, etc). The following example shows how to add a new setting called ‘exclude words’ to all textarea fields which will add an extra text input allowing specific words to be checked during validation.

1. Adding the setting

A field type specific setting can be added using the action and the function . The following snippet will add a setting. Please note that the third parameter for is excluded making it specific to .

functions.php

2. Using the setting

With the new ‘exclude_words’ setting added and a new textarea field added (using the setting), we can hook into any part of ACF and use the setting. The following code will hook into the filter which is run during validation. This will allow us to check if the current value contains any words from the ‘exclude list’ and notify the user via a validation error message.

functions.php

3. Testing the setting

With the above code added to the functions.php file and a field using the ‘exclude_words’ setting, we can now edit a post and attempt to save a value.

ACF 5.7.11

A bug was reported where consecutive calls would use the same cached value even if the site was switched via .

Status: Solved. Please re-download the ACF PRO plugin files.

A bug within the post_template location rule class caused incorrect choices to appear in the location rule dropdown. Choices were displayed as “Template Title” => “template-file-name.php” instead of “template-file-name.php” => “Template Title”.

Status: Solved. Please re-download the ACF PRO plugin files.

A bug found in the text and textarea field validation function caused an incorrect character count when validating a value containing special characters.

Status: Solved. Please re-download the ACF PRO plugin files.

A bug found in the “Local Fields” logic caused all metaboxes to appear in reverse order.

Status: Solved. Please re-download the ACF PRO plugin files.

A bug found in the function caused issues when copying meta values for revisions and previews. This bug affected serialized array values and caused the flexible content field to appear empty when previewing or restoring a revision.

Status: Solved. Please re-download the ACF PRO plugin files.

A bug found in the function prevented a field from being loaded by it’s key.

Status: Solved. Please re-download the ACF PRO plugin files.

A bug found in the function caused incorrect values to be returned for some sub fields. This issue was seen most when a sub field existed with a “name” value equal to a “field type” such as “text” or “image”.


Status: Solved. Please re-download the ACF PRO plugin files.

A bug found in the logic for syncing field groups (from Local JSON) caused the imported fields to lose their children.

Status: Solved. Please re-download the ACF PRO plugin files.

A bug found in function caused values from the Options Page to be incorrectly escaped causing multiple backslashes.

Status: Solved. Please re-download the ACF PRO plugin files.

The function was accidentally removed.

Status: Solved. Please re-download the ACF PRO plugin files.

FAQ

No. Metaboxes are still an important part of the content editing and theme development process. In fact, ACF will continue to utilize them as the primary tool for saving content.

Yes. You can make changes to your field group and fields at any time. Making changes like this will not cause any damage to already existing blocks.

Yes. You can make changes to your block template or callback function at any time. ACF blocks are 100% dynamic meaning that they are rendered by the server each time they are loaded. This allows changes to block templates to be applied all existing block content.

Yes. There are many scenarios where a block does not require any fields, such as a “latest post” block.

No. Contrary to our original post back in 2018, ACF blocks is only included in our professional version. This decision to go “Pro only” came after realising the amount of time and attention this feature will require over the coming years.

No. The ACF blocks framework is 100% PHP. If your block requires some JS for added functionality (a carousel slider for example), you can add this also.

WordPress saves block data as HTML comments in the post_content. ACF blocks follow suit and save their data as a JSON object within that HTML comment.

Yes and No. Unlike loading a value from a post or user, block values are saved in the block HTML comment found within the post_content. This prevents the parameter from working as expected in our template functions. You can, however, load the post_content of a given post, and then parse the blocks using the function.

Not yet. We are currently experimenting in this area and hope to roll out support for native block components in the future.

Introduced in WordPress 5.0, the block-based editor “Gutenberg” has transformed the way content is created. Content is now created in the unit of blocks instead of freeform text. Blocks take various forms including Paragraphs, Headings, Media and Embeds.

Getting Started

The ACF Blocks framework performs a lot of “magic” behind the scenes to offer an intuitive development experience. We’ve simplified the process down to just three steps:

1. Register a Block

Similar to registering a post type, the acf_register_block_type() function allows you to register a custom block type from your functions.php file. This function accepts an array of settings that you can use to customize your block including a name, description and more.

This example only uses a small handful of the available settings so please be sure to read the acf_register_block_type() docs for a full list.

2. Create a Field Group

The next step is to create a field group for your block. Note that any and all ACF fields can be used within your block – there are no limitations!

That said, we don’t recommend using complex or large amounts of fields. Keep your blocks as lightweight and simple as possible.

From the location rules, use the “Block” rule to select your newly registered block type.

3. Render the Block

Lastly, you’ll need to tell ACF how to render the block, which is essentially the same process you’re used to for displaying custom fields.

This is done by creating a template file within your theme that matches the render_template setting used when registering the block. In this example, the template file will be called ‘template-parts/blocks/testimonial/testimonial.php’.

There are multiple ways to render a block. Please read the acf_register_block_type() docs for a full description on the render_template and render_callback settings.

One very exciting feature of ACF Blocks is that all the ACF API function such as , and will work as expected!

template-parts/blocks/testimonial/testimonial.php

The only thing we haven’t included is the enqueuing of styles/scripts which can easily be done via the enqueue_style, enqueue_script and enqueue_assets settings available in the acf_register_block_type documentation.

That’s all there is to it! You can immediately start using your new block within Gutenberg and place it anywhere within your content .

Updates Questions

Yes, updates are free. Whether you’re using the free version or ACF PRO, you can keep your plugin up to date at no extra cost.

ACF can be updated either via one-click update or manually. When an update becomes available, you will receive a notification on your Plugins page.

To apply the update via one-click update, simply click ‘update now’ in the notification on the Plugins page.

To update manually, you can download the new version of the plugin from the WordPress plugin repository. You can then safely delete the plugin directory on your server, and upload the new version via FTP.

For more details please see our guide: How to update

ACF PRO can also be updated via one-click update or manually. When an update becomes available, you will receive a notification on your Plugins page.

To apply the update via one-click update, simply click ‘update now’ in the notification on the Plugins page.

If you want to update manually, you’ll need to download the latest version from your store account.

For more details please see our guide: How to update

If you’ve upgraded from version 4 to version 5 of ACF and you can’t see you fields, first of all, don’t panic! Version 5 uses a different data structure so they might not be visible, but your fields and their values are still there.

You should see a database upgrade prompt at the top of the page on your WordPress dashboard. All you need to do is click the button to run the database upgrade process. Your fields should re-ppear once that process has been completed

If you’re still having difficulties, please get in touch.

For some reason, the database upgrade process may not have triggered as expected when the new version was installed. To make this happen again, please ensure version 5 is activated and follow this procedure:

  1. Back up your database.
  2. In your wp_options table, please set the acf_version value back to the latest version you had installed ( something like 4.4.11 )
  3. Reload the wp-admin dashboard
  4. Click the database upgrade button that appears

If you’re still having troubles, please contact support.


In some hosting environments, communication may not be possible between your server and the WordPress update server. If this happens to you , please note any error messages you find, and contact support.

If you’d like to go back to an earlier version of ACF, we’d recommend using this rollback plugin, which is available from the WordPress repository.

Although we’re not associated with this plugin in any way, we have had reports of ACF users employing it successfully.

All the previous version of ACF PRO are available for download from the downloads section of your ACF store account. To start rolling back, you’ll need to login, download and unzip the version you’d like to rollback to.

Then, on your website, you’ll need to deactivate and delete the version you’re currently running on the _Plugins_ page.

Finally, you’ll need to upload the older version to your wp-content/plugins directory. Once the older version of ACF PRO is uploaded, you will need to activate again it by finding it in the list on the _Plugins_ page in your site’s Administration area, and clicking on the ‘Activate’ link.

Gutenberg Issues

A bug exists within the Classic Editor plugin causing a WSOD (White Screen of Death) when editing a field group. This issue has been reported to the Classic Editor here.

Status: Solved. Please update Classic Editor to version 1.1.

All field groups created with the Advanced Custom Fields plugin are shown as empty visible metaboxes when editing a post irrelevant of those field group’s location rules.

This is due to a decision in Gutenberg to override the CSS that ACF adds to “placeholder” metaboxes – used to update metaboxes dynamically whilst editing the post.

Status: This is a that has been bumped to WordPress 5.0.1.

All field groups shown in the “content area” look awkward, detached and slightly broken. More care should have gone into the styling of metaboxes to avoid such a disjointed UI and UX.

Status: This is also a known issue that has been bumped to WordPress 5.0.1.

One of our favorite, simple and intuitive features is the ability to update metaboxes dynamically whilst editing a post. For example, metaboxes will hide and show depending on location rules when changing the post template, format, parent and other post attributes.

Due to the huge and complex changes to the post edit page, our dynamic screen check no longer works.

Status: We will be working hard to get this fixed in ACF 5.8

Another highly used feature in ACF is our AJAX powered validation. This allows developers to highly customize the validation process via PHP whist providing convenient feedback to the user when a field value does not meet its requirements.

Status: Similar to above, this feature is no longer working and is scheduled to be fixed in ACF 5.8.

General Issues

This issue can occur when activating or updating the ACF PRO plugin. The following message will appear in an error notice at the top of the admin page:

Error. Could not connect to update server (cURL error 51: SSL: certificate subject name ‘*.sgvps.net’ does not match target host name ‘connect.advancedcustomfields.com’).

This problem is caused by a mixture of our ACF web host’s server setup (siteground) and your server’s SNI/TLS settings. The issue can be solved either of the following:

1. Web host: If possible, ask your web host to update the cURL version to one which supports SNI. 2. WP: Use the https_ssl_verify filter to avoid the SSL detection (code snippet below)

Download

To make life easier, we put together a comprehensive starter-kit for creating an ACF field type. This starter-kit contains all the necessary files to create a WP plugin and is heavily commented so you can build your field type quickly and confidently!

Field Type Template on Github

Please download a copy of the ACF field type template starter-kit from this Github repository (Click the Green Download Zip button).

https://github.com/AdvancedCustomFields/acf-field-type-template

Once downloaded, take a look around. Here is a list of the files and folders included.

Name Description
acf-FIELD-NAME The plugin folder.
/assets The folder for including assets. This folder contains 3 sub folders called css, js and images. These can be modified, renamed or removed.
/fields The folder for field class files. Each major version of ACF has introduced improvements to the acf_field class which are not always backwards compatible. This folder contains 2 field class files for ACF-v4 and ACF-v5.
/lang The folder for translation files (.pot, .po, .mo).
/acf-FIELD-NAME.php The main plugin file. This file contains plugin meta information, defines settings and includes the relevant field class file.
/README.md A simple readme file for your Github repository
/readme.txt A simple readme file for your WP plugin

Installation Questions

Installing ACF is just like installing any other WordPress plugin.

You can install it manually by downloading it from the WordPress Plugins Directory, and then FTP it to your site’s plugins directory. Once ACF is uploaded, you will need to activate it by finding it in the list on the _Plugins_ page in your site’s Administration area, and clicking on the ‘Activate’ link.

Or you can install it automatically by searching for ‘Advanced Custom Fields’ under _Plugins > Add New_ in your site’s Administration area. When you have found ACF in the search results, click on the ‘Install Now’ button. If the installation is successful remember to click the ‘Activate Plugin’ button to complete the process.

ACF is successfully installed and activated if your Administration menu has an entry called Custom Fields.

For a step by step guide to installation, click here.

ACF PRO is only available for download from the downloads section of your ACF store account.

As a result, ACF PRO must be installed via FTP. Unzip the file you have downloaded, and upload the folder called ‘advanced-custom-fields-pro’ to your wp-content/plugins directory. Once ACF PRO is uploaded, you will need to activate it by finding it in the list on the _Plugins_ page in your site’s Administration area, and clicking on the ‘Activate’ link.

To enable your lifetime of automatic upgrades, you’ll need to enter your license key under Custom Fields > Updates, and click ‘Activate’.

We can’t imagine why you’d want to, but you most certainly can uninstall ACF.

The first step will be to locate any ACF specific code in both your theme’s functions.php file, or its template files. For your references, you can find a list of ACF specific , and in the documentation.

You’ll need to deactivate ACF by clicking on the ‘Deactivate’ link on the Plugins page, followed by the link.

This will remove all of the plugin’s files from the WordPress plugins directory.

Simply deactivating or uninstalling ACF will not affect any of the data you’ve created while using the plugin.

This means that the data will continue to be available throughout your site even if the plugin is no longer functioning.

Please note, however, if you are using ACF specific functions such as the_field() or get_field() to access this data in your plugin or template files, these functions will no longer exist, and your website will no longer function as expected.

Because your field data remains intact after deactivation, you should be able to reinstall ACF or ACF PRO and pick up where you left off.

Simply follow the steps outlined above.

If you run into any troubles, please get in touch with support.

With ACF or ACF PRO successfully installed, you should probably ()!


С этим читают