20:39:00 GMT+0000
This will sync the settings defined in code with the ES index settings via cron for all sites. Note that only some settings are synced.
https://github.com/Automattic/vip-go-mu-plugins/pull/2059
#mu-plugins, #search
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.
20:39:00 GMT+0000
This will sync the settings defined in code with the ES index settings via cron for all sites. Note that only some settings are synced.
https://github.com/Automattic/vip-go-mu-plugins/pull/2059
#mu-plugins, #search
20:39:00 GMT+0000
Updates ElasticPress to bring in a small fix for an undefined variable notice.
20:39:00 GMT+0000
We have added a new wp vip subsites update-wp-blogs command, which updates the domain and path values for a subsite in wp_blogs.
21:03:50 GMT+0000
Increases validate-contents cron for search from 10% to 25% of deployments.
21:03:37 GMT+0000
This increases the percentage of sites that receive automated index settings from 10% to 50%
21:03:33 GMT+0000
- index.max_result_window is a setting that controls the maximum number of documents that can be paginated through. This change limits the maximum number to be 9000.
21:53:42 GMT+0000
This feature, enabled on 10% of sites, will automatically update some index settings if they are found to be inconsistent with the desired state.
21:07:26 GMT+0000
Modifies the default index replica count in preparation for changing the index shard allocation settings.
21:07:09 GMT+0000
Rather than allowing index shards to be distributed around the cluster, this change ensures that indexes are placed in a site’s origin datacenter to be closer to the web containers.
This will only affect new indexes at first – existing indexes will be modified at a later time.
21:05:45 GMT+0000
We have added a new subtree for Jetpack 9.6, initially containing version 9.6-beta. If you want to try this beta, you can follow the testing guidelines.
As usual, you need to pin your site to use Jetpack 9.6 by adding this line to your vip-config.php:
define( 'VIP_JETPACK_PINNED_VERSION', '9.6' );
13:04:04 GMT+0000
We have systems in place that alert us when the size of the options grows too big to fit into a Memcached server entry to prevent increased pressure on the Memcached server and limit potential performance degradation.
We made changes to alerting logic to prevent false positives.
13:03:54 GMT+0000
Disable Gutenberg Ramp plugin for 25% of sites, using the Feature Flags. We will then continue to iterate based on the outcome of this deployment.
13:03:49 GMT+0000
This change adds an option flag for temporarily suppressing alloptions alerts, along with supporting WP-CLI commands to manage the flag.
13:03:36 GMT+0000
This change improves multisite site search within WP Admin by filtering site_search_columns to add domain to the columns to search in a WP_Site_Query search query.
21:04:40 GMT+0000
Switches to the new Environment class for determining sandbox and CLI container status, which can now come from environment variables in addition to the hostname.
19:09:30 GMT+0000
This adds a new Automattic\VIP\Environment utility class for determining details about the current environment (like if this is a sandbox or CLI/Batch container). This will replace existing logic that is hardcoded into 000-vip-init.php, making it testable.
17:27:02 GMT+0000
This Pull-Request will disable Gutenberg Ramp plugin for 10% of sites, using the Feature Flags. When merged and if everything looks good, we will disable it for further 10%, and so forth.
17:26:57 GMT+0000
Update to the alert message received for validate-contents search cron. This change adds site URL and switches from detailed to summary report.
17:26:36 GMT+0000
intermediate_image_sizes_advanced filter by adding the attachment_id third parameter21:52:56 GMT+0000
Adds automated cron task that will run once a week and will validate all the post contents by comparing data in database against the documents in elasticsearch. It will automatically fix any issues it finds.