Timeout on Clone and empty blog site created

  • Resolved marcusjwilson

    (@marcusjwilson)


    3 years, 4 months ago

    Hi – As with several other users here, NS Cloner used to work well for us until about 1 month ago.

    We always clone from the same, unchanged network site, which has always completed as expected in the past. But now when we try to the same network site, we see 504 timeout error after about 3 minutes (the clone used to complete in much less time). And we don’t see any NS cloner log file being produced or meaningful error in the logs.

    The clone seems to result in a new empty WordPress site with default settinga, but no Post content or Media items from the cloned site.

    This seems like something has either changed in aprecemos version of NS Cloner, or maybe in WordPress?

    Can you advise how to debug in the absence of errors in the logs.

    Thanks
    Marcus

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter marcusjwilson

    (@marcusjwilson)

    I have worked out this problem, and I’ll share the solution here in case it’s of use to others.

    In the past year, our host SiteGround moved this multisite network to their new SiteToolks hosting panel (from cPanel). As a result of these moves to SiteGround, the absolute path to files on the server always changes. And we found that some older references in the wp_options table of the sites we were cloning from still referenced the OLD paths. By replacing these with the new paths in the database, the site now clones as expected.

    Worth adding some error reporting in NS Cloner to handle these situations where the cloner can’t access the file path specified in the database?

    Thanks
    Marcus

    Plugin Author Never Settle

    (@neversettle)

    Thanks Marcus,

    We will pass this information along to our team.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Timeout on Clone and empty blog site created’ is closed to new replies.