core-install.feature

Feature: Install WordPress core

  # TODO: Requires investigation for SQLite support.
  # See https://github.com/wp-cli/core-command/issues/244
  @require-mysql
  Scenario: Two WordPress installs sharing the same user table won't update existing user
    Given an empty directory
    And WP files
    And a WP install in 'second'
    And a extra-config file:
      """
      define( 'CUSTOM_USER_TABLE', 'secondusers' );
      define( 'CUSTOM_USER_META_TABLE', 'secondusermeta' );
      """

    When I run `wp --path=second user create testadmin testadmin@example.org --role=administrator`
    Then STDOUT should contain:
      """
      Success: Created user 2.
      """

    When I run `wp --path=second db tables`
    Then STDOUT should contain:
      """
      secondposts
      """
    And STDOUT should contain:
      """
      secondusers
      """

    When I run `wp --path=second user list --field=user_login`
    Then STDOUT should be:
      """
      admin
      testadmin
      """

    When I run `wp --path=second user get testadmin --field=user_pass`
    Then save STDOUT as {ORIGINAL_PASSWORD}

    When I run `wp config create {CORE_CONFIG_SETTINGS} --skip-check --extra-php < extra-config`
    Then STDOUT should be:
      """
      Success: Generated 'wp-config.php' file.
      """

    When I run `wp core install --url=example.org --title=Test --admin_user=testadmin --admin_email=testadmin@example.com --admin_password=newpassword`
    Then STDOUT should contain:
      """
      Success: WordPress installed successfully.
      """

    When I run `wp user list --field=user_login`
    Then STDOUT should be:
      """
      admin
      testadmin
      """

    When I run `wp user get testadmin --field=email`
    Then STDOUT should be:
      """
      testadmin@example.org
      """

    When I run `wp user get testadmin --field=user_pass`
    Then STDOUT should be:
      """
      {ORIGINAL_PASSWORD}
      """

    When I run `wp db tables`
    Then STDOUT should contain:
      """
      wp_posts
      """
    And STDOUT should contain:
      """
      secondusers
      """
    And STDOUT should not contain:
      """
      wp_users
      """

  # TODO: Requires investigation for SQLite support.
  # See https://github.com/wp-cli/core-command/issues/244
  @require-mysql
  Scenario: Two WordPress installs sharing the same user table will create new user
    Given an empty directory
    And WP files
    And a WP install in 'second'
    And a extra-config file:
      """
      define( 'CUSTOM_USER_TABLE', 'secondusers' );
      define( 'CUSTOM_USER_META_TABLE', 'secondusermeta' );
      """

    When I run `wp --path=second db tables`
    Then STDOUT should contain:
      """
      secondposts
      """
    And STDOUT should contain:
      """
      secondusers
      """

    When I run `wp --path=second user list --field=user_login`
    Then STDOUT should be:
      """
      admin
      """

    When I run `wp config create {CORE_CONFIG_SETTINGS} --skip-check --extra-php < extra-config`
    Then STDOUT should be:
      """
      Success: Generated 'wp-config.php' file.
      """

    When I run `wp core install --url=example.org --title=Test --admin_user=testadmin --admin_email=testadmin@example.com --admin_password=newpassword`
    Then STDOUT should contain:
      """
      Success: WordPress installed successfully.
      """

    When I run `wp user list --field=user_login`
    Then STDOUT should be:
      """
      admin
      testadmin
      """

    When I run `wp --path=second user list --field=user_login`
    Then STDOUT should be:
      """
      admin
      testadmin
      """

    When I run `wp user get testadmin --field=email`
    Then STDOUT should be:
      """
      testadmin@example.com
      """

    When I run `wp db tables`
    Then STDOUT should contain:
      """
      wp_posts
      """
    And STDOUT should contain:
      """
      secondusers
      """
    And STDOUT should not contain:
      """
      wp_users
      """

  Scenario: Install WordPress without specifying the admin password
    Given an empty directory
    And WP files
    And wp-config.php
    And a database

    # Old versions of WP can generate wpdb database errors if the WP tables don't exist, so STDERR may or may not be empty
    When I try `wp core install --url=localhost:8001 --title=Test --admin_user=wpcli --admin_email=wpcli@example.org`
    Then STDOUT should contain:
      """
      Admin password:
      """
    And STDOUT should contain:
      """
      Success: WordPress installed successfully.
      """
    And the return code should be 0

  Scenario: Install WordPress with special characters in the admin password
    Given an empty directory
    And WP files
    And wp-config.php
    And a database

    When I run `wp core install --url=localhost:8001 --title=Test --admin_user=wpcli --admin_email=wpcli@example.org --admin_password='R^^CzY;G"iZ@]H9b,' --skip-email`
    Then STDOUT should contain:
      """
      Success: WordPress installed successfully.
      """
    And the return code should be 0

    When I run `wp user check-password wpcli 'R^^CzY;G"iZ@]H9b,' --escape-chars`
    Then the return code should be 0

  # This test downgrades to an older WordPress version, but the SQLite plugin requires 6.0+
  @require-mysql
  Scenario: Install WordPress with locale set to de_DE on WP >= 4.0
    Given an empty directory
    And an empty cache
    And a database

    When I run `wp core download --version=5.6 --locale=de_DE`
    And save STDOUT 'Downloading WordPress ([\d\.]+)' as {VERSION}
    And I run `echo {VERSION}`
    Then STDOUT should contain:
      """
      5.6
      """
    And the wp-settings.php file should exist
    And the {SUITE_CACHE_DIR}/core/wordpress-{VERSION}-de_DE.tar.gz file should exist

    When I run `wp config create --dbname={DB_NAME} --dbuser={DB_USER} --dbpass={DB_PASSWORD} --dbhost={DB_HOST} --locale=de_DE --skip-check`
    Then STDOUT should be:
      """
      Success: Generated 'wp-config.php' file.
      """

    # Old versions of WP can generate wpdb database errors if the WP tables don't exist, so STDERR may or may not be empty
    When I run `wp core install --url=example.org --title=Test --admin_user=testadmin --admin_email=testadmin@example.com --admin_password=newpassword --locale=de_DE --skip-email`
    Then STDOUT should contain:
      """
      Success: WordPress installed successfully.
      """

    When I run `wp core version`
    Then STDOUT should contain:
      """
      5.6
      """

    When I run `wp taxonomy list`
    Then STDOUT should contain:
      """
      Kategorien
      """

  Scenario: Install WordPress multisite without specifying the password
    Given an empty directory
    And WP files
    And wp-config.php
    And a database

    # Old versions of WP can generate wpdb database errors if the WP tables don't exist, so STDERR may or may not be empty
    When I try `wp core multisite-install --url=foobar.org --title=Test --admin_user=wpcli --admin_email=admin@example.com`
    Then STDOUT should contain:
      """
      Admin password:
      """
    And STDOUT should contain:
      """
      Success: Network installed. Don't forget to set up rewrite rules (and a .htaccess file, if using Apache).
      """
    And the return code should be 0

  Scenario: Install WordPress multisite without adding multisite constants to wp-config file
    Given an empty directory
    And WP files
    And wp-config.php
    And a database

    When I run `wp core multisite-install --url=foobar.org --title=Test --admin_user=wpcli --admin_email=admin@example.com --admin_password=password --skip-config`
    Then STDOUT should contain:
      """
      Addition of multisite constants to 'wp-config.php' skipped. You need to add them manually:
      """

  @require-mysql
  Scenario: Install WordPress multisite with existing multisite constants in wp-config file
    Given an empty directory
    And WP files
    And a database
    And a extra-config file:
      """
      define( 'WP_ALLOW_MULTISITE', true );
      define( 'MULTISITE', true );
      define( 'SUBDOMAIN_INSTALL', true );
      $base = '/';
      define( 'DOMAIN_CURRENT_SITE', 'foobar.org' );
      define( 'PATH_CURRENT_SITE', '/' );
      define( 'SITE_ID_CURRENT_SITE', 1 );
      define( 'BLOG_ID_CURRENT_SITE', 1 );
      """

    When I run `wp config create {CORE_CONFIG_SETTINGS} --extra-php < extra-config`
    Then STDOUT should be:
      """
      Success: Generated 'wp-config.php' file.
      """

    When I run `wp core multisite-install --url=foobar.org --title=Test --admin_user=wpcli --admin_email=admin@example.com --admin_password=password --skip-config`
    Then STDOUT should be:
      """
      Created single site database tables.
      Set up multisite database tables.
      Success: Network installed. Don't forget to set up rewrite rules (and a .htaccess file, if using Apache).
      """

    When I run `wp db query "select * from wp_sitemeta where meta_key = 'site_admins' and meta_value = ''"`
    Then STDOUT should be:
      """
      """

  # Added to verify https://github.com/wp-cli/extension-command/issues/410
  @require-mysql
  Scenario: Install child theme
    Given a WP install
    When I try `wp theme install https://public-api.wordpress.com/rest/v1/themes/download/rockfield.zip --activate`
    Then STDERR should contain:
    """
    Error: The parent theme is missing. Please install the "varia-wpcom" parent theme.
    """

    When I run `wp theme install https://public-api.wordpress.com/rest/v1/themes/download/varia.zip --activate`
    Then STDOUT should contain:
    """
    Success: Installed 1 of 1 themes.
    """

    When I run `wp theme activate rockfield-wpcom`
    Then STDOUT should contain:
    """
    Success: Switched to 'Rockfield' theme.
    """

  Scenario: Core install should provide helpful error when upgrade.php is missing
    Given an empty directory
    And WP files
    And wp-config.php
    And a database

    When I run `rm wp-admin/includes/upgrade.php`
    Then the return code should be 0

    When I try `wp core install --url=example.org --title=Test --admin_user=testadmin --admin_email=testadmin@example.com --admin_password=testpass`
    Then STDERR should contain:
      """
      Error: WordPress installation is incomplete. The file
      """
    And STDERR should contain:
      """
      wp-admin/includes/upgrade.php' is missing.
      """
    And the return code should be 1

  Scenario: Core install should provide helpful error when upgrade.php is not readable
    Given an empty directory
    And WP files
    And wp-config.php
    And a database

    When I run `chmod 000 wp-admin/includes/upgrade.php`
    Then the return code should be 0

    When I try `wp core install --url=example.org --title=Test --admin_user=testadmin --admin_email=testadmin@example.com --admin_password=testpass`
    Then STDERR should contain:
      """
      Error: Cannot read WordPress installation file
      """
    And STDERR should contain:
      """
      wp-admin/includes/upgrade.php'. Check file permissions.
      """
    And the return code should be 1

    When I run `chmod 644 wp-admin/includes/upgrade.php`
    Then the return code should be 0

  Scenario: Core install should provide helpful error when WordPress file has fatal error from missing extension
    Given an empty directory
    And WP files
    And wp-config.php
    And a database

    # Simulate a missing mysqli extension by replacing upgrade.php with code that
    # triggers a fatal error mimicking what happens when mysqli_connect is called
    # but the extension is not available. This reproduces the original bug report scenario
    When I run `echo "<?php trigger_error('Call to undefined function mysqli_connect()', E_USER_ERROR);" > wp-admin/includes/upgrade.php`
    Then the return code should be 0

    When I try `wp core install --url=example.org --title=Test --admin_user=testadmin --admin_email=testadmin@example.com --admin_password=testpass`
    Then STDERR should contain:
      """
      Error: Failed to load WordPress files for WordPress installation
      """
    And STDERR should contain:
      """
      This error is in WordPress core files, not a plugin or theme
      """
    And STDERR should contain:
      """
      It often indicates a missing PHP extension (like mysqli)
      """
    And STDERR should contain:
      """
      Call to undefined function mysqli_connect()
      """
    And the return code should be 1