To provide flexibility in implementation, let's not assume where we need to change directory to.

This came up in my testing of JPS v2 where I had symlinked my Jetpack directory to another copy of Jetpack in another WordPress installation. I was able to get around this by going one directory up and running the partner provision script.

By removing the cd command going one directory above jetapck to wp-content/plugins I was able to get the script to successfully run.

To test:

• Check out branch
• Run sh jetpack/bin/partner-provision.sh --partner_id={$id} --partner_secret={$secret} --plan={$plan} --url={$url} --user=1 with proper variables. See @gravityrail or @ebinnion for details
• Ensure next_url returned in response is a proper authorization URL