Title: VIP Platform Changelog · Page 64 of 64 · WordPress VIP Documentation

---

#  VIP Platform Changelog

The VIP Platform Changelog includes updates made to the functionality and behavior
of the platform's tooling (i.e. [VIP Dashboard](https://docs.wpvip.com/vip-dashboard/),
[VIP-CLI](https://docs.wpvip.com/vip-cli/)), [VIP MU plugins](https://docs.wpvip.com/vip-go-mu-plugins/),
[VIP File System](https://docs.wpvip.com/vip-file-system/), [caching layers](https://docs.wpvip.com/caching/),
and other underlying architecture and software.

 [ RSS  ](https://docs.wpvip.com/changelog/feed/)

 Search

Showing page 64 of 64

 12 December 2020

00:55: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/excluded-failing-wordpress-5-6-core-tests-from-circleci-workflow/)

We have a couple of CircleCI jobs that run core tests with vip-go-mu-plugins attached
for each submitted change. Sometimes vip-go-mu-plugins ends up changing assertions
in a core test and those tests need to be excluded since we know they will fail 
100% of the time.

https://github.com/Automattic/vip-go-mu-plugins/pull/1909

 12 December 2020

00:54: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-changelog-draft-reminder-to-vip-go-mu-plugins-pr-template/)

We need to keep the changelog up to date so that everyone can be informed of changes
to our platform. We’re adding processes in to make that a reality and having a reminder
in the PR template is a part of facilitating those processes.

https://github.com/Automattic/vip-go-mu-plugins/pull/1907

 11 December 2020

05:15: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/code-standards-improvement-vip-go-mu-plugins-tests-search-test-class-search-php/)

We’re continuing to clean up code that isn’t 100% compliant with our coding standards.

This change also adds the `phpcs:errors` NPM script to our package.json. This brings
yet another tool for cleaning up existing non-standard code and ensuring all added
code is compliant with our standards.

This script is useable by running:

    ```wp-block-syntaxhighlighter-code
    ~$ npm run phpcs:errors
    ```

The most up to date details on this script are available in our [package.json file](https://github.com/Automattic/vip-go-mu-plugins/blob/master/package.json).

https://github.com/Automattic/vip-go-mu-plugins/pull/1904

#code-standards, #mu-plugins

 11 December 2020

05:04: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/jetpack-9-2-1/)

We upgraded Jetpack 9.2 to Jetpack 9.2.1.

Not a lot of significant changes in this patch release, just bugfixes and compatibility
improvements.

**Improved compatibility**

 * Site Health Tools: improve PHP 8 compatibility.
 * Twenty Twenty One: add support for Jetpack’s Content Options.

**Bug fixes**

 * Instant Search: fix layout issues with filtering checkboxes with some themes.
 * WordPress.com Toolbar: avoid Fatal errors when the feature is not active.
 * WordPress.com Toolbar: avoid 404 errors when loading the toolbar.

https://github.com/Automattic/vip-go-mu-plugins/pull/1905

#jetpack

 30 September 2020

14:03:28 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/new-filters-adjust-brute-force-thresholds/)

We’ve added two new filters to our login limiting functionality, which gives you
the ability to tweak the thresholds for our application-level brute force protections.
For example, you may want to lower them during situations with high security sensitivity.

 * `wpcom_vip_ip_username_login_threshold` : how many failed attempts to allow for
   an IP address and username combination
 * `wpcom_vip_ip_login_threshold` : how many failed attempts to allow for an IP 
   address

For example, if you wanted to only allow one attempt for a group of usernames per
IP:

    ```wp-block-syntaxhighlighter-code
    add_filter( 'wpcom_vip_ip_username_login_threshold', function( $threshold, $ip, $username ) {
    	if ( 'adminuser' === $username || 'otheradminuser' === $username ) {
    		$threshold = 1;
    	}

    	return $threshold;
    }, 10, 3 );
    ```

https://github.com/Automattic/vip-go-mu-plugins/pull/1782

 25 September 2020

13:43: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/bug-fix-dont-override-vary-headers/)

