Hi, I’m Bernie, a developer on the team working on the WP Super Cache (WPSC) Extension for Calypso. WP Super Cache is one of the most popular WordPress plugins and we’re asking for your help in testing it before we release it to the world! This round of testing is perfect for people that have used WPSC before, but it’s also fine if you just like to try and break things 🙂
- To do so, you need a self-hosted WordPress installation with the Jetpack plugin enabled and connected to WordPress.com. Please use a test site that isn’t of any practical relevance to you — while we don’t expect it to happen, we’d hate if you lost any data!
- Navigate to https://horizon.wordpress.com/plugins/wp-super-cache (you need to be logged in).
- Scroll down, and click the ‘Install’ button next to your JP test site.
- A link saying ‘Edit plugin settings’ should now appear right below the plugin header. Click that link.
You’ll be greeted with the following screen:
Start by switching on the ‘Enable Page Caching’ toggle.
You might notice that WPSC offers a large number of controls to fine-tune caching. How are you supposed to know if and how they work if you’ve never used WPSC before? Well, you could read the WPSC description on WordPress.org, and we certainly appreciate if you familiarize yourself with it.
But you don’t have to. Instead, we ask you to open your site’s wp-admin interface in another browser tab and compare them. (Find instructions below the image.)
- Open your site’s wp-admin backend in another browser tab, and navigate to Settings > WP Super Cache.
- Change an individual control’s value inside the Calypso extension (don’t forget to click the Save Settings button).
- Switch over to the wp-admin tab, and reload. Verify that the control that you changed inside Calypso has been carried over.
- You can also try the inverse — change a setting in the wp-admin UI, and verify that it carries over to Calypso (again, don’t forget to save and reload, respectively!)
- Be sure to also check the front-end part of your website to verify it’s not broken by any of your changes.
Please leave your feedback in the comments below. We’re mostly interested in any errors you run into at this point, but you’re also welcome to comment on any smaller glitches you notice. We’re aiming for a release of the extension on Wednesday, August 23, 2017.