sdc-build-wp 4.1.0 → 4.1.2

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/NamingConventions/PrefixAllGlobalsStandard.xml

@@ -1,119 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Prefix All Globals"
-    >
-    <standard>
-    <![CDATA[
-    All globals terms must be prefixed with a theme/plugin specific term. Global terms include Namespace names, Class/Interface/Trait/Enum names (when not namespaced), Functions (when not namespaced or in an OO structure), Constants/Variable names declared in the global namespace, and Hook names.
-
-    A prefix must be distinct and unique to the plugin/theme, in order to prevent potential conflicts with other plugins/themes and with WordPress itself.
-
-    The prefix used for a plugin/theme may be chosen by the developers and should be defined in a custom PHPCS ruleset to allow for this sniff to verify that the prefix is consistently used.
-    Prefixes will be treated in a case-insensitive manner.
-    https://github.com/WordPress/WordPress-Coding-Standards/wiki/Customizable-sniff-properties#naming-conventions-prefix-everything-in-the-global-namespace
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: Using the prefix ECPT_">
-        <![CDATA[
-define( <em>'ECPT_VERSION'</em>, '1.0' );
-
-<em>$ecpt_admin</em> = new ECPT_Admin_Page();
-
-class <em>ECPT_Admin_Page</em> {}
-
-apply_filter(
-    <em>'ecpt_modify_content'</em>,
-    $ecpt_content
-);
-        ]]>
-        </code>
-        <code title="Invalid: non-prefixed code">
-        <![CDATA[
-define( <em>'PLUGIN_VERSION'</em>, '1.0' );
-
-<em>$admin</em> = new Admin_Page();
-
-class <em>Admin_Page</em> {}
-
-apply_filter(
-    <em>'modify_content'</em>,
-    $content
-);
-        ]]>
-        </code>
-    </code_comparison>
-    <code_comparison>
-        <code title="Valid: Using the prefix ECPT_ in namespaced code">
-        <![CDATA[
-namespace <em>ECPT_Plugin\Admin</em>;
-
-// Constants declared using `const` will
-// be namespaced and therefore prefixed.
-const VERSION = 1.0;
-
-// A class declared in a (prefixed) namespace
-// is automatically prefixed.
-class Admin_Page {}
-
-// Variables in a namespaced file are not
-// namespaced, so still need prefixing.
-<em>$ecpt_admin</em> = new Admin_Page();
-
-// Hook names are not subject to namespacing.
-apply_filter(
-    <em>'ecpt_modify_content'</em>,
-    $ecpt_content
-);
-        ]]>
-        </code>
-        <code title="Invalid: using a non-prefixed namespace">
-        <![CDATA[
-namespace <em>Admin</em>;
-
-// As the namespace is not prefixed, this
-// is still bad.
-const VERSION = 1.0;
-
-// As the namespace is not prefixed, this
-// is still bad.
-class Admin_Page {}
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    Using prefixes reserved for WordPress is not permitted, even if WordPress is not currently using the prefix (yet).
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: Using the prefix mycoolplugin_">
-        <![CDATA[
-function <em>mycoolplugin_save_post()</em> {}
-        ]]>
-        </code>
-        <code title="Invalid: Using a WordPress reserved prefix wp_">
-        <![CDATA[
-function <em>wp_save_post()</em> {}
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    Prefixes must have a minimum length of three character to be considered valid, as many plugins and themes share the same initials.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: Using the distinct prefix MyPlugin">
-        <![CDATA[
-interface <em>MyPluginIsCool</em> {}
-        ]]>
-        </code>
-        <code title="Invalid: Using a two-letter prefix My">
-        <![CDATA[
-interface <em>My</em> {}
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/NamingConventions/ValidHookNameStandard.xml

@@ -1,35 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Valid Hook Name"
-    >
-    <standard>
-    <![CDATA[
-    Use lowercase letters in action and filter names. Separate words using underscores.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: lowercase hook name.">
-        <![CDATA[
-do_action( <em>'prefix_hook_name'</em>, $var );
-        ]]>
-        </code>
-        <code title="Invalid: mixed case hook name.">
-        <![CDATA[
-do_action( <em>'Prefix_Hook_NAME'</em>, $var );
-        ]]>
-        </code>
-    </code_comparison>
-    <code_comparison>
-        <code title="Valid: words separated by underscores.">
-        <![CDATA[
-apply_filters( <em>'prefix_hook_name'</em>, $var );
-        ]]>
-        </code>
-        <code title="Invalid: using non-underscore characters to separate words.">
-        <![CDATA[
-apply_filters( <em>'prefix\hook-name'</em>, $var );
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/NamingConventions/ValidPostTypeSlugStandard.xml

@@ -1,121 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Valid Post Type Slug"
-    >
-    <standard>
-    <![CDATA[
-    The post type slug used in register_post_type() must be between 1 and 20 characters.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: short post type slug.">
-        <![CDATA[
-register_post_type( 
-    <em>'my_short_slug'</em>, 
-    array() 
-);
-        ]]>
-        </code>
-        <code title="Invalid: too long post type slug.">
-        <![CDATA[
-register_post_type( 
-    <em>'my_own_post_type_too_long'</em>, 
-    array() 
-);
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    The post type slug used in register_post_type() can only contain lowercase alphanumeric characters, dashes and underscores.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: no special characters in post type slug.">
-        <![CDATA[
-register_post_type( 
-    <em>'my_post_type_slug'</em>, 
-    array() 
-);
-        ]]>
-        </code>
-        <code title="Invalid: invalid characters in post type slug.">
-        <![CDATA[
-register_post_type( 
-    <em>'my/post/type/slug'</em>, 
-    array() 
-);
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    One should be careful with passing dynamic slug names to "register_post_type()", as the slug may become too long and could contain invalid characters.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: static post type slug.">
-        <![CDATA[
-register_post_type( 
-    <em>'my_post_active'</em>, 
-    array() 
-);
-        ]]>
-        </code>
-        <code title="Invalid: dynamic post type slug.">
-        <![CDATA[
-register_post_type( 
-    <em>"my_post_{$status}"</em>, 
-    array() 
-);
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    The post type slug used in register_post_type() can not use reserved keywords, such as the ones used by WordPress itself.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: prefixed post slug.">
-        <![CDATA[
-register_post_type( 
-    <em>'prefixed_author'</em>, 
-    array() 
-);
-        ]]>
-        </code>
-        <code title="Invalid: using a reserved keyword as slug.">
-        <![CDATA[
-register_post_type( 
-    <em>'author'</em>, 
-    array() 
-);
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    The post type slug used in register_post_type() can not use reserved prefixes, such as 'wp_', which is used by WordPress itself.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: custom prefix post slug.">
-        <![CDATA[
-register_post_type( 
-    <em>'prefixed_author'</em>, 
-    array() 
-);
-        ]]>
-        </code>
-        <code title="Invalid: using a reserved prefix.">
-        <![CDATA[
-register_post_type( 
-    <em>'wp_author'</em>, 
-    array() 
-);
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/PHP/IniSetStandard.xml

@@ -1,40 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Detect Use Of `ini_set()"
-    >
-    <standard>
-    <![CDATA[
-      Using ini_set() and similar functions for altering PHP settings at runtime is discouraged. Changing runtime configuration might break other plugins and themes, and even WordPress itself.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: ini_set() for a possibly breaking setting.">
-        <![CDATA[
-// ini_set() should not be used.
-        ]]>
-        </code>
-        <code title="Invalid: ini_set() for a possibly breaking setting.">
-        <![CDATA[
-ini_set( <em>'short_open_tag'</em>, 'off' );
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-      For some configuration values there are alternative ways available - either via WordPress native functionality of via standard PHP - to achieve the same without the risk of breaking interoperability. These alternatives are preferred.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: WordPress functional alternative.">
-        <![CDATA[
-<em>wp_raise_memory_limit();</em>
-        ]]>
-        </code>
-        <code title="Invalid: ini_set() to alter memory limits.">
-        <![CDATA[
-ini_set( <em>'memory_limit'</em>, '256M' );
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/PHP/StrictInArrayStandard.xml

@@ -1,53 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Strict In Array Syntax"
-    >
-    <standard>
-    <![CDATA[
-    When using functions which compare a value to a range of values in an array, make sure a strict comparison is executed.
-
-    Typically, this rule verifies function calls to the PHP native `in_array()`, `array_search()` and `array_keys()` functions pass the `$strict` parameter.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: calling in_array() with the $strict parameter set to `true`.">
-        <![CDATA[
-$array = array( '1', 1, true );
-if ( in_array( $value, $array, <em>true</em> ) ) {}
-        ]]>
-        </code>
-        <code title="Invalid: calling in_array() without passing the $strict parameter.">
-        <![CDATA[
-$array = array( '1', 1, true );
-if ( in_array( $value, $array<em> </em>) ) {}
-        ]]>
-        </code>
-    </code_comparison>
-
-    <code_comparison>
-        <code title="Valid: calling array_search() with the $strict parameter set to `true`.">
-        <![CDATA[
-$key = array_search( 1, $array, <em>true</em> );
-        ]]>
-        </code>
-        <code title="Invalid: calling array_search() without passing the $strict parameter.">
-        <![CDATA[
-$key = array_search( 1, $array<em> </em>);
-        ]]>
-        </code>
-    </code_comparison>
-
-    <code_comparison>
-        <code title="Valid: calling array_keys() with a $search_value and the $strict parameter set to `true`.">
-        <![CDATA[
-$keys = array_keys( $array, $key, <em>true</em> );
-        ]]>
-        </code>
-        <code title="Invalid: calling array_keys() with a $search_value without passing the $strict parameter.">
-        <![CDATA[
-$keys = array_keys( $array, $key<em> </em>);
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/PHP/YodaConditionsStandard.xml

@@ -1,27 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Yoda Conditions"
-    >
-    <standard>
-    <![CDATA[
-    When doing logical comparisons involving variables, the variable must be placed on the right side. All constants, literals, and function calls must be placed on the left side. If neither side is a variable, the order is unimportant.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: The variable is placed on the right">
-        <![CDATA[
-if ( <em>true === $the_force</em> ) {
-    $victorious = you_will( $be );
-}
-        ]]>
-        </code>
-        <code title="Invalid: The variable has been placed on the left">
-        <![CDATA[
-if ( <em>$the_force === false</em> ) {
-    $victorious = you_will_not( $be );
-}
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/Security/SafeRedirectStandard.xml

@@ -1,23 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Safe Redirect"
-    >
-    <standard>
-    <![CDATA[
-    wp_safe_redirect() should be used whenever possible to prevent open redirect vulnerabilities. One of the main uses of an open redirect vulnerability is to make phishing attacks more credible. In this case the user sees your (trusted) domain and might get redirected to an attacker controlled website aimed at stealing private information.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: Redirect can only go to allowed domains.">
-        <![CDATA[
-<em>wp_safe_redirect</em>( $location );
-        ]]>
-        </code>
-        <code title="Invalid: Unsafe redirect, can be abused.">
-        <![CDATA[
-<em>wp_redirect</em>( $location );
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WP/CapabilitiesStandard.xml

@@ -1,69 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Capabilities"
-    >
-    <standard>
-    <![CDATA[
-Capabilities passed should be valid capabilities (custom capabilities can be added in the ruleset).
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: a WP native or registered custom user capability is used.">
-        <![CDATA[
-if ( author_can( $post, <em>'manage_sites'</em> ) ) { }
-        ]]>
-        </code>
-        <code title="Invalid: unknown/unsupported user capability is used.">
-        <![CDATA[
-map_meta_cap( <em>'manage_site'</em>, $user->ID );
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-Always use user capabilities instead of roles.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: user capability is used.">
-        <![CDATA[
-add_options_page(
-    esc_html__( 'Options', 'textdomain' ),
-    esc_html__( 'Options', 'textdomain' ),
-    <em>'manage_options'</em>,
-    'options_page_slug',
-    'project_options_page_cb'
-);
-        ]]>
-        </code>
-        <code title="Invalid: user role is used instead of a capability.">
-        <![CDATA[
-add_options_page(
-    esc_html__( 'Options', 'textdomain' ),
-    esc_html__( 'Options', 'textdomain' ),
-    <em>'author'</em>,
-    'options_page_slug',
-    'project_options_page_cb'
-);
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-Don't use deprecated capabilities.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: a WP native or registered custom user capability is used.">
-        <![CDATA[
-if ( author_can( $post, <em>'read'</em> ) ) { }
-        ]]>
-        </code>
-        <code title="Invalid: deprecated user capability is used.">
-        <![CDATA[
-if ( author_can( $post, <em>'level_6'</em> ) ) { }
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WP/CapitalPDangitStandard.xml

@@ -1,43 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Capital P Dangit"
-    >
-    <standard>
-    <![CDATA[
-The correct spelling of "WordPress" should be used in text strings, comments and object names.
-
-In select cases, when part of an identifier or a URL, WordPress does not have to be capitalized.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: WordPress is correctly capitalized.">
-        <![CDATA[
-class <em>WordPress</em>_Example {
-
-    /**
-     * This function is about <em>WordPress</em>.
-     */
-    public function explain() {
-        echo 'This is an explanation
-            about <em>WordPress</em>.';
-    }
-}
-        ]]>
-        </code>
-        <code title="Invalid: WordPress is not correctly capitalized.">
-        <![CDATA[
-class <em>Wordpress_Example</em> {
-
-    /**
-     * This function is about <em>Wordpress</em>.
-     */
-    public function explain() {
-        echo 'This is an explanation
-            about <em>wordpress</em>.';
-    }
-}
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WP/ClassNameCaseStandard.xml

@@ -1,23 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Class Name Case"
-    >
-    <standard>
-    <![CDATA[
-    It is strongly recommended to refer to WP native classes by their properly cased name.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: reference to a WordPress native class name using the correct case.">
-        <![CDATA[
-$obj = new WP_Query;
-        ]]>
-        </code>
-        <code title="Invalid: reference to a WordPress native class name not using the correct case.">
-        <![CDATA[
-$obj = new wp_query;
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WP/CronIntervalStandard.xml

@@ -1,45 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Cron Interval"
-    >
-    <standard>
-    <![CDATA[
-    Cron schedules running more often than once every 15 minutes are discouraged. Crons running that frequently can negatively impact the performance of a site.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: Cron schedule is created to run once every hour.">
-        <![CDATA[
-function adjust_schedules( $schedules ) {
-    $schedules['every_hour'] = array(
-        'interval' => <em>HOUR_IN_SECONDS</em>,
-        'display'  => __( 'Every hour' )
-    );
-    return $schedules;
-} 
-
-add_filter( 
-    'cron_schedules', 
-    'adjust_schedules'
-); 
-        ]]>
-        </code>
-        <code title="Invalid: Cron schedule is added to run more than once per 15 minutes.">
-        <![CDATA[
-function adjust_schedules( $schedules ) {
-    $schedules['every_9_mins'] = array(
-        'interval' => <em>9 * 60</em>,
-        'display'  => __( 'Every 9 minutes' )
-    );
-    return $schedules;
-} 
-
-add_filter( 
-    'cron_schedules', 
-    'adjust_schedules'
-);
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WP/DeprecatedClassesStandard.xml

@@ -1,23 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Deprecated Classes"
-    >
-    <standard>
-    <![CDATA[
-    Please refrain from using deprecated WordPress classes. 
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: use of a current (non-deprecated) class.">
-        <![CDATA[
-$a = new <em>WP_User_Query</em>();
-        ]]>
-        </code>
-        <code title="Invalid: use of a deprecated class.">
-        <![CDATA[
-$a = new <em>WP_User_Search</em>(); // Deprecated WP 3.1.
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WP/DeprecatedFunctionsStandard.xml

@@ -1,23 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Deprecated Functions"
-    >
-    <standard>
-    <![CDATA[
-    Please refrain from using deprecated WordPress functions. 
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: use of a current (non-deprecated) function.">
-        <![CDATA[
-$sites = <em>get_sites</em>();
-        ]]>
-        </code>
-        <code title="Invalid: use of a deprecated function.">
-        <![CDATA[
-$sites = <em>wp_get_sites</em>(); // Deprecated WP 4.6.
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WP/DeprecatedParameterValuesStandard.xml

@@ -1,23 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Deprecated Function Parameter Values"
-    >
-    <standard>
-    <![CDATA[
-    Please refrain from using deprecated WordPress function parameter values.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: passing a valid function parameter value.">
-        <![CDATA[
-bloginfo( <em>'url'</em> );
-        ]]>
-        </code>
-        <code title="Invalid: passing a deprecated function parameter value.">
-        <![CDATA[
-bloginfo ( <em>'home'</em> ); // Deprecated WP 2.2.0.
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>