10:59:36 GMT+0000
Results were not accurate because get-indexes was not taking into account index state or version.
Ready to get started with WordPress VIP? Contact Us
The release window for VIP MU plugins is currently Tuesdays between 08:00 and 22:00 UTC (09:00 and 23:00 UTC when Daylight Saving Time is in effect in North America). VIP MU plugins is open source and development can be followed in the VIP MU plugins GitHub repository.
10:59:36 GMT+0000
Results were not accurate because get-indexes was not taking into account index state or version.
19:55:32 GMT+0000
You can now launch multisite subsites in the VIP Dashboard! Please refer to the documentation for an overview on how to use our new tooling.
We have also added some validation for PEM formats when uploading your CRT, CSR, and key for TLS certificates.
16:19:07 GMT+0000
We’ve Jetpack 10.2 the new default version.
15:01:51 GMT+0000
The Usage page view in the Dashboard got some new features! Customers will now better visualize their usage across the organization by filtering the information by Date and/or Application.
Check the public documentation available at: https://docs.wpvip.com/technical-references/vip-dashboard/usage/.
11:51:36 GMT+0000
This PR enables the "Open in Parse.ly" links on wp-admin for sites that are using Parse.ly.
11:51:32 GMT+0000
sonarlint.11:51:28 GMT+0000
Fix code standards compliance issues
11:51:25 GMT+0000
Added release version of Jetpack 10.2
11:51:21 GMT+0000
11:51:18 GMT+0000
sonarlint.11:51:14 GMT+0000
sonarlint.11:51:11 GMT+0000
11:51:07 GMT+0000
11:51:04 GMT+0000
phpversion() call with the PHP_VERSION constant.11:51:01 GMT+0000
Fix phpcs errors and warnings for VIP Init
09:02:11 GMT+0000
We are implementing a safer way of loading the Parse.ly plugin.
09:02:09 GMT+0000
Improving the way the wp-parsely plugin is loaded through mu-plugins.
09:02:06 GMT+0000
Add the remaining missing indexables – Term and Comment – to the ES health validation CLI command.
09:02:04 GMT+0000
We updated site details endpoint.
09:02:01 GMT+0000
Some minor checks on the Parse.ly initialization were not being called.