Hi!
No need to do that. My ACF version was 5.4.5, for some reason I didn’t get a notification about newer release, but that one is probably related to Composer.
As our project layouts are based on Bedrock, we manage plugins via composer (advantages include version control, click-free deployments etc.), but plugins that don’t officially support Composer are a bit tricky.
Here’s how we do it:
{
"repositories": [{
"type": "composer",
"url": "https://wpackagist.org"
}, {
"type": "composer",
"url": "https://wp-languages.github.io"
}, {
"type": "package",
"package": {
"name": "advanced-custom-fields/advanced-custom-fields-pro",
"version": "5.4.8",
"type": "wordpress-plugin",
"dist": {
"type": "zip",
"url": "https://connect.advancedcustomfields.com/index.php?p=pro&a=download&k=MY_SECRET_KEY"
}
}
}],
"require": {
"advanced-custom-fields/advanced-custom-fields-pro": "*",
}
}
So if you were to add proper Composer support, we could get automatic updates, and these kind of threads would never exist 😉 Currently we have to manually bumb the version number (or flush the composer cache) to get updates. Proper Composer support would mean that composer update would be enough.
We’re not the only ones missing this feature:
https://support.advancedcustomfields.com/forums/topic/composer-support/
https://support.advancedcustomfields.com/forums/topic/installing-acf5-via-composer/
So, this problem is solved. Bad version was the cause.
