Jump to content

☁️ Duplicator: Backup and move sites

Recommended Posts

3 hours ago, rjgamer said:

Duplicator does not work with PHP 8 anymore. get_magic_quotes_gpc() is removed.

Is there any Roadmap to see how the module get evolved in the next few months?

Sorry, I don't have a PHP 8 install available at the moment. You are getting an error when using the installer, correct ?

Give me seconds.

Link to comment
Share on other sites

On 11/27/2020 at 6:01 PM, flydev 👊🏻 said:


Fix pushed, you can update the module from Github, master branch or wait that the modules directory update itself to update it from ProcessWire Upgrades (I can't login to do it manually).

Please let me know 👍🏼


Thank you! Could not test it yet. But wow, what a fast response. 👍

Link to comment
Share on other sites

  • 2 months later...

Is it possible to have the backup only run on certain hosts? I don't want it to backup my localhost to S3, just the production site.
Also - it would be ace if it would only backup on page saves. As 99% of the time my sites are static so a FE render doesn't matter. Hooking into page saves would be great. Though we'd ideally want to limit it as well =/

(Maybe debug mode is a good proxy for this, a tickbox for debugging in debug mode.)

Link to comment
Share on other sites

My hoster only allows Cronjobs via http/https request, but the folder /modules/Duplicator/cron.php is protected (403 error), is there a way to solve this issue without rewriting the .htaccess?

Link to comment
Share on other sites

  • 2 weeks later...

Thanks for this module.

I am on pw latest stable and the making of the package works fine

Then when I upload to new site and run the installer, all seems to work, files are created, database is created, and the homepage shows up, yet when I click on any link I get a 404, somehow things do not work

Any ideas?

Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...

Since the last update of the Upgrades module, there are two packages of duplicator:


One can be upgraded, the other not. And when I install duplicator, only the module "Duplicator" got installed. I've had to install "ProcessDuplicator" manually. Thanks to this info here.

It's look like something smaller is messed up since the last few PW updates. Or not?

Link to comment
Share on other sites

  • 3 months later...

Hi all,

I took over an old system with

- debian 9.13 (stretch)

- php 5

- pw 3.0.123

And I tryed to use the installed duplicator. It did not work like I would expect it (on my personal machines it workes). So I installed php7 and the latest version (1.4) of duplicator. After that I get this messages (below) in the front end of the package manager page but in the info box (duplicator config page) I get Package(s) found ›  1  Package Manager. So the built file is there on the server but not displayed in the front end. And the file is just containing paths (shown below)


package build failed.
2021-07-29 15:42:55:  - an error occured during package build.
2021-07-29 15:42:55:  - an error occured while building the ProcessWire structure.

And in the backup directory there is a file 2021-07-29 ...zip.log with many paths in it, like


0.0s: DIR: /var/www/mywebsite

0.0s: ZIP /.htaccess-...

0.0s: ZIP /wire/config.php


Does anyone have a clue?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Attention, please note!
      Nested repeaters cannot be supported technically. Therefore a check is made to prevent this. However, a nested repeater can only be detected if the field name ends for example with "_repeater1234". For example, if your MatrixRepeater field is named like this: "content_repeater" or "content_repeater123", this field is identified as nested and the module does not load. In version 2.0.1 the identification has been changed so that a field ending with the name repeater is only detected as nested if at least a two-digit number sequence follows. But to avoid this problem completely, make sure that your repeater matrix field does NOT end with the name "repeater".
      Bug fix: Thanks to @ngrmm I could discover a bug which causes that the module cannot be loaded if the MatrixRepeater field ends with the name "repeater". The code was adjusted and information about the problem was provided 2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.1)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By jaro
      This module (github) does with site/assets/files what Ryan's DatabaseBackups module does with the database:
      Backup site/assets Download ZIP archive Upload ZIP archive Restore site/assets Motivation: This module can be the missing part for projects with content backup responsibility on the client's side: The client will be able to download DB and assets/files snapshots through the backend without filesystem access, thus backing up all content themselves.
      Release state alpha – do not use in production environments.
      Credits for the nice UI go to @ryan – I reused most of it and some other code from the DatabaseBackups module.
    • By NorbertH
      Is there a hook to do something right after cloning a page ?
      I want the page to be saved right after cloning it either from the button in the tree or from a lister, because saving the page triggers several calculations that are not triggered by just cloning the page.
      Thanks in advance !
    • By John W.
      Question 1
      I recently installed PW 3.0.62 for a new site and also have sites running older version of PW 3.x.
      Can I export the database on an older version of PW 3.x and import it to PW 3.0.62 without any issues?
      Question 2
      (This is kind of alternative to the above for long term use - and maybe a better solution...)
      On  the sites I've previously built I have templates (home, basic-page, contact) and fields that I commonly use, such as business_name, phone_1.  The last site I built is running PW 3.0.42.  I was considering cloning this into a local site and running the upgrade module to bring it up to PW 3.0.62. From there on out when I start I new project I could just run the PW upgrade module, copy the folder to the location for the new project and duplicate the database using the new projects name.

      So basically, I'll always keep a "blank slate" site that I can just run the PW upgrade on, then duplicate into a new project. This would cut down on the work and time spent having to re-create these common fields, that I use. From there, I would just add fields, templates, etc, specific for the new website project.

      Is this a sound approach to speed up development?

  • Create New...