VIP Platform Changelog

We have updated the VIP Dashboard Page to include the current correct links to wpvip.com and docs.wpvip.com

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

We have updated the gutenberg-ramp plugin, that is now obsolete, to show an admin notice on sites where it’s still enabled. More information on this:

Removing Gutenberg Ramp

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

log2logstash runs fastcgi_finish_request during its shutdown hook function. Doing this before query monitor is finished causes query monitor to not load any panels.

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

In a multisite context, if one site has VIP Search all sites have access to VIP Search. Even if they don’t have an index. This is problematic as it logs false positives in our health checks. To prevent this from happening, we now skip site / indexable combos that don’t exist.

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

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

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

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

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

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');

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

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

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

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

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

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