Most BlogClone problems come from an incorrect blog ID, a duplicate permalink, an unexpected redirect page, or missing source media. Work through these checks before repeating a clone.
The clone does not appear in the expected blog
Check the source and target blog IDs. The source must contain the original post; the target must be the destination. On a one-blog site the selectors can be hidden, so confirm the IDs in the stack settings.
The wrong post data was copied
Make sure the source post is open in the Blog Editor and that its source blog ID is correct. Also check whether the same permalink exists in another blog. Use a current BlogClone version, which requires explicit source and target IDs to prevent cross-blog ambiguity.
The permalink is rejected or opens the wrong post
Enter a permalink that is not already used by another post. Keep the clone unpublished until its public URL opens the new record.
The image or gallery is missing
Confirm that Copy Main Image or Copy Gallery was enabled.
Check that the source post contains that media.
Verify the source blog ID.
Update BlogClone if an older version is installed.
The redirect opens the wrong place
Review the redirect-page setting in BlogClone. It should point to the page that contains the correct Blog Editor for the cloned post.
Protect your content
Back up the complete cms-data folder before using BlogClone and do not remove that backup until the clone has been checked. Do not repeatedly clone while the result is uncertain; repeated attempts can create additional records that are harder to distinguish.
If the issue remains, email support@stackswork.com. Include the BlogClone version, source and target blog IDs, the source permalink, the new permalink, whether media copying was enabled, and a short description of the result. Do not send private credentials.
Related: Getting started with BlogClone and Copying the main image and gallery.