Title: VIP Platform Changelog · Page 60 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 60 of 64 23 February 2021 16:58:53 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-async-publish-actions/) This change removes the creation of async post publish cron jobs if they are not being utilized. If the relevant hooks _are_ in use, the cron jobs will continue to be created normally. [https://github.com/Automattic/vip-go-mu-plugins/pull/1999](https://github.com/Automattic/vip-go-mu-plugins/pull/1999) 23 February 2021 16:58:50 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-be-more-defensive-in-a8c_filespurge_file_cache/) It used to be possible to return an undefined variable in A8C_File::purge_file_cache. The function has been made more defensive and as such this is no longer possible. 23 February 2021 16:58:46 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-files-class-vip-filesystem-php/) We’re continuing to clean up code that isn’t 100% compliant with our coding standards. 23 February 2021 16:58:41 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-gutenberg-ramp-to-latest-upstream/) The `gutenberg-ramp` plugin is deprecated and should not be in regular use. To make this transition easier and to stay aware of all users, we have upgraded `gutenberg- ramp` to the latest upstream version. This upgrade brings alerting such that if sites continue to call the main function of the `gutenberg-ramp` plugin, we will be alerted. The idea being that we want to remove all usage of the plugin and need to know if the plugin is still being used and by whom. [https://github.com/Automattic/vip-go-mu-plugins/pull/1986](https://github.com/Automattic/vip-go-mu-plugins/pull/1986) 23 February 2021 16:58:37 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-search-9/) Fixed an issue where the ElasticPress debug bar panel wasn’t showing the expected data when used with debug bar without WP_DEBUG or equivalent constant set to true. [https://github.com/Automattic/vip-go-mu-plugins/pull/1995](https://github.com/Automattic/vip-go-mu-plugins/pull/1995) 23 February 2021 16:58:33 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-fix-warning-thrown-by-blogpublic-notice-php-when-vip_go_app_environment-isnt-defined/) We wrapped the usage of VIP_GO_APP_ENVIRONMENT in a defined check so it won’t throw warnings anymore. [https://github.com/Automattic/vip-go-mu-plugins/pull/1996](https://github.com/Automattic/vip-go-mu-plugins/pull/1996) 23 February 2021 16:58:29 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/show-a-notice-if-a-non-production-site-may-be-indexable-by-search-engines/) Creates an admin notice indicating the site may be indexable by search engines if` blog_public` option is `1` ![Screen Shot 2020-05-15 at 2 59 44 PM](https://user-images.githubusercontent.com/ 251183/82099668-c0bf4500-96bc-11ea-98ac-aa3a70768c31.png) Additionally, the notice does not show if: * the current user does not have `manage_options` * the notice has been dismissed (saved in options, reset if blog_public is resaved to `1`) * the home url ends in `.go-vip.co` or `.go-vip.net` https://github.com/Automattic/vip-go-mu-plugins/pull/1597 23 February 2021 16:58:24 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-search-8/) Removes minor warning from `wp vip-search health validate-contents` when some parameters are not set. The correct default values are set both before and after this change. https://github.com/Automattic/vip-go-mu-plugins/pull/1989 18 February 2021 10:10:39 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/update-elasticpress-to-latest-from-upstream/) This version of ElasticPress contains changes to how mappings are built – it breaks out the generation from the API requests to make it reusable. #mu-plugins, #search 18 February 2021 10:10:34 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/search-sanitize-query-errors-for-logging/) Adds a sanitization step to the generated EP query to prevent sensitive info from being logged. [https://github.com/Automattic/vip-go-mu-plugins/pull/1988](https://github.com/Automattic/vip-go-mu-plugins/pull/1988) 18 February 2021 10:07:49 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/search-remove-cron-job-scheduling-on-rest_api_init-action/) Changed how a VIP Search cron job is scheduled – previously it was hooked into ` rest_api_init` along with 2 other hooks, but this is unnecessary overhead as the job will be scheduled reliably via WP CLI (which runs regularly via cron). [https://github.com/Automattic/vip-go-mu-plugins/pull/1991](https://github.com/Automattic/vip-go-mu-plugins/pull/1991) 17 February 2021 23:42:55 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-user-role-backups/) This change adds an automated daily backup of the user roles option that can be used to recover roles if they are corrupted. It also adds some CLI commands to aid in managing these backups. 17 February 2021 09:37:01 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-jetpack-9-4-1/) Web have upgraded Jetpack 9.4 subtree to Jetpack 9.4.1, the latest patch release. Not a lot of changes, just [a few bugfixes and improvements](https://github.com/Automattic/jetpack-production/releases/tag/9.4.1). [https://github.com/Automattic/vip-go-mu-plugins/pull/1987](https://github.com/Automattic/vip-go-mu-plugins/pull/1987) 11 February 2021 23:59:24 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-files-purge-cache-for-attachments/) 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. [https://github.com/Automattic/vip-go-mu-plugins/pull/1980](https://github.com/Automattic/vip-go-mu-plugins/pull/1980) 11 February 2021 23:59: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-prevent-invalid-query-args-from-causing-php-errors-a-limitless-query/) 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 DESC ``` This is a stopgap while awaiting the resolution of the following core ticket: [https://core.trac.wordpress.org/ticket/17737](https://core.trac.wordpress.org/ticket/17737) [https://github.com/Automattic/vip-go-mu-plugins/pull/1981](https://github.com/Automattic/vip-go-mu-plugins/pull/1981) 11 February 2021 23:59:06 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-files-prevent-cross-site-lookup/) 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. [https://github.com/Automattic/vip-go-mu-plugins/pull/1975](https://github.com/Automattic/vip-go-mu-plugins/pull/1975) 11 February 2021 23:59:01 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-files-always-send-x-private-header/) 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. [https://github.com/Automattic/vip-go-mu-plugins/pull/1974](https://github.com/Automattic/vip-go-mu-plugins/pull/1974) 11 February 2021 23:58:56 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-files-handle-sites-paths-for-private-files/) 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. [https://github.com/Automattic/vip-go-mu-plugins/pull/1963](https://github.com/Automattic/vip-go-mu-plugins/pull/1963) 11 February 2021 23:58:35 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-search-7/) 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. [https://github.com/Automattic/vip-go-mu-plugins/pull/1976](https://github.com/Automattic/vip-go-mu-plugins/pull/1976) 11 February 2021 23:58:31 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/options-activate-notoptions-error-detection-and-mitigation-code/) Activated the already-deployed code to detect and mitigate problems with the notoptions cache. [https://github.com/Automattic/vip-go-mu-plugins/pull/1977](https://github.com/Automattic/vip-go-mu-plugins/pull/1977) --- * [Previous](https://docs.wpvip.com/changelog/page/59/?output_format=md) * [Page 1](https://docs.wpvip.com/changelog/?output_format=md) * … * [Page 57](https://docs.wpvip.com/changelog/page/57/?output_format=md) * [Page 58](https://docs.wpvip.com/changelog/page/58/?output_format=md) * [Page 59](https://docs.wpvip.com/changelog/page/59/?output_format=md) * Page 60 * [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](https://docs.wpvip.com/changelog/page/64/?output_format=md) * [Next](https://docs.wpvip.com/changelog/page/61/?output_format=md)