acf-pro-installer: HTTP/1.1 400 Bad Request

I have a similar issue as described in issue #5.

I’ve added the following code to the composer.json file that’s in the root of my theme

"repositories": [ { "type": "package", "package": { "name": "advanced-custom-fields/advanced-custom-fields-pro", "version": "5.3.10", "type": "wordpress-plugin", "dist": { "type": "zip", "url": "https://connect.advancedcustomfields.com/index.php?p=pro&a=download" }, "require": { "philippbaschke/acf-pro-installer": "^1.0", "composer/installers": "^1.0" } } } ],

I then added the ACF_PRO_KEY variable (with key) to the .env file.

Then when I run the command composer require advanced-custom-fields/advanced-custom-fields-pro:*, I get the following error message: [Composer\Downloader\TransportException] The 'https://connect.advancedcustomfields.com/index.php?p=pro&a=download&t=5.3.10&k=b3jk...' URL could not be accessed: HTTP/1.1 400 Bad Request

My composer version is: composer --version Composer version 1.4-dev 2017-01-22 19:01:35

When checking the url (with and without the GET params) in Chrome’s Postman I get the same 400 Bad Request error.

What is causing this issue and how can I fix this?

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 22 (9 by maintainers)

Most upvoted comments

Hey @codilechasseur and @PhilippBaschke - I am still getting the same error even with composer cache cleared. Just performed a test and it fails with the t=5.3.9 parameter, but downloads as expected when removed. Have you been able to get this working successfully?

timalbert on Jun 9, 2017

For anyone having issues right now with this. It looks like ACF has broken the “t=” part of their download URL. Tested from composer, browser and from the account dashboard of ACF’s site.

BROKEN https://connect.advancedcustomfields.com/index.php?p=pro&a=download&k={ACF_PRO_KEY}&t=5.5.14

WORKS https://connect.advancedcustomfields.com/index.php?p=pro&a=download&k={ACF_PRO_KEY}

codilechasseur on Jun 5, 2017

Super strange yes. I only had this problem on server when running deploy.

I ran the deploy again to get the composer error message for you but I ran into other issues with the deploy.

I upgraded wp-cli from v0.24.1 to v1.1.0 to fix the issue with the deploy and ran it again. Successfully. And the ACF key was added aswell.

My issue on this server seems to be resolved. Thanks for all your help and taking you time with this.

slackday on Apr 7, 2017

That is super strange 😱 Would you mind clearing the composer files, installing again and then show me the console output of the install step?

In your project directory

$ rm composer.lock
$ rm -rf vendor
$ composer clearcache
$ composer install

PhilippBaschke on Apr 6, 2017