composer require wpengine/advanced-custom-fields-pro installs fine from connect.advancedcustomfields.com. But the package it pulls down declares this in its own composer.json:
{
"name": "wpengine/advanced-custom-fields",
"type": "wordpress-plugin"
}So the name inside the package doesn't match the name you distribute it under.
It bites going the other way. I'm migrating sites to a Composer-managed setup, so I read each installed plugin's composer.json to work out what to require. For ACF Pro that gives me wpengine/advanced-custom-fields, which isn't installable, so I special-case it back to -pro.
Any chance the Pro build could declare wpengine/advanced-custom-fields-pro in composer.json? Keeping the replace on the free name would avoid breaking anything else.
(Seen on 6.8.1.)
composer require wpengine/advanced-custom-fields-proinstalls fine from connect.advancedcustomfields.com. But the package it pulls down declares this in its own composer.json:{ "name": "wpengine/advanced-custom-fields", "type": "wordpress-plugin" }So the name inside the package doesn't match the name you distribute it under.
It bites going the other way. I'm migrating sites to a Composer-managed setup, so I read each installed plugin's composer.json to work out what to require. For ACF Pro that gives me
wpengine/advanced-custom-fields, which isn't installable, so I special-case it back to-pro.Any chance the Pro build could declare
wpengine/advanced-custom-fields-proin composer.json? Keeping thereplaceon the free name would avoid breaking anything else.(Seen on 6.8.1.)