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.
23:59:24 GMT+0000
When the Restrict Unpublished Files module is enabled, a post update will now automatically purge the URLs for any child attachments for that post. This allows us to quickly propagate visibility changes and also cache public files for much longer, which has several performance benefits.
23:59:19 GMT+0000
Passing a query string like http://vip-go-dev.lndo.site/?name[]=test will cause the below php error:
PHP Warning: trim() expects parameter 1 to be string, array given in /app/wp/wp-includes/class-wp-query.php on line 779
Because WordPress interprets these sorts of query strings as single post or single page queries – it will end up with a main query that looks like the SQL query below – which is notably limitless:
SELECT wp_posts.*
FROM wp_posts
WHERE 1=1
AND wp_posts.post_type = 'post'
ORDER BY wp_posts.post_date DESCThis is a stopgap while awaiting the resolution of the following core ticket:
23:59:06 GMT+0000
In a multisite install, we support running mixed private and public sites. To harden our ACL endpoint and prevent accidentally leaking private files via public sites, we now restrict access to files on the same subsite.
23:59:01 GMT+0000
To harden the feature and avoid unexpected issues when the ACL endpoint may hit an error (e.g. fatal), we now will always send the X-Private header when the endpoint successfully processes the file. This way, we can differentiate between successful and unsuccessful requests and handle them appropriately upstream.
23:58:56 GMT+0000
We’ve added a fix that properly handles files with a subsite path (e.g. /wp-content/uploads/sites/4/2021/01/unpublished.jpg) with our Private Files feature. We now strip the sites/:id portion of the path before forwarding the request to WordPress.
23:58:35 GMT+0000
This change skips count validation on indexes that have no documents – these are assumed uninitialized. This results in a special line in the CLI initiated report:
$ wp vip-search health validate-counts
Validating post count
✅ no inconsistencies found when counting entity: post, type: post, index_version: 2 - (DB: 5, ES: 5, Diff: 0)
✅ no inconsistencies found when counting entity: post, type: page, index_version: 2 - (DB: 1, ES: 1, Diff: 0)
🟧 skipping, because there are no documents in ES when counting entity: post, type: post, index_version: 3
🟧 skipping, because there are no documents in ES when counting entity: post, type: page, index_version: 3
Validating user count
✅ no inconsistencies found when counting entity: user, type: N/A, index_version: 1 - (DB: 3, ES: 3, Diff: 0)
✅ no inconsistencies found when counting entity: user, type: N/A, index_version: 2 - (DB: 3, ES: 3, Diff: 0)Also, the health cron job will not report mismatches for indexes with 0 documents.
23:58:31 GMT+0000
Activated the already-deployed code to detect and mitigate problems with the notoptions cache.
19:26:53 GMT+0000
Adds a new file with code that automatically detects corruption of the notoptions cache entry, clearing the cache and alerting when it is detected. This code is not yet activated – it will be required by a follow-up PR.
16:31:35 GMT+0000
Adds another filter to reduce requests from Jetpack made to detect HTTPS / SSL support.
https://github.com/Automattic/vip-go-mu-plugins/pull/1973
07:25:47 GMT+0000
Since Jetpack works across many different hosting providers (some which may not support HTTPS / SSL), it attempts to detect support by making an HTTPS request to WordPress.com, which is then cached for 1 day. On VIP, SSL is always supported so we can skip this check by filtering the transient used to store the result.
18:03:46 GMT+0000
We have rolled out Jetpack 9.4 to all VIP Go sites (except those that are pinned to a specific version).
You can find here the list of changes in this version.
18:03:44 GMT+0000
As a part of code style cleanup, we need to rename class-health-job.php => class-healthjob.php. This is the last step removing to now unused class-health-job.php.
12:38:44 GMT+0000
As a part of code style cleanup, we need to rename class-health-job.php => class-healthjob.php. This is the second step switching all the references class-health-job.php => class-healthjob.php.
12:38:15 GMT+0000
In order to make future migration from Jetpack search easier, we implemented support for a jetpack_sync_post_meta_whitelist filter.
12:38:05 GMT+0000
We have upgraded the Jetpack 9.4 subtree to contain the final Jetpack 9.4 release. This will be set as the default for all unpinned sites on Thursday 4th.
12:27:21 GMT+0000
We added inactive index detection. This will detect all the inactive index versions if there was no change in active/non-active index versions for more than a month. This is the first step towards having an automated cleanup of these non-used index versions.
12:26:44 GMT+0000
Phpcs cleanup of class-health-job.php.
https://github.com/Automattic/vip-go-mu-plugins/pull/1960
#mu-plugins, #search, #code-standards
12:25:53 GMT+0000
As a part of code style cleanup, we need to rename class-health-job.php => class-healthjob.php. This is the first step introducing class-healthjob.php which is a full copy of class-health-job.php as a new file.
08:56:49 GMT+0000
This change makes it easier for us to detect if/when the changelog automation fails to create a draft post.
16:58:32 GMT+0000
There’s now the option to skip loading VaultPress code entirely, which can be useful if it’s not being used.
Some considerations need to be taken to disable VaultPress if it has been used before. So in case you are interested, please open a support ticket to get more information.
https://github.com/Automattic/vip-go-mu-plugins/pull/1965
#mu-plugins, #vaultpress