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 /
db-command /
features /
[ HOME SHELL ]
Name
Size
Permission
Action
db-check.feature
3.67
KB
-rw-r--r--
db-columns.feature
3.56
KB
-rw-r--r--
db-export.feature
2.49
KB
-rw-r--r--
db-import.feature
4.9
KB
-rw-r--r--
db-prefix.feature
224
B
-rw-r--r--
db-query.feature
3.14
KB
-rw-r--r--
db-search.feature
29.69
KB
-rw-r--r--
db-size.feature
5.96
KB
-rw-r--r--
db-tables.feature
5.95
KB
-rw-r--r--
db.feature
8.63
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : db-query.feature
Feature: Query the database with WordPress' MySQL config Scenario: Database querying shouldn't load any plugins Given a WP install And a wp-content/mu-plugins/error.php file: """ <?php WP_CLI::error( "Plugin loaded." ); """ When I try `wp option get home` Then STDERR should be: """ Error: Plugin loaded. """ When I run `wp db query "SELECT COUNT(ID) FROM wp_users;"` Then STDOUT should be: """ COUNT(ID) 1 """ Scenario: Database querying with passed-in options Given a WP install When I run `wp db query "SELECT COUNT(ID) FROM wp_posts;" --dbuser=wp_cli_test --html` Then STDOUT should contain: """ <TABLE """ When I try `wp db query "SELECT COUNT(ID) FROM wp_posts;" --dbuser=no_such_user` Then the return code should not be 0 And STDERR should contain: """ Access denied """ And STDOUT should be empty Scenario: Database querying with MySQL defaults and passed-in options Given a WP install When I run `wp db query --defaults "SELECT COUNT(ID) FROM wp_posts;" --dbuser=wp_cli_test --html` Then STDOUT should contain: """ <TABLE """ When I try `wp db query --defaults "SELECT COUNT(ID) FROM wp_posts;" --dbuser=no_such_user` Then the return code should not be 0 And STDERR should contain: """ Access denied """ And STDOUT should be empty Scenario: Database querying with --nodefaults and passed-in options Given a WP install When I run `wp db query --no-defaults "SELECT COUNT(ID) FROM wp_posts;" --dbuser=wp_cli_test --html` Then STDOUT should contain: """ <TABLE """ When I try `wp db query --no-defaults "SELECT COUNT(ID) FROM wp_posts;" --dbuser=no_such_user` Then the return code should not be 0 And STDERR should contain: """ Access denied """ And STDOUT should be empty Scenario: MySQL defaults are available as appropriate with --defaults flag Given a WP install When I try `wp db query --defaults --debug` Then STDERR should match #Debug \(db\): Running shell command: /usr/bin/env (mysql|mariadb) --no-auto-rehash# When I try `wp db query --debug` Then STDERR should match #Debug \(db\): Running shell command: /usr/bin/env (mysql|mariadb) --no-defaults --no-auto-rehash# When I try `wp db query --no-defaults --debug` Then STDERR should match #Debug \(db\): Running shell command: /usr/bin/env (mysql|mariadb) --no-defaults --no-auto-rehash# Scenario: SQL modes do not include any of the modes incompatible with WordPress Given a WP install When I try `wp db query 'SELECT @@SESSION.sql_mode;' --debug` Then STDOUT should not contain: """ NO_ZERO_DATE """ And STDOUT should not contain: """ ONLY_FULL_GROUP_BY """ And STDOUT should not contain: """ STRICT_TRANS_TABLES """ And STDOUT should not contain: """ STRICT_ALL_TABLES """ And STDOUT should not contain: """ TRADITIONAL """ And STDOUT should not contain: """ ANSI """
Close