alexc7018 / vvv-site-wizard

Automates setting up new WordPress sites in Varying Vagrant Vagrants
GNU General Public License v2.0
346 stars 47 forks source link

htdocs not being populated on new site install #31

Closed joelworsham closed 9 years ago

joelworsham commented 9 years ago

Sometimes when I install a new site, WordPress doesn't install into the htdocs, it just leaves it empty. I can't figure out why this would happen.

joelworsham commented 9 years ago

I think I found the issue, but I don't know how to resolve it.

Installing WordPress (release version) in test/htdocs... Downloading WordPress 4.0.1 (en_US)... Using cached file '/home/vagrant/.wp-cli/cache/core/en_US-4.0.1.tar.gz'... PHP Fatal error: Uncaught exception 'UnexpectedValueException' with message 'phar tar error: "/home/vagrant/.wp-cli/cache/core/en_US-4.0.1.tar.gz" already exists as a regular phar and must be deleted from disk prior to creating as a tar-based phar' in /srv/www/wp-cli/php/commands/core.php:182 Stack trace:

0 /srv/www/wp-cli/php/commands/core.php(182): PharData->__construct('/home/vagrant/....')

#1 /srv/www/wp-cli/php/commands/core.php(155): Core_Command::_extract('/home/vagrant/....', '/srv/www/test/h...')
#2 [internal function]: Core_Command->download(Array, Array)
#3 /srv/www/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(52): call_user_func(Array, Array, Array)
#4 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher{closure}(Array, Array)
#5 /srv/www/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(295): call_user_func(Object(Closure), Array, Array)
#6 /srv/www/wp-cli/php/WP_CLI/Runner.php(304): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
#7 /srv/www/wp-cli/php/WP_CLI/Runner.php(311): WP_CLI\ in /srv/www/wp-cli/php/commands/core.php on line 182
Error: This does not seem to be a WordPress install.
Pass --path=`path/to/wordpress` or run `wp core download`.
Error: This does not seem to be a WordPress install.
Pass --path=`path/to/wordpress` or run `wp core download`.
/srv/www/test
joelworsham commented 9 years ago

I see now that it is because of this issue, which is with WP-CLI https://github.com/aliso/vvv-site-wizard/issues/20.

Hopefully this gets sorted out, but at least now I know why this is happening