Just to echo what Liam said, this was due to an API issue and impacted any ACF PRO customer, both lifetime and subscription license holders.
This has been fixed in ACF 6.1.7 🙌
https://www.advancedcustomfields.com/blog/acf-6-1-7/
Hey folks, we have just released native support for installing ACF PRO with Composer, without the need for another package or installer 🙌
👉 https://www.advancedcustomfields.com/resources/installing-acf-pro-with-composer/
Hey all, just to let you know we added this feature in ACF 6.0.3 🙌
Thanks @luckyfella73 – this will be fixed in the next release 👍
Hey @willryanuk – the new pagination setting for the Repeater field in ACF 6.0 should help with this issue. https://www.advancedcustomfields.com/blog/acf-6-0-released/#repeater-pagination
Hey all 👋
As part of the ACF 5.11 release we added native support for ACF fields in the WordPress REST API. Read more about that here.
@madebytincans Yes, exactly like @squarecandy says. Putting it somewhere other than wp-config.php would be specific to each setup, eg. using .env files with Bedrock.
I’m pleased to say that this has now been implemented as part of ACF PRO 5.11 🙌
ACF will now look for and use a PHP constant named ACF_PRO_LICENSE
, which you can define with your license key.
define('ACF_PRO_LICENSE', 'yourkeyhere' );
This can be done in the wp-config.php file or any other file that WordPress runs before it loads the ACF PRO plugin. For more details, check out our guide on how to activate the ACF PRO plugin.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.