Configuring cron using wp-cli on local server with Mamp Pro

Question

I'm testing CiviCRM 4.7 in a WordPress 4.4.2 installation. I'm running this on a local server with Mac OSX 10.11.2 using MAMP Pro.

I'm trying to configure cron using the wp-cli method. I've installed, renamed and moved wp-cli and running wp --info in /Applications/MAMP/bin gives

PHP binary: /usr/bin/php PHP version: 5.5.30 php.ini used:
WP-CLI root dir: phar://wp-cli.phar WP-CLI global config:
WP-CLI project config:
WP-CLI version: 0.22.0 Phils-MacBook-Air:bin phillip$

wp help shows the WordPress commands

I'm now trying to implement

/path/to/wp --user=<cron> --url=<http://example.com> --path=</path/to/wp> civicrm api job.execute auth=0

In my case I'm trying

/users/phillip/Sites/thetestsite.dev --user=<philnicholl> --url=<http://thetestsite.dev:8888> --path=</users/phillip/Sites/thetestsite.dev> civicrm api job.execute auth=0

but I get

-bash: philnicholl: No such file or directory

(philnicholl is my WordPress administrator username)

I know I'm missing something obvious.

I'm have experience with WordPress and Mamp Pro but am new to both CLI and CIVICRM. Any help would be much appreciated.

Thank you.

Answer 1

Here's an example wp-cli command I use that works:

/home/ubuntu/wp-cli/wp-cli --require=/home/ubuntu/wp-cli/civicrm.php --path=/var/www/wordpress civicrm api job.execute > /dev/null

I hope that helps!

UPDATE: I see your problem! "/path/to/wp" means, "path to wp-cli, including wp-cli". I completely looked past that part at the beginning, since that's not generally where the problems are found.

Usually, "wp-cli" is aliased to "wp" so it can automatically include the CiviCRM extension - but with cron, I usually just use the require directly.

So log into your computer and type which wp-cli. Let's say it returns /usr/bin/local/wp-cli. Replace ONLY the first path to WP with that, so it looks like:

To forestall your next question about why it doesn't work - the is a placeholder, and the angle brackets should NOT be included in the actual statement. Angle brackets are a common way in documentation of command-line programs to say, "insert your value here". So instead of <philnicoll>, just write philnicoll.

You should be left with something like:

/usr/bin/local/wp-cli --user=philnicholl --url=http://thetestsite.dev:8888 --path=/users/phillip/Sites/thetestsite.dev civicrm api job.execute auth=0