Linux iad1-shared-b7-18 6.6.49-grsec-jammy+ #10 SMP Thu Sep 12 23:23:08 UTC 2024 x86_64
Apache
: 67.205.6.31 | : 216.73.216.47
Cant Read [ /etc/named.conf ]
8.2.29
fernandoquevedo
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
usr /
local /
wp /
vendor /
wp-cli /
core-command /
features /
[ HOME SHELL ]
Name
Size
Permission
Action
core-check-update.feature
2.23
KB
-rw-r--r--
core-download.feature
15.02
KB
-rw-r--r--
core-install.feature
9.79
KB
-rw-r--r--
core-update-db.feature
5.57
KB
-rw-r--r--
core-update.feature
10.4
KB
-rw-r--r--
core-version.feature
1020
B
-rw-r--r--
core.feature
11.59
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : core.feature
Feature: Manage WordPress installation # `wp db create` does not yet work on SQLite, # See https://github.com/wp-cli/db-command/issues/234 @require-mysql Scenario: Database doesn't exist Given an empty directory And WP files And wp-config.php When I try `wp core is-installed` Then the return code should be 1 And STDERR should not be empty When I run `wp db create` Then STDOUT should not be empty Scenario: Database tables not installed Given an empty directory And WP files And wp-config.php And a database When I try `wp core is-installed` Then the return code should be 1 When I try `wp core is-installed --network` Then the return code should be 1 When I try `wp core install` Then the return code should be 1 And STDERR should contain: """ missing --url parameter (The address of the new site.) """ When I run `wp core install --url='localhost:8001' --title='Test' --admin_user=wpcli --admin_email=admin@example.com --admin_password=1` Then STDOUT should not be empty When I run `wp eval 'echo home_url();'` Then STDOUT should be: """ http://localhost:8001 """ When I try `wp core is-installed --network` Then the return code should be 1 Scenario: Install WordPress by prompting Given an empty directory And WP files And wp-config.php And a database And a session file: """ localhost:8001 Test wpcli wpcli admin@example.com """ When I run `wp core install --prompt < session` Then STDOUT should not be empty When I run `wp eval 'echo home_url();'` Then STDOUT should be: """ https://localhost:8001 """ Scenario: Install WordPress by prompting for the admin email and password Given an empty directory And WP files And wp-config.php And a database And a session file: """ wpcli admin@example.com """ When I run `wp core install --url=localhost:8001 --title=Test --admin_user=wpcli --prompt=admin_password,admin_email < session` Then STDOUT should not be empty When I run `wp eval 'echo home_url();'` Then STDOUT should be: """ http://localhost:8001 """ Scenario: Install WordPress with an https scheme Given an empty directory And WP files And wp-config.php And a database When I run `wp core install --url='https://localhost' --title='Test' --admin_user=wpcli --admin_email=admin@example.com --admin_password=1` Then the return code should be 0 When I run `wp eval 'echo home_url();'` Then STDOUT should be: """ https://localhost """ Scenario: Install WordPress with an https scheme and non-standard port Given an empty directory And WP files And wp-config.php And a database When I run `wp core install --url='https://localhost:8443' --title='Test' --admin_user=wpcli --admin_email=admin@example.com --admin_password=1` Then the return code should be 0 When I run `wp eval 'echo home_url();'` Then STDOUT should be: """ https://localhost:8443 """ Scenario: Full install Given a WP install When I run `wp core is-installed` Then STDOUT should be empty And the wp-content/uploads directory should exist When I run `wp eval 'var_export( is_admin() );'` Then STDOUT should be: """ false """ When I run `wp eval 'var_export( function_exists( "media_handle_upload" ) );'` Then STDOUT should be: """ true """ # Can complain that it's already installed, but don't exit with an error code When I try `wp core install --url='localhost:8001' --title='Test' --admin_user=wpcli --admin_email=admin@example.com --admin_password=1` Then the return code should be 0 Scenario: Convert install to multisite Given a WP install When I run `wp eval 'var_export( is_multisite() );'` Then STDOUT should be: """ false """ When I try `wp core is-installed --network` Then the return code should be 1 When I run `wp core install-network --title='test network'` Then STDOUT should be: """ Set up multisite database tables. Added multisite constants to 'wp-config.php'. Success: Network installed. Don't forget to set up rewrite rules (and a .htaccess file, if using Apache). """ And STDERR should be empty When I run `wp eval 'var_export( is_multisite() );'` Then STDOUT should be: """ true """ When I run `wp core is-installed --network` Then the return code should be 0 When I try `wp core install-network --title='test network'` Then the return code should be 1 When I run `wp network meta get 1 upload_space_check_disabled` Then STDOUT should be: """ 1 """ Scenario: Install multisite from scratch 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=1` Then STDOUT should be: """ Created single site database tables. Set up multisite database tables. Added multisite constants to 'wp-config.php'. Success: Network installed. Don't forget to set up rewrite rules (and a .htaccess file, if using Apache). """ And STDERR should be empty When I run `wp eval 'echo $GLOBALS["current_site"]->domain;'` Then STDOUT should be: """ foobar.org """ # Can complain that it's already installed, but don't exit with an error code When I try `wp core multisite-install --url=foobar.org --title=Test --admin_user=wpcli --admin_email=admin@example.com --admin_password=1` Then the return code should be 0 When I run `wp network meta get 1 upload_space_check_disabled` Then STDOUT should be: """ 1 """ # `wp db reset` does not yet work on SQLite, # See https://github.com/wp-cli/db-command/issues/234 @require-mysql Scenario: Install multisite from scratch, with MULTISITE already set in wp-config.php Given a WP multisite install And I run `wp db reset --yes` When I try `wp core is-installed` Then the return code should be 1 # WP will produce wpdb database errors in `get_sites()` on loading if the WP tables don't exist And STDERR should contain: """ WordPress database error Table """ When I run `wp core multisite-install --title=Test --admin_user=wpcli --admin_email=admin@example.com --admin_password=1` Then STDOUT should not be empty When I run `wp eval 'echo $GLOBALS["current_site"]->domain;'` Then STDOUT should be: """ example.com """ Scenario: Install multisite with subdomains on localhost Given an empty directory And WP files And wp-config.php And a database When I try `wp core multisite-install --url=http://localhost/ --title=Test --admin_user=wpcli --admin_email=admin@example.com --admin_password=1 --subdomains` Then STDERR should contain: """ Error: Multisite with subdomains cannot be configured when domain is 'localhost'. """ And the return code should be 1 # SQLite compat blocked by https://github.com/wp-cli/wp-cli-tests/pull/188. @require-mysql Scenario: Custom wp-content directory Given a WP install And a custom wp-content directory When I run `wp plugin status akismet` Then STDOUT should not be empty Scenario: User defined in wp-cli.yml Given an empty directory And WP files And wp-config.php And a database And a wp-cli.yml file: """ user: wpcli """ When I run `wp core install --url='localhost:8001' --title='Test' --admin_user=wpcli --admin_email=admin@example.com --admin_password=1` Then STDOUT should not be empty When I run `wp eval 'echo home_url();'` Then STDOUT should be: """ http://localhost:8001 """ Scenario: Test output in a multisite install with custom base path Given a WP install When I run `wp core multisite-convert --title=Test --base=/test/` And I run `wp post list` Then STDOUT should contain: """ Hello world! """ Scenario: Download WordPress Given an empty directory When I run `wp core download` Then STDOUT should contain: """ Success: WordPress downloaded. """ And the wp-settings.php file should exist Scenario: Don't download WordPress when files are already present Given an empty directory And WP files When I try `wp core download` Then STDERR should be: """ Error: WordPress files seem to already be present here. """ And the return code should be 1 # `wp db create` does not yet work on SQLite, # See https://github.com/wp-cli/db-command/issues/234 @require-php-7.0 @require-mysql Scenario: Install WordPress in a subdirectory Given an empty directory And a wp-config.php file: """ <?php // ** MySQL settings ** // /** The name of the database for WordPress */ define('DB_NAME', '{DB_NAME}'); /** MySQL database username */ define('DB_USER', '{DB_USER}'); /** MySQL database password */ define('DB_PASSWORD', '{DB_PASSWORD}'); /** MySQL hostname */ define('DB_HOST', '{DB_HOST}'); /** Database Charset to use in creating database tables. */ define('DB_CHARSET', 'utf8'); /** The Database Collate type. Don't change this if in doubt. */ define('DB_COLLATE', ''); $table_prefix = 'wp_'; /* That's all, stop editing! Happy publishing. */ /** Absolute path to the WordPress directory. */ if ( !defined('ABSPATH') ) define('ABSPATH', dirname(__FILE__) . '/'); /** Sets up WordPress vars and included files. */ require_once(ABSPATH . 'wp-settings.php'); """ And a wp-cli.yml file: """ path: wp """ When I run `wp core download` Then the wp directory should exist And the wp/wp-blog-header.php file should exist When I run `wp db create` # extra/no-mail.php not present as mu-plugin so skip sending email else will fail on Travis with "sh: 1: -t: not found" And I run `wp core install --url=example.com --title="WP Example" --admin_user=wpcli --admin_password=wpcli --admin_email=wpcli@example.com --skip-email` Then STDOUT should contain: """ Success: WordPress installed successfully. """ When I run `wp option get home` Then STDOUT should be: """ http://example.com """ When I run `wp option get siteurl` Then STDOUT should be: """ http://example.com """ Scenario: Warn when multisite constants can't be inserted into wp-config Given a WP install And "That's all" replaced with "C'est tout" in the wp-config.php file When I try `wp core multisite-convert` Then STDOUT should be: """ Set up multisite database tables. Success: Network installed. Don't forget to set up rewrite rules (and a .htaccess file, if using Apache). """ And STDERR should contain: """ Warning: Multisite constants could not be written to 'wp-config.php'. You may need to add them manually: """ And the return code should be 0 Scenario: Convert to WordPress multisite without adding multisite constants to wp-config file Given a WP install When I run `wp core multisite-convert --skip-config` Then STDOUT should contain: """ Addition of multisite constants to 'wp-config.php' skipped. You need to add them manually: """
Close