Error running composer install

[jdelia]

I receive an error after checking out 2.0.0-dev branch and run composer install https://cl.ly/2i203o2w0g2T

Expected Behavior

Thought I would load a fresh copy of UPRO 2.0 to have a look at the blog page template issue.

Current Behavior

This is a fresh install for 2.0.0-dev - tried running composer install first. Received the error. Ran npm install and that finished without error.

Possible Solution

Not sure what is wrong.

Steps to Reproduce (for bugs)

1. create a fresh genesis install
2. clone the repo, fetch and checkout 2.0.0-dev
3. run composer install
4. see this error:

[utility-pro] (2.0.0-dev)$ composer install Loading composer repositories with package information Installing dependencies (including require-dev) from lock file Nothing to install or update Generating autoload files

"vendor/bin/phpcs" --config-set installed_paths ../../wp-coding-standards/wpcs PHP Fatal error: Uncaught Error: Call to undefined function did_action() in /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/tgmpa/tgm-plu gin-activation/class-tgm-plugin-activation.php:2109 Stack trace:

0 /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/composer/autoload_real.php(66): require()

1 /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/composer/autoload_real.php(56): composerRequire77a62ca96cd94535a00b72d63329e908('a5f882

d89ab791a...', '/Users/loneduch...')

2 /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/autoload.php(7): ComposerAutoloaderInit77a62ca96cd94535a00b72d63329e908::getLoader()

3 /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/squizlabs/php_codesniffer/CodeSniffer/CLI.php(27): include_once('/Users/loneduch...')

4 /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/the in /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/tgmpa/tgm-plu

gin-activation/class-tgm-plugin-activation.php on line 2109

Fatal error: Uncaught Error: Call to undefined function did_action() in /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/tgmpa/tgm-plugin-a ctivation/class-tgm-plugin-activation.php:2109 Stack trace:

0 /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/composer/autoload_real.php(66): require()

1 /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/composer/autoload_real.php(56): composerRequire77a62ca96cd94535a00b72d63329e908('a5f882

d89ab791a...', '/Users/loneduch...')

2 /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/autoload.php(7): ComposerAutoloaderInit77a62ca96cd94535a00b72d63329e908::getLoader()

3 /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/squizlabs/php_codesniffer/CodeSniffer/CLI.php(27): include_once('/Users/loneduch...')

4 /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/the in /Users/loneduchess/Local Sites/utility-pro-2/app/public/wp-content/themes/utility-pro/vendor/tgmpa/tgm-plu

gin-activation/class-tgm-plugin-activation.php on line 2109 Script "vendor/bin/phpcs" --config-set installed_paths ../../wp-coding-standards/wpcs handling the install-standards event returned with error code 255

Context

Unable to proceed.

Your Environment

• Version used:
• Environment name and version (e.g. PHP 7.0): PHP 7.0.3
• Server type and version (e.g. nginx 1.9.1): nginx
• Operating System and version (or Host and package): OS Sierra / Local by Flywheel
• Link to your project:

[gspice]

My Environment

The same as Jackie's, using Local with PHP 7.0.3 , WordPress 4.8, nginx server

My Steps and Results (a little different)

• Clean install of Genesis
• Downloaded zip of the issue assigned to me to test #76
• Unzipped theme folder in /themes folder for the site
• Navigated to theme folder in Terminal, typed composer install
• Received the Mac error -bash: composer: command not found
• Installed composer again using npm both locally and globally but received the same error, Google'd and found articles saying it's because you're missing the composer.phar file. I ran a manual process to install then tried again.
• Entered composer install, received the same error -bash: composer: command not found
• Read article that said to use the php command, tried php composer install, received new error could not open input file: composer
• Next tried php composer.phar install and received a long list of errors, the first saying Problem 1 - This package requires php ^7.0 but your PHP version (5.6.30) does not satisfy that requirement. which doesn't make sense since I am running 7.0.3 for this install.
• Next step, manually installed all of the gulp packages it asked for until typing gulp ran without asking for a missing module. It ran through quite a bit then broke on this error, which I'm guessing is from missing files yet to be installed or a misread of the php version, here is the top snippet of the error:

/Users/Ginger/Local Sites/upro2/app/public/wp-content/themes/utility-pro-2.0.0-dev/node_modules/gulp-wp-pot/index.js:54 contents: Buffer.from(potContents) TypeError: this is not a typed array. at Function.from (native) at DestroyableTransform._flush (/Users/Ginger/Local Sites/upro2/app/public/wp-content/themes/utility-pro-2.0.0-dev/node_modules/gulp-wp-pot/index.js:54:24) at DestroyableTransform.<anonymous> (/Users/Ginger/Local Sites/upro2/app/public/wp-content/themes/utility-pro-2.0.0-dev/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:138:49) at DestroyableTransform.g (events.js:260:16) at emitNone (events.js:67:13) at DestroyableTransform.emit (events.js:166:7)

Context

At this point, I am stalled until I can learn further instructions.

[GaryJones]

Will look more and post better instructions tomorrow, but Ginger's is due to Local not supporting Composer by default, and then running it from her machine, instead of right-click -> Open in SSH (which would then use the right version of PHP). Not the fault of UP2.

Jackie's looks like it's pulling down not-the-right version of TGMPA, where we've fixed a recent global call. Replace it was develop branch, which includes a return, and the post install composer script should work fine.

[GaryJones]

Right click the site and Open in SSH. Then:

apt-get update && apt-get install -y wget
wget -qO- https://getcomposer.org/installer | php
mv composer.phar /usr/local/bin/composer

The Local SSH needs some prep work.

# Allow Code Standards to be installed
cd /app/public/wp-content/themes/utility-pro/vendor/squizlabs/php_codensniffer
chmod 666 CodeSniffer.conf

# Install sudo, curl, git and apt-transport-https packages.
apt-get install sudo curl git apt-transport-https

# Add repo for Node.JS 8.
curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -

# Install Node.JS 8 and npm.
sudo apt-get install -y nodejs

# Optionally, add repo for Yarn (alternative for npm).
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list

# Optionally install Yarn.
sudo apt-get install yarn

# Tidy up any un-needed libraries.
apt-get autoremove

Now you should be able to:

cd app/public/wp-content/themes/utility-pro
composer install

[jdelia]

@GaryJones Thanks for this. I will run through this again over the weekend and see if I can get things working properly.

[gspice]

Same here: I will be able to focus better on getting this working over the weekend.

[gspice]

@GaryJones Thank you for your detailed instructions!

My steps today:

• I completed the area in the black.
• When running this section: "The Local SSH needs some prep work." I did not have a vendor folder yet so I ran composer install and even though it had some errors, it created the vendor folder and the squizlabs/php_codensniffer folder so I was able to proceed.
• On this entry chmod 666 CodeSniffer.conf I did not have that file but I did have CodeSniffer.conf.dist so I used that.
• I received a few errors on the Yarn entries.
• At the end I ran composer install again and it ran, albeit with a few errors.
• I went back to the WP dashboard and was able to activate the theme without receiving fatal errors which had happened previously, yay!
• That said, when I view the console have a few errors:

Also attaching my full SSH window contents for reference: Terminal-Saved-Output.txt

[GaryJones]

@gspice I don't think you pulled down the latest version of UP 2.0.0-dev before starting, as your output (useful to include, thanks!) shows you have TGMPA 2.6.1 instead of the develop branch.

[gspice]

@GaryJones You are correct, I had the previous develop branch, this time I downloaded 2.0.0-dev.

Steps and results today:

• Using the newer branch, my output matched yours in the black area above except for an error on yard.
• No vendor folder, so ran composer install like before.
• Use CodeSniffer.conf.dist like before
• Ran composer install at the end, a few errors
• Tried to activate the theme and this time I could not since the style.css file wasn't generated.

Here's my terminal output:

Terminal-Saved-Output-July-23.txt

[GaryJones]

@gspice Still the same error.

Before doing a composer install, do a composer update, so that it updates the lock file. Right now, it still pulled down TGMPA 2.6.1, and not the dev-develop.

See the:

Error: Call to undefined function did_action() in /app/public/wp-content/themes/utility-pro-2.0.0-dev/vendor/tgmpa/tgm-plugin-activation/class-tgm-plugin-activation.php on line 2109

This was fixed by adding https://github.com/TGMPA/TGM-Plugin-Activation/blob/ec6a3f286e095facdabb19aa1b9e5f2794dddf51/class-tgm-plugin-activation.php#L35-L38 to the start of that TGMPA file.

I'll see about getting a new TGMPA release done this week.

Also, you could update your system PHP, and then use composer on your host machine (not inside Local's SSH) to do the composer actions.

[gspice]

@GaryJones I'm closer! :-)

• Found this article to update my Mac's PHP verison: https://coolestguidesontheplanet.com/upgrade-php-on-osx/
• Unfortunately I still had to use SSH, maybe it required a restart, not sure
• Ran through all the steps again , used composer update at the end of the black area
• Ran this step at the end of the list otherwise I received an error that it was locked, and the file wasn't present yet at the start: # Allow Code Standards to be installed cd /app/public/wp-content/themes/utility-pro/vendor/squizlabs/php_codensniffer chmod 666 CodeSniffer.conf
• First time at the end I was able to run composer install and everything appeared to load, the style.css was generated.
• Able to activate the theme and no console errors, YAY!
• Next tried to run gulp at the theme root to activate the watch for CSS changes
• Received this error: Ginger-Coolidges-MacBook-Pro:utility-pro-2.0.0-dev Ginger$ gulp /Users/Ginger/Local Sites/upro2/app/public/wp-content/themes/utility-pro-2.0.0-dev/node_modules/node-sass/lib/binding.js:15 throw new Error(errors.missingBinary()); ^

Error: Missing binding /Users/Ginger/Local Sites/upro2/app/public/wp-content/themes/utility-pro-2.0.0-dev/node_modules/node-sass/vendor/darwin-x64-47/binding.node Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 5.x

Found bindings for the following environments:

• Linux 64-bit with Node.js 8.x

This usually happens because your environment has changed since running npm install. Run npm rebuild node-sass --force to build the binding for your current environment.

• Followed the instruction and ran npm rebuild node-sass --force
• This appeared to finish OK.
• Attempted to run gulp again, at the end received this error: /Users/Ginger/Local Sites/upro2/app/public/wp-content/themes/utility-pro-2.0.0-dev/node_modules/gulp-wp-pot/index.js:54 contents: Buffer.from(potContents), ^ TypeError: this is not a typed array. at Function.from (native)

[GaryJones]

The npm rebuild should be a one-off task, each time you update Node.

The gulp-wp-pot issue can be reported at https://github.com/rasmusbe/gulp-wp-pot to see if they can identify the issue.

[cdils]

@jdelia I'm closing this out. I'll upload a fresh branch for testing before Monday and please create a new issue if the problem persists.