Unsupported repo, here's a replacement

[davidrhoderick]

Hello future user looking for a composer installer of premium WordPress plugins. I was greeted by this repository multiple times via Google search, which was frustrating because it is no longer supported and no longer works.

However, if you are looking for a working repo to solve this issue, look to https://github.com/ffraenz/private-composer-installer for help. This will work as of my posting.

[schliflo]

I'd highly suggest using https://github.com/pivvenit/acf-composer-bridge instead of ffraenz/private-composer-installer as it supports updating ACF through composer as well as some other nifty things.

[timnolte]

Neither of these alternatives work for me with as they are no drop-in replacements for this one, and they cause additional dependency conflicts that are not easily resolved. The acf-composer-bridge might have been an option but it went off the rails on what key it's looking for instead of using the widely used ACF_PRO_KEY variable.

[Qrious]

Neither of these alternatives work for me with as they are no drop-in replacements for this one, and they cause additional dependency conflicts that are not easily resolved. The acf-composer-bridge might have been an option but it went off the rails on what key it's looking for instead of using the widely used ACF_PRO_KEY variable.

@timnolte We (pivvenit/acf-pro-installer) support the (default) ACF_PRO_KEY environment variable. I'm interested in your problem, could you please create an issue at our repository (in order not to hijack this issue). Thanks in advance :)

[timnolte]

Neither of these alternatives work for me with as they are no drop-in replacements for this one, and they cause additional dependency conflicts that are not easily resolved. The acf-composer-bridge might have been an option but it went off the rails on what key it's looking for instead of using the widely used ACF_PRO_KEY variable.

@timnolte We (pivvenit/acf-pro-installer) support the (default) ACF_PRO_KEY environment variable. I'm interested in your problem, could you please create an issue at our repository (in order not to hijack this issue). Thanks in advance :)

@Qrious We've decided to land on a single resolution to solve all of our premium plugin management with Composer using a SatisPress instance with authentication. This allows us to keep things working regardless if the plugin vendor changes their distribution method.