-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Composer 2.0 support #44
Comments
Hi, This plugin is more or less abandoned, the last change was mid 2017. pivvenit/acf-pro-installer The first one is a fork/rewrite of this plugin that is composer 2.0 and PHP8 compatible . You can use it in the same way as this plugin, or (as I would recommend) using our composer repository as described in the documentation. This enables you to actually use semver ranges, and to have tools like dependabot automatically update your ACF version. The second one is Composer 2 and php8 compatible as well. It's main advantage is that it supports arbitrary private packages. However since you have specify the URL of the package to download (including version), tools like dependabot won't work. Both plugins have active maintainers, and are supported for the forseeable future. Disclaimer: I'm the author of pivvenit/acf-pro-installer. I believe i've described both plugins objectively, but if anyone has something to add, feel free to respond :) |
I think you described the status quo very well :) Disclaimer: I'm the author of the other package. |
I'm actually laughing so hard at the exchange above. Thanks for the help! |
I had a good experience with https://github.com/junaidbhura/composer-wp-pro-plugins. |
Hi there!
My usage broke today since it seems not to be compatible anymore with composer 2.0. See the following log:
The "philippbaschke/acf-pro-installer" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
Any ideas on a quick fix?
The text was updated successfully, but these errors were encountered: