Potential Bug with NS Cloner 4.0.9

  • We use WebP Express to convert the images on our multisite set up to Next Gen format. The plugin has been working flawlessly with the multisite setup and with NS Cloner when we clone sites up until we updated our plugins, theme, and WordPress.

    Now when we clone a site with NS Cloner we are not able to view the images that we upload to the media library.

    This is the error we get:
    Sanity check failed for source (passed as relative path, through querystring): File does not exist or is outside restricted basedir

    We found how to fix the issue which is why we think this is a bug with the latest version of NS Cloner. The issue is the rules in the .htaccess file in the /wp-content/uploads/sites/ID folder are not being updated. When we opened up the file for the latest site we cloned (ID 73) the rewrite rules were still mentioning ID 3 which is the ID we cloned from.

    We wanted to put this out there incase other people have this issue as well as hoping that if it is an NS Cloner bug that it will be fixed in the next release.

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Never Settle

    (@neversettle)

    Hello @sebomarketing,

    I’m not sure exactly what may have been the cause for it going from working to not, but I can tell you it’s not a change in NS Cloner itself as the Cloner has never made any changes/replacements to files in wp-content/uploads/sites – it just copies whatever is there exactly as-is.

    We probably can’t realistically add automatic replacement as it’s non-standard to have an .htaccess in the uploads/sites directory, but one possibility: can you check if you delete the .htaccess file, if WebP Express will regenerate it automatically? If that’s the case, we could just add an exclusion to prevent the Cloner from copying .htaccess files (so the one mentioning the wrong ID would not be copied over) and then let WebP Express create the appropriate one.

    Thread Starter sebo.marketing

    (@sebomarketing)

    Thanks for the information. That is very interesting information. I wonder why it stopped working then? I guess I need to reach out to WebP Express to see what they have to say. I tried deleting the .htaccess file to see if it will recreate it and it didn’t. I even went to the plugin settings and had it regenerate the .htaccess rules and it still didn’t recreate it. The odd thing is the images appear to be working without the .htaccess file in place so now I wonder if this file is even doing anything. I am going to reach out to WebP and see what they say.

    Again, thanks for responding and letting us know more about how your plugin works. The NS Cloner really does make our job a lot easier.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Potential Bug with NS Cloner 4.0.9’ is closed to new replies.