Previously, Managed WordPress Hosting customers could create a staging environment by cloning a live site, but the recently released Selective Push initially supported deployments only from staging to a live site and between staging environments. Being able to push code, media, and database tables from a live site to what might be a development environment offers new flexibility for website builders.

When content is generated directly on a live site — by your publishing team or website visitors — a staged site used for development can quickly slip out of sync. Being able to move media library uploads and selected database tables back to staging is a good example of using Selective Push to equip a development environment with the latest content.

How to use Selective Push from a live environment

Pushing assets from your live website begins by making that environment active in MyKinsta (if it’s not already):

1. Select Info in the main menu to display the Site Information page.
2. Click the current environment name in the top menu bar.
3. Select the Live environment in the Jump to or search… dialog.

With your live site selected, the Push Environment button appears near the top of the page. Click the button to select a target staging environment:

Now, you can select which files, folders, and database tables you want to push from the live site. Below, our target staging environment is named “Development”:

Remember: We make an automatic backup of the target environment before beginning the push actions.

WordPress development made easier

We’re dedicated to delivering tools that make WordPress maintenance simpler. So, if you’re looking for fast and secure WordPress hosting, check out Kinsta’s plans to find the one that fits you best.

The post Selective Push now supports deployments from live to staging appeared first on Kinsta®.

That has changed.

An update to navigation in MyKinsta puts all things related to caching under a single main menu entry labeled (you guessed it) Caching. Under that are grouped the tools to manage:

• Edge Caching
• Kinsta CDN (the content distribution network)
• Server caching
• Redis cache

You can reach that menu by navigating to one of your WordPress sites in MyKinsta and then selecting Caching in the left-hand menu:

Previously, you would have to dig through different menu items for Edge Caching and CDN, while server caching and the Redis add-on were managed through entries in the Tools section. Now, it takes less time to reach the tools you need to make your WordPress site faster.

Take control of cache with Kinsta

Kinsta customers can enable and disable Edge Caching and CDN within the MyKinsta dashboard and clear those caches — as well as the server cache and Redis cache — using the same interface. However, Kinsta offers even more options for managing important tools to speed up WordPress.

The Kinsta MU (Must Use) plugin offers cache management within the WordPress admin dashboard. That means members of a publishing team who might not have access to MyKinsta can clear server-side caches, CDN, and edge caches within WordPress.

In addition, the Kinsta API is available for those who want to create their own tools for site maintenance, including clearing caches.

If you’re not already a Kinsta customer and want to take advantage of these powerful tools for your WordPress site, find a hosting plan that’s right for you.

The post Find all your WordPress caching tools together in MyKinsta appeared first on Kinsta®.

The CDN can be enabled and disabled for individual sites within the MyKinsta dashboard. This Bulk Actions functionality adds to a list of multi-site updaters that already includes:

• Clearing site caches
• Updating plugins
• Updating themes
• Change Edge Caching
• Changing PHP versions
• Exporting site information to CSV
• Changing MyKinsta’s site labels

How to bulk-update CDN status in MyKinsta

To change Kinsta CDN status for multiple website environments:

1. Select WordPress Sites in MyKinsta’s main menu and use the checkboxes on the left-hand side of the sites list to choose the environments you want to update.
2. When one or more environments have been selected, an Actions button and a count of the selected environments appear above the sites list:

3. Select Change CDN from the Actions menu. A prompt asks whether you want to Enable or Disable CDN on the selected environments:

4. Click the Change CDN button to launch the Bulk Action.

The Kinsta CDN is available only for live sites and environments with the Premium Staging Environment add-on. The Change CDN Bulk Action does not affect a free, basic staging environment. For example, in the screenshot below, MyKinsta is reporting a failed attempt to change the CDN status for a basic staging environment:

Create your own bulk actions using the Kinsta API

Did you know you can use the Kinsta API to create your own bulk-action tools for WordPress sites? The API provides a gateway to managing WordPress sites, Web Applications, Managed Databases, and Static Sites hosted by Kinsta.

Currently, you can’t enable or disable the CDN via the API, but you can use it to clear the CDN cache, just as you can with Bulk Actions in MyKinsta.

We’ve got some tips on optimizing your WordPress site environment using the Kinsta API.

At Kinsta, we’re dedicated to engineering new ways to simplify WordPress maintenance. If you’re looking for a blazingly fast and secure hosting provider, check out Kinsta’s plans to find the one that best suits you.

The post Change CDN status added to MyKinsta’s Bulk Actions appeared first on Kinsta®.