Download the PHP package isotopsweden/wp-syncs without Composer

On this page you can find all versions of the php package isotopsweden/wp-syncs. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of isotopsweden/wp-syncs

Informations about the package wp-syncs

Syncs Build Status codecov

Requires PHP 7.0 and WordPress 4.6

Syncs synchronizes attachments, posts and terms between multisites

Installation

Usage

Example configuration for post types:

Example configuration for taxonomies:

How the sync works

Created data

When a new post, term or attachment is created on a multisite it will be created on the other multisites and all obeject ids will be linked with a global sync id that is stored in the syncs table like this:

id sync_id object_id object_type site_id
1 1 15  post  1
2 1 32  post  2
3 1 90  post  3

All sync ids are stored as metadata on objects just because of WP_Query, when you read sync_id with get_metadata it actual reads from the syncs table.

Updated data

When a post, term or attachment is updated on a multisite the master it's the multisite where the user is updating. The other objects on other multisites will be removed and created again with the same global sync id but with new object ids. That's why you can't use object id as a id, instead you have to use sync_id value. It can be access via get_metadata or syncs()->get_sync_id( $object_id, $object_type, [$site_id = 0] )

Deleted data

When a post, term or attachment is deleted it will be deleted on all multisites and the sync_id will be deleted.

WP CLI

You can run wp syncs sync to synchronizes all posts from one site to all other sites.

License

MIT © Isotop

All versions of wp-syncs with dependencies

PHP Build Version
Package Version
Requires php Version ^7
composer/installers Version ~1.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package isotopsweden/wp-syncs contains the following files

Loading the files please wait ....