Bypass cache for more WordPress-related cookies

This release broadens the scope of cookies that can bypass cache. Users using this setting should un-apply then re-apply the bypass cache on cookies for the new value to take effect. (#9, thanks @jboonstra!)

Fix an error when scanning for sites

This release fixes a PHP fatal error encountered when scanning a StackPath account for sites. (#4)

Better error reporting and logging

This release makes it easier to spot errors coming from the StackPath API. Now you can more easily tell if an error is due to an error in the plugin or with your StackPath service. (#2)

• The plugin now handles more types of error structures from StackPath, preventing potential PHP fatal errors. Big thanks to @perariontaeadastra for reporting this!
• When WP_DEBUG and WP_DEBUG_DISPLAY are both set to true in wp-config.php then errors reported from StackPath include information about the API request and response that produced the error.
• When WP_DEBUG is set to true and WP_DEBUG_LOG is set to a valid value in wp-config.php then errors reported from StackPath are recorded in WordPress' or PHP's error log. Sensitive information like authentication tokens and passwords are scrubbed from the display and file logs, but they may contain service-specific information like your StackPath API client ID, stack slug, and site IDs.
• A more standards complaint User-Agent string is now used in StackPath API requests.
• Various small grammatical issues spotted in the UI were also addressed.

Initial release

Welcome to the first preview release of the StackPath WordPress plugin!

This is a beta release. We do not recommend running this on a production site yet, there may be bugs, and there are features still in development. Please open an issue if you'd like to talk about the plugin.