We wanted to make our caching statistics compatible with multiple caching plugins but it required changing the plugin`s code and in the end, the statistics were still inaccurate. Any heavily visited website or high CPU usage website should use the Litespeed cache plugin because the caching statistics are useful for optimizing the HTTP requests (e.g. blocking some crawlers) or reducing the CPU usage (e.g. finding not-cacheable requests by some plugins).

These logs can be very useful, especially when you made some changes (installing, updating or deleting a plugin or theme)  and the website becomes slow or simply does not work.

Regions using N2 CPU instances:

• asia-southeast1
• australia-southeast1
• us-central1
• europe-west3
• us-east1
• asia-northeast1
• europe-west4
• europe-west2
• asia-east1
• europe-west1
• us-east4
• us-west1
• southamerica-east1
• asia-east2

Upgrading a region might require downtime of approximately 5 minutes, between 1:00 AM-5:00 AM clock, local region time.

Object-Cache will be disabled by default because some plugins might not be compatible with persistent Object-Cache.

Available only to experienced users as we need more use cases for testing.

Some user account, especially those with more active websites may have experienced lower memory usage statistics.

Our built-in search and replace functionality from now on will also replace escaped URLs (e.g escaped URLs for Slider Revolution images) and URLs used in a statically generated files (e.g Divi Builder CSS cache files).

Two new tabs in Site->Logs.

Example of a few new user agents for detecting unique visitors:

• Konqueror
• Norton Safe Browser
• Baidu Browser
• Pale Moon

This feature will eliminate all false-positive security rules for logged in WordPress admin users.

CloudSnap is chargeable service starting 15 August 2018. For pricing details, check the following link.

Closte now follows Google Cloud default SSL policy across the entire platform.

Once we add a new gTLD domain via Mailgun API, the domain is suspended and all our API functionalities are disabled, means, the other users cannot add/delete email domains. This is the main reason why currently only top-level domain TLDs and country level TLDs are supported.

Beta version and only works for domain added from our WordPress plugin or via WP Ultimo.

When a task fails because the site is not compatible with WP-CLI, now task details page has the option to view the output of the executed WP-CLI command. In many cases, you can find the issue just by reviewing the output. Here is a sample output and it`s easy to see that trx_addons plugin is the issue.

Undefined option "debug_mode" called from:
Array[4]
   file => "/home/{APP ID}/public_html/wp-content/plugins/trx_addons/includes/plugin.debug.php"
   line => 180
   function => "trx_addons_get_option"
   args => Array[1]
      0 => "debug_mode"

By default, new sites are deployed on HTTP protocol. From now on, when installing an SSL certificate on the primary domain, you have options to change the protocol to HTTPS as well search and replace the database. Because search-replace, in theory, can mess up the database, we always ensure the backup is taken before we replace the database.

World first WordPress hosting with a live debugging feature.

Improved PHP log parser with a DateTime converted to user timezone.

Cache Invalidation page now has "Restart PHP" option which will restart current PHP process, clear OPcache & Object-Cache.

WordPress XML-RPC is disabled by default due to security reasons. To enable it, go to Site -> Settings -> Security tab.

We noticed that some WordPress sites were not able to receive 304 response code when accessing the same cache-able page for the 2nd time. By default, WordPress + Litespeed cache works fine but some plugins overwrite the response headers, preventing browsers to use the E-tag header. Since we do not see any use case why a user should get a 200 response code for the same page accessing for the 2nd time, we forced all cache-able responses to return Cache-Control:no-cache, must-revalidate, max-age=0. This will improve the delivery time as well save a little bandwidth.

This values will be used only for new WordPress installations, all current sites remain with the current values. We recommend increasing opcache.memory_consumption to 160MB as we found a simple WordPress site to use around ~60MB.