VIP Platform Changelog

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

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:

mutation replaceIPAllowListMutation($input: AppEnvironmentIPAllowListInput) {
	replaceIPAllowList(input: $input) {
		app {
			id
		}
		ips
	}
}

With variables:

{
	"input": {
		"id": 999999,
		"environmentId": 999999,
		"ips": []
	}
}

#cloud-api #ip-allow-list

We’ve updated our skeleton repo to use Twenty Twenty One v1.1 which includes various bug fixes. 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://github.com/Automattic/vip-go-skeleton/pull/62

#skeleton

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

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

There was an extraneous comma added in 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

Updated Test jQuery Updates 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/Automattic/vip-go-mu-plugins/pull/1901

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

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

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

Starting today, users that have manage_options capability will be able to flush the page cache for any page and its related style and script assets. Look for “Flush Cache for Page” button in the admin bar.

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

Learn more in our Lobby post.

#mu-plugins

Core WordPress tests are already validated as running successfully as part of the WordPress release process. Running them without including vip-go-mu-plugins on every change to vip-go-mu-plugins isn’t necessary.

We will continue to run the WordPress core test jobs in CircleCI that include vip-go-mu-plugins on every change to ensure changes work as expected with WordPress core.

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

add_role can lead to database writes which, when called on init, can trigger on the frontend. That is not ideal as it can cause performance problems. It can also lead to undesirable circumstances with other roles being removed if there are intermittent database issues.

We still trigger our upgrade routine on admin_init so new installs still get the VIP Support roles added correctly.

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

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

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

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:

~$ 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/pull/1904

#code-standards, #mu-plugins

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

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:

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

When using the Cache Personalization API library, 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

We’ve upgraded the Query Monitor plugin 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
• Related Hooks 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://github.com/Automattic/vip-go-mu-plugins/pull/1775