WP_Debug_Data::debug_data(): array

36	public static function debug_data() {37		/*38		 * Set up the array that holds all debug information.39		 *40		 * When iterating through the debug data, the ordering of the sections41		 * occurs in insertion-order of the assignments into this array.42		 *43		 * This is the single assignment of the sections before filtering. Null-entries will44		 * be automatically be removed.45		 */46		$info = array(47			'wp-core'             => self::get_wp_core(),48			'wp-paths-sizes'      => self::get_wp_paths_sizes(),49			'wp-dropins'          => self::get_wp_dropins(),50			'wp-active-theme'     => self::get_wp_active_theme(),51			'wp-parent-theme'     => self::get_wp_parent_theme(),52			'wp-themes-inactive'  => self::get_wp_themes_inactive(),53			'wp-mu-plugins'       => self::get_wp_mu_plugins(),54			'wp-plugins-active'   => self::get_wp_plugins_active(),55			'wp-plugins-inactive' => self::get_wp_plugins_inactive(),56			'wp-media'            => self::get_wp_media(),57			'wp-server'           => self::get_wp_server(),58			'wp-database'         => self::get_wp_database(),59			'wp-constants'        => self::get_wp_constants(),60			'wp-filesystem'       => self::get_wp_filesystem(),61		);62 63		/*64		 * Remove null elements from the array. The individual methods are65		 * allowed to return `null`, which communicates that the category66		 * of debug data isn't relevant and shouldn't be passed through.67		 */68		$info = array_filter(69			$info,70			static function ( $section ) {71				return isset( $section );72			}73		);74 75		/**76		 * Filters the debug information shown on the Tools -> Site Health -> Info screen.77		 *78		 * Plugin or themes may wish to introduce their own debug information without creating79		 * additional admin pages. They can utilize this filter to introduce their own sections80		 * or add more data to existing sections.81		 *82		 * Array keys for sections added by core are all prefixed with `wp-`. Plugins and themes83		 * should use their own slug as a prefix, both for consistency as well as avoiding84		 * key collisions. Note that the array keys are used as labels for the copied data.85		 *86		 * All strings are expected to be plain text except `$description` that can contain87		 * inline HTML tags (see below).88		 *89		 * @since 5.2.090		 *91		 * @param array $args {92		 *     The debug information to be added to the core information page.93		 *94		 *     This is an associative multi-dimensional array, up to three levels deep.95		 *     The topmost array holds the sections, keyed by section ID.96		 *97		 *     @type array ...$0 {98		 *         Each section has a `$fields` associative array (see below), and each `$value` in `$fields`99		 *         can be another associative array of name/value pairs when there is more structured data100		 *         to display.101		 *102		 *         @type string $label       Required. The title for this section of the debug output.103		 *         @type string $description Optional. A description for your information section which104		 *                                   may contain basic HTML markup, inline tags only as it is105		 *                                   outputted in a paragraph.106		 *         @type bool   $show_count  Optional. If set to `true`, the amount of fields will be included107		 *                                   in the title for this section. Default false.108		 *         @type bool   $private     Optional. If set to `true`, the section and all associated fields109		 *                                   will be excluded from the copied data. Default false.110		 *         @type array  $fields {111		 *             Required. An associative array containing the fields to be displayed in the section,112		 *             keyed by field ID.113		 *114		 *             @type array ...$0 {115		 *                 An associative array containing the data to be displayed for the field.