sdkns

Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Forum: Plugins
    In reply to: [NS Cloner - Site Copier] Image Issue after Cloning
    Plugin Author sdkns

    (@sdkns)

    8 months ago

    Hi @amplispot,

    It sounds like you’re seeing a classic “URL + cache” mismatch after cloning Oxygen sites. Backgrounds in Oxygen are often stored inside builder data (JSON/shortcodes) and CSS caches—not just as normal image attachments. If the old domain (dev) still lurks anywhere in that data, or the Oxygen CSS cache wasn’t rebuilt, backgrounds disappear in the editor.

    Here’s the solution I recommend (in order):

    1) Clone with serialized-safe URL replacement ON

    NS Cloner already does smart, serialized-safe URL swaps during a clone. Make sure that’s enabled, and if you’re “teleporting” between servers, add an explicit dev→prod replacement so the builder’s buried references get flipped. You can also re-run Cloner’s Search & Replace mode post-clone across the live site.

    2) Immediately run Oxygen’s built-in URL Replacement

    After the site is up on production, go to Oxygen → Settings → URL Replacement and replace the dev URL with the prod URL. This hits Oxygen’s design data, page options, selectors, etc., which is exactly where background image references often live.

    3) Re-sign shortcodes & rebuild Oxygen’s CSS cache

    Do the standard Oxygen migration cleanup:

    • Settings → Permalinks: save twice
    • Oxygen → Settings → Security: Re-sign shortcodes
    • Oxygen → Settings → CSS Cache: Regenerate CSS
    • Clear any page/server caches/CDN
      These steps fix stale CSS and signature mismatches that can blank backgrounds.

    4) Sweep the database for stragglers (just in case)

    Even with the above, you can still have hard-coded URLs in custom selectors or custom CSS. Run a final serialized-safe search/replace across the DB for the dev domain (NS Cloner’s Search/Replace mode is fine here). This is the most reliable way to catch leftover background URLs embedded in JSON/meta.

    5) Validate the media itself

    Make sure all uploads actually made it over (especially if you use offloaded storage/CDN). If the files exist but aren’t rendering, it’s almost always the URL/caching issues above—not missing attachments. General migration threads across builders (Oxygen/Bricks/etc.) report backgrounds as the first thing to break when URLs aren’t fully replaced.

    Quick diagnostic checks (targeted)

    • In the DB, inspect postmeta for Oxygen keys like ct_builder_json / ct_builder_shortcodes on a problem page—if you still see dev.example.com in that JSON, you’ve found the culprit. (Run the step 4 sweep.)
    • Inspect /wp-content/uploads/oxygen/css/ on prod—if those files reference the dev domain, your CSS cache wasn’t rebuilt. (Run step 3.)

    Hope this helps!

    Forum: Plugins
    In reply to: [NS Cloner - Site Copier] Automatically Cloning a Subsite
    Plugin Author sdkns

    (@sdkns)

    10 months, 2 weeks ago

    That’s correct. In Cloner Pro, the options for choosing which sites to offer new users when registering to select as templates in under the Member Templates menu item… There are very straight forward instructions on that page so it’s very easy to understand and use!

    Forum: Plugins
    In reply to: [NS Cloner - Site Copier] Automatically Cloning a Subsite
    Plugin Author sdkns

    (@sdkns)

    10 months, 2 weeks ago

    Yes, you can use Member Templates and assign which sites in your network can be used as a theme to select from for the person registering…

    Forum: Plugins
    In reply to: [NS Cloner - Site Copier] Weirdness with “empty” site url when cloning
    Plugin Author sdkns

    (@sdkns)

    1 year, 2 months ago

    This issue with WP Site Cloner appears to be related to how the siteurl and home values are being set (or not set) during the cloning process. The three-slash (https:///) issue strongly suggests that the domain replacement step is failing, leaving an empty string where the domain should be. Possible Causes:

    1. Database Serialization Issues
      • If the plugin replaces site URLs in serialized data but doesn’t handle it correctly, it could lead to missing or blank values.
    2. WP Engine’s Caching or Redirect Rules
      • WP Engine has aggressive caching, which can sometimes interfere with site cloning/migration scripts. Try purging all caches in WP Engine’s dashboard and checking for any forced siteurl overrides in wp-config.php.
    3. Missing wp_options Updates
      • Normally, wp_options should be updated with the new siteurl and home values during cloning. If this fails, URLs can break.
    4. Inconsistent Environment Settings
      • If previous clones worked fine but this one didn’t, something may have changed in WP Engine’s setup, or your WordPress configuration may have been altered.

    Troubleshooting Steps:

    1. Manually Update wp_options
      • Run this SQL query in PHPMyAdmin or through WP CLI: UPDATE wp_options SET option_value = 'https://clonedsite.example.com' WHERE option_name IN ('siteurl', 'home');
      • If this fixes the issue, it suggests the plugin isn’t properly updating these values.
    2. Check wp-config.php
      • See if WP_HOME or WP_SITEURL is being forced: define('WP_HOME', 'https://clonedsite.example.com'); define('WP_SITEURL', 'https://clonedsite.example.com');
      • If missing, adding them manually might help as a temporary fix.
    3. Run a Search & Replace on the Database
      • Use WP-CLI or a plugin like WP Migrate DB to replace empty URLs with the correct domain: wp search-replace 'https:///' 'https://clonedsite.example.com/'
    4. Test with a Different Site
      • Try cloning another site on WP Engine. If the issue persists across different sites, it might indicate a WP Engine-specific change affecting the cloning process.
    5. Check WP Engine’s Support Logs
      • WP Engine may have logs that show why the siteurl value is missing.

    Since this worked before on the same hosting, it’s possible WP Engine made a change that affects the cloning process. If none of the above fixes work, you may want to check with WP Engine support to see if they’ve adjusted how they handle site migrations/clones.

    Forum: Plugins
    In reply to: [NS Cloner - Site Copier] Can’t clone site – Subsite already exists
    Plugin Author sdkns

    (@sdkns)

    1 year, 3 months ago

    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)