Remove ACF Pro from examples now that they support native Composer integration?

[jeffwidman]

Want to remove ACF Pro from your examples now that they natively support composer integration?

• https://www.advancedcustomfields.com/resources/installing-acf-pro-with-composer/
• https://github.com/pivvenit/acf-pro-installer#warning-deprecated-supported-till-1st-of-june-2023-warning

[szepeviktor]

Some people prefer proven solutions.
I may be using their Composer repository after a year, or later.

[mcaskill]

I recently contacted ACF Pro's vendor (WPEngine, at the time of writing). Important changes have occurred and more are in the works:

1. The URL for the ACF Pro example (/index.php?p=pro&a=download&k=***&t=X.Y.Z) is obsolete.
2. The new URL (/v2/plugins/download?p=pro&k=***&t=X.Y.Z) does not work with Composer (because the server checks the User-Agent for Composer for its Composer repository).
3. In the coming months, the vendor is changing its API to use server generated single-use URLs.
4. Even the URLs from the official Composer repository (/v2/plugins/composer_download?p=pro&t=X.Y.Z) will eventually adopt single-use URLs.

[szepeviktor]

Very well hard-coded user agent.
https://github.com/composer/composer/blob/685add70ec84d18075a202686288304db0d6d265/src/Composer/Util/StreamContextFactory.php#L119

[szepeviktor]

But maybe in the proxy settings!
https://getcomposer.org/doc/articles/authentication-for-private-packages.md#custom-token-authentication

[mcaskill]

If its possible to change the user-agent via proxy settings, that will only be practical for the short term. Eventually, the vendor will deploy single-use URLs (à la Easy Digital Downloads) which will require an intermediate request to retrieve the download URL.