← All changes
|
jetpack_vendor/automattic/jetpack-seo/src/class-initializer.php
+1
-29
16.3-a.3
→
16.3-beta
View file →
| @@ -27,9 +27,9 @@ | ||
| 27 | 27 | * Jetpack SEO package version. |
| 28 | 28 | * |
| 29 | 29 | * @var string |
| 30 | 30 | */ |
| 31 | - const PACKAGE_VERSION = '0.9.5'; | |
| 31 | + const PACKAGE_VERSION = '0.9.8'; | |
| 32 | 32 | |
| 33 | 33 | /** |
| 34 | 34 | * WordPress.com site feature that enables the Jetpack SEO surface. |
| 35 | 35 | * |
| @@ -59,22 +59,8 @@ | ||
| 59 | 59 | */ |
| 60 | 60 | const SCRIPT_DATA_KEY = 'seo'; |
| 61 | 61 | |
| 62 | 62 | /** |
| 63 | - * Option recording whether sitemap generation is enabled. | |
| 64 | - * | |
| 65 | - * Read in place of the standalone `sitemaps` module's active state. Module-active | |
| 66 | - * state is filtered against the modules present on disk, so once that module is | |
| 67 | - * removed it would read as inactive even for sites that had it on. A one-time | |
| 68 | - * migration in the Jetpack plugin seeds this option from the site's existing module | |
| 69 | - * state and keeps it in sync while the legacy module still exists. See | |
| 70 | - * `Jetpack::migrate_sitemaps_module_to_seo_option()`. | |
| 71 | - * | |
| 72 | - * @var string | |
| 73 | - */ | |
| 74 | - const SITEMAP_ENABLED_OPTION = 'jetpack_seo_sitemap_enabled'; | |
| 75 | - | |
| 76 | - /** | |
| 77 | 63 | * Option recording that the user has deliberately turned the site's sitemap OFF, |
| 78 | 64 | * so WordPress core's own sitemap should be suppressed too ("off" means no sitemap |
| 79 | 65 | * at all, not a fallback to `/wp-sitemap.xml`). |
| 80 | 66 | * |
| @@ -87,22 +73,8 @@ | ||
| 87 | 73 | * |
| 88 | 74 | * @var string |
| 89 | 75 | */ |
| 90 | 76 | const SUPPRESS_WP_SITEMAP_OPTION = 'jetpack_seo_suppress_wp_sitemap'; |
| 91 | - | |
| 92 | - /** | |
| 93 | - * Option recording whether canonical URLs are enabled. | |
| 94 | - * | |
| 95 | - * Read in place of the standalone `canonical-urls` module's active state. Module-active | |
| 96 | - * state is filtered against the modules present on disk, so once that module is | |
| 97 | - * removed it would read as inactive even for sites that had it on. A one-time | |
| 98 | - * migration in the Jetpack plugin seeds this option from the site's existing module | |
| 99 | - * state and keeps it in sync while the legacy module still exists. See | |
| 100 | - * `Jetpack::migrate_canonical_urls_module_to_seo_option()`. | |
| 101 | - * | |
| 102 | - * @var string | |
| 103 | - */ | |
| 104 | - const CANONICAL_ENABLED_OPTION = 'jetpack_seo_canonical_urls_enabled'; | |
| 105 | 77 | |
| 106 | 78 | /** |
| 107 | 79 | * Option recording whether the Jetpack SEO surface is discoverable on this site. |
| 108 | 80 | * |