• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Duplicate a site?

Originally posted by Jllynch
Can we duplicate a site and all of its content in Sitebuilder? So that we can setup a site exactly the same that can then be edited in the sitebuilder?

Theoretically, it is possible. The site stores information in /usr/local/sitebuilder/htdocs/sites/xx/xxxxxxxxxxxxxxxxxxx

directory and in database. So first of all content should be copied and all appropriate records in database.

If you have static site without any modules, copy of the site can be done using site content only. But if you have modules added to the site, it won't be easy to create a duplicate site, because each module has some related records in database which should be also copied with site content.
 
So at the end I want to say that there is no exactly procedure which could help you do this, but you can try and make some experiments, for example with static sites.
 
Let's imagine the following situation: web site with modules was created and published. You created copy of this web site. Newly created web site will not have publishing settings set, because publishing to the same location does not make sence.
Site stores their data at published site, we have 2 options:
1. during site copying Sitebuilder should make copy data from published site via FTP/XCOPY/VPS
2. create dumb data (empty database)

We'd prefer to go with 2-nd option. What is your expectations?
 
Back
Top