22:14:48 GMT+0000
We enabled Parse.ly telemetry for all sites that have Parse.ly enabled.
Ready to get started with WordPress VIP? Contact Us
The VIP Platform Changelog includes updates made to the functionality and behavior of the platform's tooling (i.e. VIP Dashboard, VIP-CLI), VIP MU plugins, VIP File System, caching layers, and other underlying architecture and software.
22:14:48 GMT+0000
We enabled Parse.ly telemetry for all sites that have Parse.ly enabled.
22:14:45 GMT+0000
Fix PHP warning in Health::diff_document_and_prepared_document()
11:56:37 GMT+0000
To ensure the integrity of our clusters.
11:56:33 GMT+0000
Added function: vip_get_env_var as a shortcut to requiring Automattic\VIP\Environment::get_var
$my_env_var = vip_get_env_var( 'FOO', 'BAR' );
If the key, for the custom environment variable ("FOO") does not exist, the default value ( "BAR" ) will be returned.
11:56:28 GMT+0000
Fix typo of md_rand to mt_rand
11:56:24 GMT+0000
We’ve implemented a delay between validation batches to minimize the chances of causing a resource strain during periodic content validation.
11:56:20 GMT+0000
Update development dependencies to fix security issues:
11:56:16 GMT+0000
Internal dependency – ElasticPress was updated to v3.6.4 from v3.6.2.
The see all the changes please see EP release page
11:56:12 GMT+0000
Improve cacheability of the static assets.
11:56:08 GMT+0000
Update plugin to rev 85e6d94
18:23:40 GMT+0000
18:50:26 GMT+0000
Data syncs (production -> child env) will now run wp vip data-cleanup datasync directly inline during the sync job. This happens both before cron is re-enabled and before maintenance mode is lifted, helping better ensure the the cleanup hooks have run before any requests hit the application. A new hook has been introduced to perform actions during this cleanup: vip_datasync_cleanup (note that vip_go_migration_cleanup still runs, though there are plans to deprecate in the future).
SQL Imports (any env) will also run a similar wp vip data-cleanup sql-import directly inline as well. There is a new WP hook that can be used to perform actions during this cleanup: vip_sqlimport_cleanup.
Alongside those new cleanup processes, the WP options below are backed up before a data sync or SQL import takes place, then restored afterwards. The main reasoning behind this is to prevent production environments from sharing this data with their child environments, as they need to remain unique per environment.
'jetpack_options',
'jetpack_private_options',
'vaultpress',
'vip_jetpack_connection_pilot_heartbeat',
'wordpress_api_key',
'vip_search_index_versions',
'vip_search_global_index_versions',
16:56:46 GMT+0000
No need to perform a remote request since it will throw an index_not_found_exception.
16:56:04 GMT+0000
We’ve addressed an issue where potentially sensitive information may have been logged when the Elasticsearch server returns a Warning response.
16:55:29 GMT+0000
Includes the various changes:
16:54:56 GMT+0000
We upgraded Jetpack 10.2 to Jetpack 10.3
Jetpack 10.3 contains many new updates and more information can be found here: Jetpack 10.3 Release .
20:18:39 GMT+0000
Update from Jetpack 10.3-beta to the 10.3 tag, preparing for future release.
19:43:52 GMT+0000
Sites that have Parse.ly enabled will send telemetry to A8c’s Tracks.
19:42:10 GMT+0000
Previously we included a few classes, notably VIP_Request_Block and our custom error handler very early in the bootstrap, prior to loading the vip-config.php. Although those files are located in mu-plugins we didn’t load them from there.
We’ve made a change to include 000-pre-vip-config/requires.php that will now contain those early dependencies so that it’s more apparent.
19:41:06 GMT+0000
Show Autoloaded Options in Query Monitor