composer conflict on flynt create

[bdebrie]

Since this Bedrock update roots/bedrock#412 the flynt create command is not working anymore because of a conflict during requireComposerPackages.

This comes from the fact that the philippbaschke/acf-pro-installer package that is explicitly requiring a ^2.2 version of phpdotenv, while bedrock asks for a ^3

It has already been reported and a PR is already available PhilippBaschke/acf-pro-installer#38, yet it seems that it is unclear if the repo is still alive and if this will get merged soon.

In the discussion someone created a new repo as an alternative, which supports phpdotenv ^3 https://github.com/ffraenz/private-composer-installer

[bdebrie]

Any thoughts or feedback regarding this ? @domtra @Qakulukiam

[nilsbosman]

I'm also running into this issue. Any status updates regarding this?

[bdebrie]

Hi @nilsbosman, from what I saw, this is not fixed. The workaround is to launch flynt create, and then go to composer.json after the installation fails. There you have to

• replace the advanced-custom-fields/advanced-custom-fields-pro with the following config.
  { "type": "package", "package": { "name": "advanced-custom-fields/advanced-custom-fields-pro", "version": "5.7.7", "type": "wordpress-plugin", "dist": { "type": "zip", "url": "https://connect.advancedcustomfields.com/index.php?a=download&p=pro&k={%PLUGIN_ACF_KEY}&t={%version}" }, "require": { "ffraenz/private-composer-installer": "^2.0", "composer/installers": "^1.0" } } },

• add ACF_PRO_KEY=yourkey to your env file

• manually run the flynt-cli commands that were not executed

[bdebrie]

The solution above was working two weeks ago but not anymore.

Easiest fix is to not put an acf pro key when the cli asks for it, and then manually add the acf plugin once the project is created.

[nilsbosman]

Hi @bdebrie, thanks for the help, for me it also didn't work. I'll try your new suggestion. However I did notice that they've changed the readme and it now says this repo is no longer under active development and refer to https://github.com/flyntwp/flynt with instructions on how to use the latest version of Flynt.

[domtra]

Hi @bdebrie and @nilsbosman,
the solution for broken acf pro installs on create should be to not provide a acf pro key, as @bdebrie stated. we actually never used this way of installing acf pro, so i cannot really give you feedback to this.

regarding the deprecation: we made some really big changes to the flynt-starter-theme. the result, ongoing in development but already used on a couple of production sites, can be found in the https://github.com/flyntwp/flynt. our goal was to simplify every aspect of flynt. the theme can actually be dropped into any wordpress installation, bedrock or regular, and it will work. so there is not really a need for the flynt-cli anymore. for migrating data between environment, the wp cli is really handy and some manual rsync.

we will keep you updated about the development. the only info about the new flynt is actually currently in the readme of the mentioned github repo. if you have any questions, feel free to ask.