blueprints: installing themes and plugins fails, warning about root access

[israelcurtis]

when using a blueprint, for every theme and plugin, and eve option that I have listed, I get this big red warning output

==> default: Setting up blueprint somatic...
==> default: Installing themes...
==> default: Error: YIKES! It looks like you're running this as root. You probably meant to run this as the user that your WordPress install exists under.
==> default: 
==> default: If you REALLY mean to run this as root, we won't stop you, but just bear in mind that any code on this site will then have full control of your server, making it quite DANGEROUS.
==> default: 
==> default: If you'd like to continue as root, please run this again, adding this flag:  --allow-root
==> default: 
==> default: If you'd like to run it as the user that this site is under, you can run the following to become the respective user:
==> default: 
==> default:     sudo -u USER -i -- wp <command>

but strangely, I don't get the error when it comes to mu-plugins

==> default: Installing mu-plugins...
==> default: Cloning into 'WDS-Required-Plugins'...

so at the end of it all, the install does work, and the site runs, but I have none of the themes, plugins, or options from the blueprint -- just the mu-plugins

[bradp]

Just pushed an update to the vv-install branch, which gets pulled down during provision. Should be all good to go now.

[israelcurtis]

worked great for plugins and themes, but setting the options still throws the error (so no theme activated, etc)

==> default: Installing mu-plugins...
==> default: Cloning into 'WDS-Required-Plugins'...
==> default: setting up options...
==> default: Error: YIKES! It looks like you're running this as root. You probably meant to run this as the user tha
t your WordPress install exists under.
==> default: 
==> default: If you REALLY mean to run this as root, we won't stop you, but just bear in mind that any code on this 
site will then have full control of your server, making it quite DANGEROUS.
==> default: 
==> default: If you'd like to continue as root, please run this again, adding this flag:  --allow-root
==> default: 
==> default: If you'd like to run it as the user that this site is under, you can run the following to become the re
spective user:
==> default: 
==> default:     sudo -u USER -i -- wp <command>
==> default: Error: YIKES! It looks like you're running this as root. You probably meant to run this as the user tha
t your WordPress install exists under.
==> default: 
==> default: If you REALLY mean to run this as root, we won't stop you, but just bear in mind that any code on this 
site will then have full control of your server, making it quite DANGEROUS.
==> default: 
==> default: If you'd like to continue as root, please run this again, adding this flag:  --allow-root
==> default: 
==> default: If you'd like to run it as the user that this site is under, you can run the following to become the re
spective user:
==> default: 
==> default:     sudo -u USER -i -- wp <command>

now it looks like the root warning fired twice in this section, even though I only have one option declared in my blueprint:

{
  "somatic": {
    "themes": [
      "automattic/_s"
    ],
    "mu_plugins": [
      "https://github.com/WebDevStudios/WDS-Required-Plugins.git"
    ],
    "plugins": [
      "somatic-framework",
      "debug-this",
      "what-template-file-am-i-viewing",
      "custom-post-type-permalinks",
      "debug-bar",
      "debug-bar-console",
      "simple-page-ordering",
      "restricted-site-access",
      "enable-media-replace",
      "user-switching",
      "regenerate-thumbnails",
      "file-un-attach",
      "antivirus",
      "if-menu",
      "custom-upload-dir",
      "jetpack"
    ],
    "options": [
      "active_theme::_s"
    ],
    "defines": [
      "WP_DEBUG::true"
    ]
  }
}

[bradp]

I'll see if I can replicate this issue, and I'll try to get a fix out.

Thanks!

[bradp]

Actually, just pushed out a fix for this now.

Should work great for new sites with blueprints.

[israelcurtis]

hmmm... still getting error on options. just tried to provision a new site.

[bradp]

Just pushed an update to fix the options - try it now.

[israelcurtis]

ok, the root error is gone, but the option is still not set (_s is not active theme, twentyfourteen is).

==> default: setting up options...
==> default: Error: Could not delete 'active_theme' option. Does it exist?
==> default: Adding constants to wp-config.php...
==> default: Blueprint set up.

[bradp]

Oops - turns out the option name is current_theme.

Its been fixed in the file that vv pulls down, so new sites should be good to go.