Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified
📁 ..	-	2025-05-25 12:40
📄 .actrc # Configuration file for nektos/act. # See https://github.com/nektos/act#configuration -P ubuntu-latest=shivammathur/node:latest	129 B	2025-05-25 12:40
📄 .distignore .DS_Store .git .gitignore .editorconfig .travis.yml circle.yml bin/ features/ utils/	85 B	2025-05-25 12:40
📄 .editorconfig # This file is for unifying the coding style for different editors and IDEs # editorconfig.org # WordPress Coding Standards # https://make.wordpress.org/core/handbook/coding-standards/ # From https://github.com/WordPress/wordpress-develop/blob/trunk/.editorconfig with a couple of additions. root = true [] charset = utf-8 end_of_line = lf insert_final_newline = true trim_trailing_whitespace = true indent_style = tab [{.yml,.feature,.jshintrc,.json}] indent_style = space indent_size = 2 [.md] trim_trailing_whitespace = false [{.txt,wp-config-sample.php}] end_of_line = crlf	591 B	2025-05-25 12:40
📁 .git	-	2026-03-21 17:12
📄 .gitattributes /.actrc export-ignore /.distignore export-ignore /.editorconfig export-ignore /.github export-ignore /.gitignore export-ignore /.typos.toml export-ignore /AGENTS.md export-ignore /behat.yml export-ignore /features export-ignore /phpcs.xml.dist export-ignore /phpstan.neon.dist export-ignore /phpunit.xml.dist export-ignore /tests export-ignore /wp-cli.yml export-ignore	370 B	2026-03-21 17:12
📁 .github	-	2025-05-25 12:40
📄 .gitignore .DS_Store wp-cli.local.yml node_modules/ vendor/ composer.lock *.log	69 B	2025-05-25 12:40
📄 AGENTS.md # Instructions This package is part of WP-CLI, the official command line interface for WordPress. For a detailed explanation of the project structure and development workflow, please refer to the main @README.md file. ## Best Practices for Code Contributions When contributing to this package, please adhere to the following guidelines: * Follow Existing Conventions: Before writing any code, analyze the existing codebase in this package to understand the coding style, naming conventions, and architectural patterns. * Focus on the Package's Scope: All changes should be relevant to the functionality of the package. * Write Tests: All new features and bug fixes must be accompanied by acceptance tests using Behat. You can find the existing tests in the `features/` directory. There may be PHPUnit unit tests as well in the `tests/` directory. * Update Documentation: If your changes affect the user-facing functionality, please update the relevant inline code documentation. ### Building and running Before submitting any changes, it is crucial to validate them by running the full suite of static code analysis and tests. To run the full suite of checks, execute the following command: `composer test`. This single command ensures that your changes meet all the quality gates of the project. While you can run the individual steps separately, it is highly recommended to use this single command to ensure a comprehensive validation. ### Useful Composer Commands The project uses Composer to manage dependencies and run scripts. The following commands are available: * `composer install`: Install dependencies. * `composer test`: Run the full test suite, including linting, code style checks, static analysis, and unit/behavior tests. * `composer lint`: Check for syntax errors. * `composer phpcs`: Check for code style violations. * `composer phpcbf`: Automatically fix code style violations. * `composer phpstan`: Run static analysis. * `composer phpunit`: Run unit tests. * `composer behat`: Run behavior-driven tests. ### Coding Style The project follows the `WP_CLI_CS` coding standard, which is enforced by PHP_CodeSniffer. The configuration can be found in `phpcs.xml.dist`. Before submitting any code, please run `composer phpcs` to check for violations and `composer phpcbf` to automatically fix them. ## Documentation The `README.md` file might be generated dynamically from the project's codebase using `wp scaffold package-readme` ([doc](https://github.com/wp-cli/scaffold-package-command#wp-scaffold-package-readme)). In that case, changes need to be made against the corresponding part of the codebase. ### Inline Documentation Only write high-value comments if at all. Avoid talking to the user through comments. ## Testing The project has a comprehensive test suite that includes unit tests, behavior-driven tests, and static analysis. * Unit tests are written with PHPUnit and can be found in the `tests/` directory. The configuration is in `phpunit.xml.dist`. * Behavior-driven tests are written with Behat and can be found in the `features/` directory. The configuration is in `behat.yml`. * Static analysis is performed with PHPStan. All tests are run on GitHub Actions for every pull request. When writing tests, aim to follow existing patterns. Key conventions include: * When adding tests, first examine existing tests to understand and conform to established conventions. * For unit tests, extend the base `WP_CLI\Tests\TestCase` test class. * For Behat tests, only WP-CLI commands installed in `composer.json` can be run. ### Behat Steps WP-CLI makes use of a Behat-based testing framework and provides a set of custom step definitions to write feature tests. > Note: If you are expecting an error output in a test, you need to use `When I try ...` instead of `When I run ...` . #### Given * `Given an empty directory` - Creates an empty directory. * `Given /^an? (empty\|non-existent) ([^\s]+) directory$/` - Creates or deletes a specific directory. * `Given an empty cache` - Clears the WP-CLI cache directory. * `Given /^an? ([^\s]+) (file\|cache file):$/` - Creates a file with the given contents. * `Given /^"([^"]+)" replaced with "([^"]+)" in the ([^\s]+) file$/` - Search and replace a string in a file using regex. * `Given /^that HTTP requests to (.?) will respond with:$/` - Mock HTTP requests to a given URL. `Given WP files` - Download WordPress files without installing. * `Given wp-config.php` - Create a wp-config.php file using `wp config create`. * `Given a database` - Creates an empty database. * `Given a WP install(ation)` - Installs WordPress. * `Given a WP install(ation) in :subdir` - Installs WordPress in a given directory. * `Given a WP install(ation) with Composer` - Installs WordPress with Composer. * `Given a WP install(ation) with Composer and a custom vendor directory :vendor_directory` - Installs WordPress with Composer and a custom vendor directory. * `Given /^a WP multisite (subdirectory\|subdomain)?\s?(install\|installation)$/` - Installs WordPress Multisite. * `Given these installed and active plugins:` - Installs and activates one or more plugins. * `Given a custom wp-content directory` - Configure a custom `wp-content` directory. * `Given download:` - Download multiple files into the given destinations. * `Given /^save (STDOUT\|STDERR) ([\'].+[^\'])?\s?as \{(\w+)\}$/` - Store STDOUT or STDERR contents in a variable. * `Given /^a new Phar with (?:the same version\|version "([^"]+)")$/` - Build a new WP-CLI Phar file with a given version. * `Given /^a downloaded Phar with (?:the same version\|version "([^"]+)")$/` - Download a specific WP-CLI Phar version from GitHub. * `Given /^save the (.+) file ([\'].+[^\'])? as \{(\w+)\}$/` - Stores the contents of the given file in a variable. * `Given a misconfigured WP_CONTENT_DIR constant directory` - Modify wp-config.php to set `WP_CONTENT_DIR` to an empty string. * `Given a dependency on current wp-cli` - Add `wp-cli/wp-cli` as a Composer dependency. * `Given a PHP built-in web server` - Start a PHP built-in web server in the current directory. * `Given a PHP built-in web server to serve :subdir` - Start a PHP built-in web server in the given subdirectory. #### When * ``When /^I launch in the background `([^`]+)`$/`` - Launch a given command in the background. * ``When /^I (run\|try) `([^`]+)`$/`` - Run or try a given command. * ``When /^I (run\|try) `([^`]+)` from '([^\s]+)'$/`` - Run or try a given command in a subdirectory. * `When /^I (run\|try) the previous command again$/` - Run or try the previous command again. #### Then * `Then /^the return code should( not)? be (\d+)$/` - Expect a specific exit code of the previous command. * `Then /^(STDOUT\|STDERR) should( strictly)? (be\|contain\|not contain):$/` - Check the contents of STDOUT or STDERR. * `Then /^(STDOUT\|STDERR) should be a number$/` - Expect STDOUT or STDERR to be a numeric value. * `Then /^(STDOUT\|STDERR) should not be a number$/` - Expect STDOUT or STDERR to not be a numeric value. * `Then /^STDOUT should be a table containing rows:$/` - Expect STDOUT to be a table containing the given rows. * `Then /^STDOUT should end with a table containing rows:$/` - Expect STDOUT to end with a table containing the given rows. * `Then /^STDOUT should be JSON containing:$/` - Expect valid JSON output in STDOUT. * `Then /^STDOUT should be a JSON array containing:$/` - Expect valid JSON array output in STDOUT. * `Then /^STDOUT should be CSV containing:$/` - Expect STDOUT to be CSV containing certain values. * `Then /^STDOUT should be YAML containing:$/` - Expect STDOUT to be YAML containing certain content. * `Then /^(STDOUT\|STDERR) should be empty$/` - Expect STDOUT or STDERR to be empty. * `Then /^(STDOUT\|STDERR) should not be empty$/` - Expect STDOUT or STDERR not to be empty. * `Then /^(STDOUT\|STDERR) should be a version string (<\|<=\|>\|>=\|==\|=\|<>) ([+\w.{}-]+)$/` - Expect STDOUT or STDERR to be a version string comparing to the given version. * `Then /^the (.+) (file\|directory) should( strictly)? (exist\|not exist\|be:\|contain:\|not contain):$/` - Expect a certain file or directory to (not) exist or (not) contain certain contents. * `Then /^the contents of the (.+) file should( not)? match (((\/.\/)\|(#.#))([a-z]+)?)$/` - Match file contents against a regex. `Then /^(STDOUT\|STDERR) should( not)? match (((\/.\/)\|(#.#))([a-z]+)?)$/` - Match STDOUT or STDERR against a regex. `Then /^an email should (be sent\|not be sent)$/` - Expect an email to be sent (or not). * `Then the HTTP status code should be :code` - Expect the HTTP status code for visiting `http://localhost:8080`.	8.48 KB	2026-03-21 17:12
📄 LICENSE.md Copyright (c) 2016 runcommand, LLC Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.	1.03 KB	2025-05-25 12:40
📄 README.md wp-cli/doctor-command ===================== Diagnose problems within WordPress by running a series of checks for symptoms. [![Testing](https://github.com/wp-cli/doctor-command/actions/workflows/testing.yml/badge.svg)](https://github.com/wp-cli/doctor-command/actions/workflows/testing.yml) Quick links: [Overview](#overview) \| [Using](#using) \| [Installing](#installing) \| [Contributing](#contributing) ## Overview `wp doctor` lets you easily run a series of configurable checks to diagnose what's ailing with WordPress. Without `wp doctor`, your team has to rely on their memory to manually debug problems. With `wp doctor`, your team saves hours identifying the health of your WordPress installs by codifying diagnosis procedures as a series of checks to run with WP-CLI. `wp doctor` [comes with dozens of checks out of the box](https://make.wordpress.org/cli/handbook/guides/doctor/doctor-default-checks/), and [supports customized `doctor.yml` files](https://make.wordpress.org/cli/handbook/guides/doctor/doctor-customize-config/) to define the checks that are most important to you. Each check includes a name, status (either "success", "warning", or "error"), and a human-readable message. For example, `cron-count` is a check to ensure WP Cron hasn't exploded with jobs: ``` $ wp doctor check cron-count +------------+---------+--------------------------------------------------------------------+ \| name \| status \| message \| +------------+---------+--------------------------------------------------------------------+ \| cron-count \| success \| Total number of cron jobs is within normal operating expectations. \| +------------+---------+--------------------------------------------------------------------+ ``` Want to pipe the results into another system? Use `--format=json` or `--format=csv` to render checks in a machine-readable format. `wp doctor` is designed for extensibility. Create a custom `doctor.yml` file to define additional checks you deem necessary for your system: ``` plugin-w3-total-cache: check: Plugin_Status options: name: w3-total-cache status: uninstalled ``` Then, run the custom `doctor.yml` file using the `--config=<file>` parameter: ``` $ wp doctor check --fields=name,status --all --config=doctor.yml +-----------------------+--------+ \| name \| status \| +-----------------------+--------+ \| plugin-w3-total-cache \| error \| +-----------------------+--------+ ``` Running all checks together, `wp doctor` is the fastest way to get a high-level overview to the health of your WordPress installs. ## Using This package implements the following commands: ### wp doctor Diagnose what ails WordPress. ~~~ wp doctor ~~~ EXAMPLES # Verify WordPress core is up to date. $ wp doctor check core-update +-------------+---------+-----------------------------------------------------------+ \| name \| status \| message \| +-------------+---------+-----------------------------------------------------------+ \| core-update \| warning \| A new major version of WordPress is available for update. \| +-------------+---------+-----------------------------------------------------------+ # List checks to run. $ wp doctor list +----------------------------+--------------------------------------------------------------------------------+ \| name \| description \| +----------------------------+--------------------------------------------------------------------------------+ \| autoload-options-size \| Warns when autoloaded options size exceeds threshold of 900 kb. \| \| constant-savequeries-falsy \| Confirms expected state of the SAVEQUERIES constant. \| \| constant-wp-debug-falsy \| Confirms expected state of the WP_DEBUG constant. \| \| core-update \| Errors when new WordPress minor release is available; warns for major release. \| ### wp doctor check Run a series of checks against WordPress to diagnose issues. ~~~ wp doctor check [<checks>...] [--all] [--spotlight] [--config=<file>] [--fields=<fields>] [--<field>=<value>] [--format=<format>] ~~~ A check is a routine run against some scope of WordPress that reports a 'status' and a 'message'. The status can be 'success', 'warning', or 'error'. The message is a human-readable explanation of the status. If any of the checks fail, then the command will exit with the code `1`. OPTIONS [<checks>...] Names of one or more checks to run. [--all] Run all registered checks. [--spotlight] Focus on warnings and errors; ignore any successful checks. [--config=<file>] Use checks registered in a specific configuration file. [--fields=<fields>] Limit the output to specific fields. [--<field>=<value>] Filter results by key=value pairs. [--format=<format>] Render results in a particular format. --- default: table options: - table - json - csv - yaml - count --- AVAILABLE FIELDS These fields will be displayed by default for each check: * name * status * message EXAMPLES # Verify WordPress core is up to date. $ wp doctor check core-update +-------------+---------+-----------------------------------------------------------+ \| name \| status \| message \| +-------------+---------+-----------------------------------------------------------+ \| core-update \| warning \| A new major version of WordPress is available for update. \| +-------------+---------+-----------------------------------------------------------+ # Verify the site is public as expected. $ wp doctor check option-blog-public +--------------------+--------+--------------------------------------------+ \| name \| status \| message \| +--------------------+--------+--------------------------------------------+ \| option-blog-public \| error \| Site is private but expected to be public. \| +--------------------+--------+--------------------------------------------+ ### wp doctor list List all available checks to run. ~~~ wp doctor list [--config=<file>] [--fields=<fields>] [--format=<format>] ~~~ OPTIONS [--config=<file>] Use checks registered in a specific configuration file. [--fields=<fields>] Limit the output to specific fields. [--format=<format>] Render output in a specific format. --- default: table options: - table - json - csv - count --- AVAILABLE FIELDS These fields will be displayed by default for each check: * name * description EXAMPLES # List checks to run. $ wp doctor list +----------------------------+--------------------------------------------------------------------------------+ \| name \| description \| +----------------------------+--------------------------------------------------------------------------------+ \| autoload-options-size \| Warns when autoloaded options size exceeds threshold of 900 kb. \| \| constant-savequeries-falsy \| Confirms expected state of the SAVEQUERIES constant. \| \| constant-wp-debug-falsy \| Confirms expected state of the WP_DEBUG constant. \| \| core-update \| Errors when new WordPress minor release is available; warns for major release. \| ## Installing Installing this package requires WP-CLI v2.12 or greater. Update to the latest stable release with `wp cli update`. Once you've done so, you can install the latest stable version of this package with: ```bash wp package install wp-cli/doctor-command:@stable ``` To install the latest development version of this package, use the following command instead: ```bash wp package install wp-cli/doctor-command:dev-main ``` ## Contributing We appreciate you taking the initiative to contribute to this project. Contributing isn’t limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation. For a more thorough introduction, [check out WP-CLI's guide to contributing](https://make.wordpress.org/cli/handbook/contributing/). This package follows those policy and guidelines. ### Reporting a bug Think you’ve found a bug? We’d love for you to help us get it fixed. Before you create a new issue, you should [search existing issues](https://github.com/wp-cli/doctor-command/issues?q=label%3Abug%20) to see if there’s an existing resolution to it, or if it’s already been fixed in a newer version. Once you’ve done a bit of searching and discovered there isn’t an open or fixed issue for your bug, please [create a new issue](https://github.com/wp-cli/doctor-command/issues/new). Include as much detail as you can, and clear steps to reproduce if possible. For more guidance, [review our bug report documentation](https://make.wordpress.org/cli/handbook/bug-reports/). ### Creating a pull request Want to contribute a new feature? Please first [open a new issue](https://github.com/wp-cli/doctor-command/issues/new) to discuss whether the feature is a good fit for the project. Once you've decided to commit the time to seeing your pull request through, [please follow our guidelines for creating a pull request](https://make.wordpress.org/cli/handbook/pull-requests/) to make sure it's a pleasant experience. See "[Setting up](https://make.wordpress.org/cli/handbook/pull-requests/#setting-up)" for details specific to working on this package locally. This README.md is generated dynamically from the project's codebase using `wp scaffold package-readme` ([doc](https://github.com/wp-cli/scaffold-package-command#wp-scaffold-package-readme)). To suggest changes, please submit a pull request against the corresponding part of the codebase.	10.08 KB	2025-09-06 07:07
📄 behat.yml default: suites: default: contexts: - WP_CLI\Tests\Context\FeatureContext paths: - features	126 B	2025-09-06 07:07
📁 bin	-	2025-05-25 12:40
📄 composer.json { "name": "wp-cli/doctor-command", "type": "wp-cli-package", "description": "Diagnose problems within WordPress by running a series of checks for symptoms.", "homepage": "https://runcommand.io/wp/doctor/", "license": "MIT", "authors": [ { "name": "Daniel Bachhuber", "email": "daniel@runcommand.io", "homepage": "https://runcommand.io" } ], "require": { "ext-json": "*", "wp-cli/checksum-command": "^2", "wp-cli/core-command": "^2", "wp-cli/cron-command": "^2", "wp-cli/entity-command": "^2", "wp-cli/extension-command": "^2", "wp-cli/language-command": "^2", "wp-cli/wp-cli": "^2.12" }, "require-dev": { "wp-cli/wp-cli-tests": "^5" }, "config": { "process-timeout": 7200, "sort-packages": true, "allow-plugins": { "dealerdirect/phpcodesniffer-composer-installer": true, "johnpbloch/wordpress-core-installer": true, "phpstan/extension-installer": true }, "lock": false }, "extra": { "branch-alias": { "dev-main": "2.x-dev" }, "commands": [ "doctor", "doctor check", "doctor list" ], "readme": { "sections": [ "Overview", "Using", "Installing", "Contributing" ], "overview": { "body": "bin/readme/overview-body.md" } } }, "autoload": { "psr-4": { "WP_CLI\\Doctor\\": "src/" }, "files": [ "doctor-command.php" ] }, "minimum-stability": "dev", "prefer-stable": true, "scripts": { "behat": "run-behat-tests", "behat-rerun": "rerun-behat-tests", "lint": "run-linter-tests", "phpcs": "run-phpcs-tests", "phpstan": "run-phpstan-tests", "phpcbf": "run-phpcbf-cleanup", "phpunit": "run-php-unit-tests", "prepare-tests": "install-package-tests", "test": [ "@lint", "@phpcs", "@phpstan", "@phpunit", "@behat" ] } }	2.25 KB	2025-09-06 07:07
📄 doctor-command.php <?php if ( ! class_exists( 'WP_CLI' ) ) { return; } $wpcli_doctor_autoloader = __DIR__ . '/vendor/autoload.php'; if ( file_exists( $wpcli_doctor_autoloader ) ) { require_once $wpcli_doctor_autoloader; } WP_CLI::add_command( 'doctor', 'WP_CLI\Doctor\Command' );	267 B	2025-09-06 07:07
📄 doctor.yml # Default check configuration for `wp doctor` autoload-options-size: check: Autoload_Options_Size constant-savequeries-falsy: check: Constant_Definition options: constant: SAVEQUERIES falsy: true constant-wp-debug-falsy: check: Constant_Definition options: constant: WP_DEBUG falsy: true core-update: check: Core_Update core-verify-checksums: check: Core_Verify_Checksums cron-count: check: Cron_Count cron-duplicates: check: Cron_Duplicates file-eval: check: File_Contents options: regex: eval\(.base64_decode\(. option-blog-public: check: Option_Value options: option: blog_public value: 1 plugin-active-count: check: Plugin_Active_Count plugin-deactivated: check: Plugin_Deactivated plugin-update: check: Plugin_Update theme-update: check: Theme_Update cache-flush: check: Cache_Flush php-in-upload: check: PHP_In_Upload language-update: check: Language_Update	934 B	2025-05-25 12:40
📁 features	-	2026-03-21 17:12
📄 phpcs.xml.dist <?xml version="1.0"?> <ruleset name="WP-CLI-doctor"> <description>Custom ruleset for WP-CLI doctor-command</description> <!-- ############################################################################# COMMAND LINE ARGUMENTS For help understanding this file: https://github.com/squizlabs/PHP_CodeSniffer/wiki/Annotated-ruleset.xml For help using PHPCS: https://github.com/squizlabs/PHP_CodeSniffer/wiki/Usage ############################################################################# --> <!-- What to scan. --> <file>.</file> <!-- Show progress. --> <arg value="p"/> <!-- Strip the filepaths down to the relevant bit. --> <arg name="basepath" value="./"/> <!-- Check up to 8 files simultaneously. --> <arg name="parallel" value="8"/> <!-- ############################################################################# USE THE WP_CLI_CS RULESET ############################################################################# --> <rule ref="WP_CLI_CS"> <!-- Ignore namespace prefix for now, package should be ported to PSR-4. --> <exclude name="WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedNamespaceFound"/> <!-- Ignore underscore prefix for base class members. --> <exclude name="PSR2.Classes.PropertyDeclaration.Underscore"/> </rule> <!-- ############################################################################# PROJECT SPECIFIC CONFIGURATION FOR SNIFFS ############################################################################# --> <!-- For help understanding the `testVersion` configuration setting: https://github.com/PHPCompatibility/PHPCompatibility#sniffing-your-code-for-compatibility-with-specific-php-versions --> <config name="testVersion" value="7.2-"/> </ruleset>	1.71 KB	2025-09-06 07:07
📁 src	-	2026-03-21 17:12
📄 wp-cli.yml require: - doctor-command.php	32 B	2025-09-06 07:07

Edit File:

Terminal