When using the [Cache Personalization API library](https://wpvip.com/documentation/vip-go/cache-personalization/),
any `Vary` headers sent before the library was initialized would be overridden. 
This is no longer the case and all supported `Vary` headers are now properly supported.

https://github.com/Automattic/vip-go-mu-plugins/pull/1740

 25 September 2020

00:15:00 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/query-monitor-3-6-4/)

We’ve upgraded [the Query Monitor plugin](https://querymonitor.com/) to 3.6.4 (previously
3.1.1).

As we’re jumping up a few releases, there are quite a few changes. A few notable
ones:

 * Dark mode
 * Stack trace support for fatal errors
 * [wp_die() support](https://querymonitor.com/blog/2019/02/new-features-in-query-monitor-3-3/)
 * [Related Hooks](https://querymonitor.com/blog/2019/02/new-features-in-query-monitor-3-3/)
   for various panels
 * Block debugging support for sites using the Block Editor

Not using Query Monitor yet? Learn how to [enable Query Monitor on your environments](https://wpvip.com/documentation/vip-go/vip-go-faq/#how-can-i-enable-query-monitor-on-my-site).

https://github.com/Automattic/vip-go-mu-plugins/pull/1775

 17 September 2020

14:30:00 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/two-factor-0-7/)

We updated [the Two Factor plugin](https://wpvip.com/documentation/vip-go/two-factor-authentication-on-vip-go/)
to 0.7 (previously 0.6). This version includes numerous bug fixes including better
compatibility with password managers like 1Password and fixing an annoying notice
about incorrectly registered scripts. Learn more about the changes in the [Release Notes](https://github.com/WordPress/two-factor/releases/tag/0.7.0).

https://github.com/Automattic/vip-go-mu-plugins/pull/1737

 16 September 2020

10:00:00 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-pass-local-date-to-wpcom_vip_top_posts_array/)

We now set the default `$end_date` param using the site’s local date (rather than
UTC time). Previously, the function could return incorrect data due to the mismatch
in timezones.

https://github.com/Automattic/vip-go-mu-plugins/pull/1756

 28 August 2020

16:37:32 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/private-mode-by-default/)

Starting today, any applications created with new GitHub repos will have [Content Distribution](https://wpvip.com/documentation/vip-go/restricting-access-to-a-site-hosted-on-vip-go/#controlling-content-distribution-via-jetpack)
disabled by default in their non-production environments.

The change was introduced in our VIP Skeleton repo here:

https://github.com/Automattic/vip-go-skeleton/pull/55

If you would like to tweak this behavior, you can remove or adjust the lines in 
the `vip-config.php` file in your repo.

Note: This will not impact existing applications or new applications/environments
created that use existing GitHub repos.

Learn more about [Content Distribution](https://wpvip.com/documentation/vip-go/restricting-access-to-a-site-hosted-on-vip-go/#controlling-content-distribution-via-jetpack).

#skeleton #jetpack

 28 August 2020

15:43:09 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/mu-plugins-reset-stats-cache-on-upload/)

We’ve pushed a fix to properly clear an internal stats cache for uploaded files.
This was causing an incorrect `filesize` value to be returned after an upload (if
done within the same request).

    ```wp-block-syntaxhighlighter-code
    wp> $file = wp_upload_bits( 'hello.txt', 'world' )['file'];
    int(5)
    wp> filesize( $file );
    int(5) <= this would previously return 0
    ```

The fix was pushed in our mu-plugins repo here:

https://github.com/Automattic/vip-go-mu-plugins/pull/1741

#mu-plugins

---

 *  [Previous](https://docs.wpvip.com/changelog/page/63/?output_format=md)
 *  [Page 1](https://docs.wpvip.com/changelog/?output_format=md)
 *  …
 *  [Page 61](https://docs.wpvip.com/changelog/page/61/?output_format=md)
 *  [Page 62](https://docs.wpvip.com/changelog/page/62/?output_format=md)
 *  [Page 63](https://docs.wpvip.com/changelog/page/63/?output_format=md)
 *  Page 64