Multisite

In this tutorial, I will dive into how you can disable a network activated plugin for one specific site within your WordPress Multisite Network.

In this article, I want to show you how to transfer multiple WordPress posts between sites (and you can choose manually which posts).

More than that, I want it to be almost a one-click solution, something like this:

What you can see in the screenshot above:

• You can connect target sites only once and then migrate posts there at any time.
• You can select only specific posts and pages if you need, or select all of them.
• If a post has already been transferred from “Site A” to “Site B”, then you can sync the changes made in the original version of the post at any time as well.

Seems quite convenient, doesn’t it?

Of course, there are tons of export and import plugins that are available to you; however, doing it using the export-import method is too much trouble, in my opinion. It may only do the trick during the initial migration of all posts.

In this guide, I will show you how to automatically create or update a taxonomy term (it could be a category, a tag, or a custom taxonomy) on one or multiple subsites within a WordPress multisite network when you create or update it on the main site.

More than that, we will also add a checklist with all subsites to the taxonomy edit page, so you can manually select specific subsites to which you want to sync this particular taxonomy term.

This is how it is going to look:

In this tutorial, we will talk about ways of managing media files when you’re running a bunch of WordPress websites within a single WordPress multisite network. By the way, if you’re not 100% sure what a multisite network is, then you’re probably running multiple standalone sites.

Long story short, I will show you how the media files in multisite networks are handled by WordPress, how to set up centralized media management across your network, and also how to organize media with folders.

In this tutorial, I want to dive deep into the steps you need to take if you want to clone a specific subsite of your WordPress Multisite network. The process is not very difficult, but there are some moments you will need to keep in mind.

We will also take a look at two different approaches – I will show you how to do it with the help of the plugin and also programmatically.

Let’s jump into it.

If you have ever wondered how users are handled in a WordPress Multisite network, then this tutorial will definitely be helpful for you.

We will discuss various aspects of multisite user management: registrations, user roles in multisites, and associating users with specific sites of a network.

When chatting with my customers, I keep getting the idea that people don’t always understand what a “WordPress Multisite network” is. Most of them think of it as a “multi-site” model for their store, like having completely separate stores (not necessarily on WooCommerce, by the way), each store with its own domain, database, etc.

Which is a completely wrong assumption!

Having a WordPress Multisite setup for your WooCommerce stores means:

• The stores will share the same server.
• The stores will share the same database.
• And what is most important – they share the same WordPress installation (basically, it means that if you sign in as a super administrator, you get access to every store within a single admin dashboard, or, if you sign in as a specific store administrator, you will get access only to that store and to all stores you’re added to).

Not sure whether you’re using WooCommerce Multisite? You can check it easily – if you have the following page in your WordPress admin dashboard, then it is a multisite network:

Once we get this main misunderstanding out of the way, let’s move to more practical stuff.