PHPackages                             timkelty/craftcms-site-sync - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. timkelty/craftcms-site-sync

ActiveCraft-plugin

timkelty/craftcms-site-sync
===========================

Sync content to other sites on element save.

1.2.0(6y ago)393.2k8[4 issues](https://github.com/timkelty/craftcms-site-sync/issues)MITPHPPHP >=7.1.0CI failing

Since Nov 9Pushed 6y ago2 watchersCompare

[ Source](https://github.com/timkelty/craftcms-site-sync)[ Packagist](https://packagist.org/packages/timkelty/craftcms-site-sync)[ RSS](/packages/timkelty-craftcms-site-sync/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependencies (1)Versions (12)Used By (0)

Site-Sync
=========

[](#site-sync)

Synchronize content between sites in a multi-site [Craft CMS](https://craftcms.com/) installation.

Motivation
----------

[](#motivation)

In a [multi-site](https://docs.craftcms.com/v3/sites.html) configuration, translatable field content is propagated to other sites *only on initial save*. If you want to edit translatable content and propagate those changes to your other sites, you have to recreate the changes on each site. 🤢

**Site-Sync** allows you to propagate and sychronize changes on a per-field basis, whenever you save an element. In addition to any field content (including Matrix, et al.), it can also sync `title` and `slug` content, as those are *always* translatable in Craft.

Unlike the [Craft 2 version](https://github.com/timkelty/craftcms-site-sync/tree/craft-2) and [other similar plugins](https://github.com/Goldinteractive/craft3-sitecopy), this plugin is implemented as a field for a few key reasons:

- It works when saving an element in the HUD.
- Multiple fields can be created with different default settings.

Installation
------------

[](#installation)

```
$ composer require timkelty/craftcms-site-sync
```

Usage
-----

[](#usage)

Each field layout where you would like to perform syncing must contain a **Site-Sync Settings** field.

[![Site-Sync Settings Field](https://raw.githubusercontent.com/timkelty/craftcms-site-sync/master/resources/screenshot-field.png)](https://raw.githubusercontent.com/timkelty/craftcms-site-sync/master/resources/screenshot-field.png)

In the field settings you can configure the default state of the field. Note, that unlike most fields, changes to this field do not persist between element saves. They will always revert to the state configured in the field settings.

[![Site-Sync Settings Field](https://raw.githubusercontent.com/timkelty/craftcms-site-sync/master/resources/screenshot-field-settings.png)](https://raw.githubusercontent.com/timkelty/craftcms-site-sync/master/resources/screenshot-field-settings.png)

When you save an entry with a **Site-Sync Settings** field:

- If the **Enabled** toggle is on when you save an element, content that matched before saving will be propagated to the other sites.
- Only content from the selected **Sources** will be synchronized.
- Content will only be propagated to sites where the user has permission to save elements.

### Nesting (Matrix, Neo, SuperTable, et al.)

[](#nesting-matrix-neo-supertable-et-al)

If you want to sync nested content, the child fields with the actual content should be translatable, not the parent field (Matrix, etc.) Do not check "Manage blocks on a per-site basis". This setting treats each `MatrixBlock` as a unique element, and therefore will not sync.

Should you still wish to make Matrix field your translatable, there is explicit support for Matrix and SuperTable when using the "Overwrite" option. If these fields are translatable, they will sync to other sites \_only when "overwrite" is enabled.

When *any* element (e.g. `MatrixBlock`, `Entry`) is saved, the plugin will traverse up its hierachy (via [`ElementInterface::getParent`](https://docs.craftcms.com/api/v3/craft-base-elementinterface.html#method-getparent)) until it finds a **Site-Sync Settings** field.

For example, this means you can have a single **Site-Sync Settings** field on your `Entry` layout, but a nested `MatrixBlock` will still find it and use those settings for syncing.

This also means (if you want to get crazy), that you could include a **Site-Sync Settings** field on a `MatrixBlock` to limit the scope of the syncing to that block only. Or, you could include one on the `Entry` layout and override it with another on a **MatrixBlock** layout. While this approach is supported, it can get exponentially confusing for the user and likely isn't practical for most uses.

Roadmap
-------

[](#roadmap)

- Support Overwrite + Neo
- Leverage deltas for better comparisons
- Plugin store
- Validate field layouts to only allow 1 of this field type
- Value/label usability improvements (`toggleLabelId`)
- Fix compatibility with CP Field Links
- Change "Title" name if there is a custom.
- Implement getElementValidationRules to add errors to the element
- Ensure elements are only saved when they have pending changes (performance)

###  Health Score

34

—

LowBetter than 77% of packages

Maintenance18

Infrequent updates — may be unmaintained

Popularity29

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity65

Established project with proven stability

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~68 days

Recently: every ~111 days

Total

9

Last Release

2206d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/f17a828989c32b4dc355214677bca83beeb894450f4ddb3c2b7fa4897712457c?d=identicon)[timkelty](/maintainers/timkelty)

---

Tags

cmsCraftcraftcmscraft-pluginsyncsitesite-sync

### Embed Badge

![Health badge](/badges/timkelty-craftcms-site-sync/health.svg)

```
[![Health](https://phpackages.com/badges/timkelty-craftcms-site-sync/health.svg)](https://phpackages.com/packages/timkelty-craftcms-site-sync)
```

###  Alternatives

[nystudio107/craft-seomatic

SEOmatic facilitates modern SEO best practices & implementation for Craft CMS 5. It is a turnkey SEO system that is comprehensive, powerful, and flexible.

1741.4M46](/packages/nystudio107-craft-seomatic)[verbb/image-resizer

Resize assets when they are uploaded.

127269.1k7](/packages/verbb-image-resizer)[verbb/tablemaker

Create customizable and user-defined table fields.

40168.8k1](/packages/verbb-tablemaker)[verbb/hyper

A user-friendly links field for Craft.

24130.9k9](/packages/verbb-hyper)[verbb/social-poster

Automatically post entries to social media.

918.5k](/packages/verbb-social-poster)[weareferal/remote-sync

Sync your database and assets across Craft environments

1216.0k](/packages/weareferal-remote-sync)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)