Title: Changelog: VIP MU plugins [Production] · Page 39 of 40 · WordPress VIP Documentation --- 1. [Changelog](https://docs.wpvip.com/changelog/) 2. VIP MU plugins [Production] # Changelog: VIP MU plugins [Production] The release window for [VIP MU plugins](https://docs.wpvip.com/vip-go-mu-plugins/) is currently Tuesdays between 08:00 and 22:00 UTC (09:00 and 23:00 UTC when Daylight Saving Time is in effect in North America). VIP MU plugins is open source and development can be followed in [the VIP MU plugins GitHub repository](https://github.com/Automattic/vip-go-mu-plugins/). [ RSS  ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/feed/) Search Showing page 39 of 40 12 January 2021 12:42:45 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/bug-fix-append-blog-id-to-vip-search-post-count-cache-keys/) There was a bug with the VIP Search validate-counts command where the cache keys for post counts are the same for identical query args when iterating all subsites when using the `--network-wide` flag. To account for this, we appended the blog ID to the cache keys. https://github.com/Automattic/vip-go-mu-plugins/pull/1932 12 January 2021 12:42:38 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/added-ability-to-set-fixed-timestamps-in-vip-search/) Adding the ability to set fixed timestamps in VIP Search is handy for creating consistent and reliable automated tests. https://github.com/Automattic/vip-go-mu-plugins/pull/1935 #mu-plugins #search 12 January 2021 10:59:27 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/updates-the-way-vip-search-versioning-information-is-stored/) The versioning information for vip-search index needed to be updated to address global indexables (e.g. User), and different versioning across sites in a multisite environment. This change stores global indexable separately – one per network. While making sure non-global versions are stored one per site. https://github.com/Automattic/vip-go-mu-plugins/pull/1921 #mu-plugins #search 12 January 2021 10:58:19 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/phpcs-error-cleanup-iputils-class/) As part of the ongoing work on cleaning up legacy we go over files not touched in a while and make sure they still comply with our code standards. This change updates the style of IpUtils library. https://github.com/Automattic/vip-go-mu-plugins/pull/1929 #mu-plugins #code-standards 05 January 2021 23:24:52 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/jetpack-9-3-beta-added/) Jetpack 9.3-beta has been released and is now available in mu-plugins. To test the new version, simply add this constant to your `vip-config.php` file: `define( 'VIP_JETPACK_PINNED_VERSION',' 9.3');` 05 January 2021 22:59:54 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/resolves-phpcompatibility-phpcs-warnings-for-php-7-4-wpcom-error-handler/) The warnings were already reviewed previously and deemed false positive in this case. However, we updated the implementation here to silence/resolve the warnings. https://github.com/Automattic/vip-go-mu-plugins/pull/1920 04 January 2021 17:18:54 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/added-proposal-requirements-to-vip-go-mu-plugins-pr-template/) As part of improving our SDLC process, we’re going to require proposals for feature additions / significant feature alterations. This will allow us to ensure that features and significant feature alterations deliver much more value to our platform by being properly planned out, executed, and released. https://github.com/Automattic/vip-go-mu-plugins/pull/1908 #mu-plugins 29 December 2020 11:18:13 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/store-site-details-in-a-temporary-location/) We keep working in the Site Details functionality, that will allow us to have up to date details about sites, such as the list of plugins and their versions, whether VIP Search is enabled, Jetpack connection status… While the final implementation is still in progress, we are now storing site details in a temporary location in logstash, so that we can start using this data as soon as possible. One example is finding all sites that are running a certain version of a plugin, to prepare for an upgrade to a newer version. https://github.com/Automattic/vip-go-mu-plugins/pull/1924 #mu-plugins #site-details 29 December 2020 11:01:10 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/add-more-information-to-site-details/) We keep working in the Site Details functionality, that will allow us to have up to date details about sites, such as the list of plugins and their versions, whether VIP Search is enabled, Jetpack connection status… This adds some more fields, namely the information about Jetpack (version, active status, Jetpack id, active modules). In the future, all these will be stored and be accessible to run actions on them. E.g, easily find all sites that have a certain old Jetpack version that needs upgrading. https://github.com/Automattic/vip-go-mu-plugins/pull/1923 #mu-plugins #site-details 29 December 2020 10:58:59 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/improved-internal-stat-tracking-for-cache-manager/) We have updated stats keys allowing us to better track usage for Cache Manager functionality. https://github.com/Automattic/vip-go-mu-plugins/pull/1922 #mu-plugins 29 December 2020 10:30:05 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/resolves-phpcompatibility-phpcs-warnings-for-php-7-4/) The warnings were already reviewed previously and deemed false positive in this case. However, we updated the implementation here to silence/resolve the warnings. https://github.com/Automattic/vip-go-mu-plugins/pull/1919 23 December 2020 20:02:12 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/bug-fix-disable-ip-allow-list/) We’ve fixed bug which caused the `replaceIPAllowListMutation` to not work correctly when passed an empty array. The fix now correctly disables the IP Allow List from the environment when given an empty array. Example query: ```wp-block-syntaxhighlighter-code mutation replaceIPAllowListMutation($input: AppEnvironmentIPAllowListInput) { replaceIPAllowList(input: $input) { app { id } ips } } ``` With variables: ```wp-block-syntaxhighlighter-code { "input": { "id": 999999, "environmentId": 999999, "ips": [] } } ``` #cloud-api #ip-allow-list 23 December 2020 03:43:08 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/vip-skeleton-twenty-twenty-one-v1-1/) We’ve updated our skeleton repo to use [Twenty Twenty One v1.1](https://make.wordpress.org/core/2020/12/22/twenty-twenty-one-and-twenty-nineteen-updates-now-available/) which includes [various bug fixes](https://core.trac.wordpress.org/query?keywords=~twenty-twenty-one-1.1&or&keywords=~twenty-nineteen-1.9&group=type&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=milestone&order=priority). All new applications will have their repos generated with this new version. Existing applications can update their version by downloading the new version from [the WordPress.org Theme Directory](https://wordpress.org/themes/twentytwentyone/). https://github.com/Automattic/vip-go-skeleton/pull/62 #skeleton 17 December 2020 22:21:38 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/log-to-logstash-when-vip-search-rate-limiting-begins/) To assist with debugging VIP Search related issues, we need an easy way to determine if rate limiting is currently in effect for queries or indexing operations. The easiest way to accomplish this right now is by logging when rate limiting starts to logstash. https://github.com/Automattic/vip-go-mu-plugins/pull/1916 17 December 2020 20:57:04 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/added-dry-run-of-vip-search-index-version-corruption-detection/) In order to provide stable and robust index versioning for our search offering, we need to be able to detect and heal any issues with the versioning data. This feature is the first step towards that goal. It detects index versioning issues and logs them without performing any actions so we can identify any potential issues before rolling this out to all VIP Search users. There will be an additional change in the future to allow this to run for real once we’ve verified everything operates as we intend. https://github.com/Automattic/vip-go-mu-plugins/pull/1881 17 December 2020 17:45:54 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/bug-fix-removed-extraneous-comma-from-button_enqueue_scripts-in-vip-cache-manager-vip-cache-manager-php/) There was an extraneous comma added in [Feature: Flush Cache for Page](https://wpvipchangelog.wordpress.com/2020/12/15/feature-flush-cache-for-page/). This didn’t affect any of our environments. The issue only presents itself in earlier PHP versions and only caused some issues when running certain tests locally with phpunit-docker.sh. This comma was removed to address this issue and won’t affect anything else. https://github.com/Automattic/vip-go-mu-plugins/pull/1915 15 December 2020 22:50:15 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/plugin-updated-test-jquery-updates-2-0-x/) Updated [Test jQuery Updates](https://github.com/WordPress/wp-jquery-update-test) to the latest upstream version to bring in support for WordPress 5.7 and various minor improvements / bugfixes. **Note** We are on 2.0.x because have modified the plugin. The current latest 2.0 release doesn’t operate as expected on read-only file systems due to capability check changes. An issue have been opened [here](https://github.com/WordPress/wp-jquery-update-test/issues/14). https://github.com/Automattic/vip-go-mu-plugins/pull/1901 15 December 2020 22:50:12 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/updated-old-domains-and-wordpress-com-references/) Updated old documentation URLs and WordPress.com VIP references in code comments and some customer-facing strings. https://github.com/Automattic/vip-go-mu-plugins/pull/1911 15 December 2020 22:50:10 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/added-support-for-the-concatenation-plugin-outside-of-vip-environments/) Allow any environment that is correctly configured to run the concatenation plugin to do so and use the same logic as VIPs environments. https://github.com/Automattic/vip-go-mu-plugins/pull/1913 15 December 2020 22:50:07 GMT+0000 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/) [ Permalink ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/bug-fix-hook-into-init-rather-than-plugins_loaded-for-vip-search-versionings-delete-handlers/) Previously VIP Search registered actions to handle deleted content during `plugins_loaded`, but this is too early as some Indexables may not have been registered yet. VIP Search sets up Features (and their Indexables) on `init`, which comes later. https://github.com/Automattic/vip-go-mu-plugins/pull/1903 --- * [Previous](https://docs.wpvip.com/changelog/vip-mu-plugins-production/page/38/?output_format=md) * [Page 1](https://docs.wpvip.com/changelog/vip-mu-plugins-production/?output_format=md) * … * [Page 36](https://docs.wpvip.com/changelog/vip-mu-plugins-production/page/36/?output_format=md) * [Page 37](https://docs.wpvip.com/changelog/vip-mu-plugins-production/page/37/?output_format=md) * [Page 38](https://docs.wpvip.com/changelog/vip-mu-plugins-production/page/38/?output_format=md) * Page 39 * [Page 40](https://docs.wpvip.com/changelog/vip-mu-plugins-production/page/40/?output_format=md) * [Next](https://docs.wpvip.com/changelog/vip-mu-plugins-production/page/40/?output_format=md)