Weave Code
Duplicator Laravel Package
doublethreedigital/duplicator
Duplicator is a Laravel package for duplicating Eloquent models in a single line. Clone records along with their relationships, customise which attributes and relations get copied, and keep data consistent when recreating entries, templates, or drafts without repetitive code.
Seamlessly duplicate entries & terms in the Control Panel (only for multi-site!)
Frequently asked questions about Duplicator
- What does the doublethreedigital/duplicator package actually do?
- Duplicator is a lightweight Statamic addon that adds a Duplicate action to the control panel, letting editors clone an entry, page, or custom collection item in one click. The copy is created with all field values and content intact, so you can rename it, edit the slug, and publish without retyping anything. It is aimed at repetitive workflows such as seasonal pages, product variants, or template entries. It does not own routing, schema, storage, or business logic beyond the copy itself.
- Is Duplicator a Laravel package or a Statamic addon?
- It is a Statamic addon, not a general-purpose Laravel package, despite some descriptions circulating that frame it as an Eloquent model duplicator. It sits at the Control Panel UX layer and only makes sense in a project that already runs Statamic. If your application is plain Laravel without Statamic, this package is out of scope and you should look at a dedicated model-duplication package instead.
- How do I install Duplicator in a Statamic project?
- Installation follows the standard Statamic addon pattern: composer require doublethreedigital/duplicator, then let service provider auto-discovery or manual registration handle the rest, with optional config publishing. Because the repository has been archived, do not assume installability on a current project. Run composer why-not doublethreedigital/duplicator before anything else, and never force it through with --ignore-platform-reqs.
- Does Duplicator support Statamic 4 and 5, Laravel 10 and 11, or PHP 8.2 and 8.3?
- Treat that as unverified. The addon has been archived since May 2023 and its last release predates the Statamic and PHP versions most projects now run, so it is unlikely to declare or be tested against Statamic 4 or 5 or PHP 8.2 and 8.3. The real matrix is Statamic major times Laravel major times PHP minor per environment. A composer why-not check against each target project will answer installability far faster than reading release notes.
- Is doublethreedigital/duplicator still maintained?
- No. The upstream repository was archived in May 2023, which means no security patches, no compatibility updates, and no bug fixes. Any defect you hit becomes yours to fix by forking, and the MIT license makes that lawful rather than free. You should also confirm the package is still resolvable from Packagist and has not been abandoned or name-squatted since archiving.
- Does Statamic already have a built-in duplicate action, making this addon redundant?
- Check your current Statamic version before adding anything, because native content duplication has been improving and many teams find the addon unnecessary. If native duplication covers the collections you care about, the addon is a redundant convenience with extra maintenance risk. Only adopt it if you have a specific gap that native behaviour does not fill and you are prepared to fork.
- How does Duplicator handle relations, assets, unique slugs and multi-site localization when cloning?
- Preserving field values and related data is deceptively hard, and duplication routinely misbehaves on nested fields, asset references, relations, unique slugs, entry URIs, and multi-site placement. Each of those has to be handled deliberately, and a low-adoption addon archived in 2023 has had few eyes on those edge cases. Test each case explicitly on a staging copy before letting editors use the action. A misduplicated entry creates bad content state that someone may publish.
- Does Duplicator respect Statamic's permissions when duplicating content?
- Verify this yourself rather than assuming. A duplicate action must enforce the authoring permissions of both the source and the target collection, and must not let an editor copy content across boundaries they should not cross. Review the addon code or test with a restricted role before enabling it in production. This is exactly the kind of check an unmaintained package will never do for you.
- What should I check before using Duplicator in production?
- Confirm the version triple for every environment, verify the package still resolves from Packagist, and install it on a staging copy of the real site. Then duplicate representative content with nested fields, relations, assets, unique slugs, and multi-site localization, and confirm the control panel behaves correctly rather than merely installing cleanly. Check that permissions are honoured and decide up front whether maintaining a fork is an acceptable cost. If it is not, the correct decision may be to drop the capability.
- What are the alternatives to Duplicator, and is forking it realistic?
- The realistic options are Statamic's native duplication where it exists, a small custom duplicate action you control, or forking this MIT-licensed addon and owning it. Forking is lawful but not free: you inherit compatibility drift, security responsibility, and every edge case the original never handled. For plain Eloquent model duplication outside Statamic, use a maintained Laravel model-duplication package instead of this addon.
Weaver
How can I help you explore Laravel packages today?