mirror of
https://github.com/WordPress/WordPress.git
synced 2024-12-27 11:38:01 +01:00
c03305852e
Dynamic (non-explicitly declared) properties are deprecated as of PHP 8.2 and are expected to become a fatal error in PHP 9.0. There are a number of ways to mitigate this: * If it is an accidental typo for a declared property: fix the typo. * For known properties: declare them on the class. * For unknown properties: add the magic `__get()`, `__set()`, et al. methods to the class or let the class extend `stdClass` which has highly optimized versions of these magic methods built in. * For unknown ''use'' of dynamic properties, the `#[AllowDynamicProperties]` attribute can be added to the class. The attribute will automatically be inherited by child classes. Trac ticket #56034 is open to investigate and handle the third and fourth type of situations, however it has become clear this will need more time and will not be ready in time for WP 6.1. To reduce “noise” in the meantime, both in the error logs of WP users moving onto PHP 8.2, in the test run logs of WP itself, in test runs of plugins and themes, as well as to prevent duplicate tickets from being opened for the same issue, this commit adds the `#[AllowDynamicProperties]` attribute to all “parent” classes in WP. The logic used for this commit is as follows: * If a class already has the attribute: no action needed. * If a class does not `extend`: add the attribute. * If a class does `extend`: - If it extends `stdClass`: no action needed (as `stdClass` supports dynamic properties). - If it extends a PHP native class: add the attribute. - If it extends a class from one of WP's external dependencies: add the attribute. * In all other cases: no action — the attribute should not be needed as child classes inherit from the parent. Whether or not a class contains magic methods has not been taken into account, as a review of the currently existing magic methods has shown that those are generally not sturdy enough and often even set dynamic properties (which they should not). See the [https://www.youtube.com/watch?v=vDZWepDQQVE live stream from August 16, 2022] for more details. This commit only affects classes in the `src` directory of WordPress core. * Tests should not get this attribute, but should be fixed to not use dynamic properties instead. Patches for this are already being committed under ticket #56033. * While a number bundled themes (2014, 2019, 2020, 2021) contain classes, they are not a part of this commit and may be updated separately. Reference: [https://wiki.php.net/rfc/deprecate_dynamic_properties PHP RFC: Deprecate dynamic properties]. Follow-up to [53922]. Props jrf, hellofromTonya, markjaquith, peterwilsoncc, costdev, knutsp, aristath. See #56513, #56034. Built from https://develop.svn.wordpress.org/trunk@54133 git-svn-id: http://core.svn.wordpress.org/trunk@53692 1a063a9b-81f0-0310-95a4-ce76da25c4cd
97 lines
2.0 KiB
PHP
97 lines
2.0 KiB
PHP
<?php
|
|
/**
|
|
* Sitemaps: WP_Sitemaps_Index class.
|
|
*
|
|
* Generates the sitemap index.
|
|
*
|
|
* @package WordPress
|
|
* @subpackage Sitemaps
|
|
* @since 5.5.0
|
|
*/
|
|
|
|
/**
|
|
* Class WP_Sitemaps_Index.
|
|
* Builds the sitemap index page that lists the links to all of the sitemaps.
|
|
*
|
|
* @since 5.5.0
|
|
*/
|
|
#[AllowDynamicProperties]
|
|
class WP_Sitemaps_Index {
|
|
/**
|
|
* The main registry of supported sitemaps.
|
|
*
|
|
* @since 5.5.0
|
|
* @var WP_Sitemaps_Registry
|
|
*/
|
|
protected $registry;
|
|
|
|
/**
|
|
* Maximum number of sitemaps to include in an index.
|
|
*
|
|
* @since 5.5.0
|
|
*
|
|
* @var int Maximum number of sitemaps.
|
|
*/
|
|
private $max_sitemaps = 50000;
|
|
|
|
/**
|
|
* WP_Sitemaps_Index constructor.
|
|
*
|
|
* @since 5.5.0
|
|
*
|
|
* @param WP_Sitemaps_Registry $registry Sitemap provider registry.
|
|
*/
|
|
public function __construct( WP_Sitemaps_Registry $registry ) {
|
|
$this->registry = $registry;
|
|
}
|
|
|
|
/**
|
|
* Gets a sitemap list for the index.
|
|
*
|
|
* @since 5.5.0
|
|
*
|
|
* @return array[] Array of all sitemaps.
|
|
*/
|
|
public function get_sitemap_list() {
|
|
$sitemaps = array();
|
|
|
|
$providers = $this->registry->get_providers();
|
|
/* @var WP_Sitemaps_Provider $provider */
|
|
foreach ( $providers as $name => $provider ) {
|
|
$sitemap_entries = $provider->get_sitemap_entries();
|
|
|
|
// Prevent issues with array_push and empty arrays on PHP < 7.3.
|
|
if ( ! $sitemap_entries ) {
|
|
continue;
|
|
}
|
|
|
|
// Using array_push is more efficient than array_merge in a loop.
|
|
array_push( $sitemaps, ...$sitemap_entries );
|
|
if ( count( $sitemaps ) >= $this->max_sitemaps ) {
|
|
break;
|
|
}
|
|
}
|
|
|
|
return array_slice( $sitemaps, 0, $this->max_sitemaps, true );
|
|
}
|
|
|
|
/**
|
|
* Builds the URL for the sitemap index.
|
|
*
|
|
* @since 5.5.0
|
|
*
|
|
* @global WP_Rewrite $wp_rewrite WordPress rewrite component.
|
|
*
|
|
* @return string The sitemap index URL.
|
|
*/
|
|
public function get_index_url() {
|
|
global $wp_rewrite;
|
|
|
|
if ( ! $wp_rewrite->using_permalinks() ) {
|
|
return home_url( '/?sitemap=index' );
|
|
}
|
|
|
|
return home_url( '/wp-sitemap.xml' );
|
|
}
|
|
}
|