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
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.
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
12:39:29 GMT+0000
Password-protected posts are accounted for when using protected_content feature.
12:39:25 GMT+0000
The Parse.ly Plugin 2.5 branch is no longer available as an option to load in the platform.
08:44:18 GMT+0000
Fix an issue when tracking would not work for filters that require a return value.
11:09:46 GMT+0000
We fixed a case in which the tracking would not be correctly send on the Parse.ly Recommended Widget.
18:01:51 GMT+0000
Add js_concat_script_attributes filter to allow for adding script attributes to concatenated scripts.
18:01:43 GMT+0000
Fix the use of an uninitialized value in wpcom_vip_get_adjacent_post() when $excluded_terms is not empty.
18:01:38 GMT+0000
We have added Jetpack 10.3-beta. If you want to try this beta, you need to pin your site to use Jetpack 10.3 by adding this line to your vip-config.php:
define( 'VIP_JETPACK_PINNED_VERSION', '10.3' );