BlogClone duplicates an existing Total CMS 1 blog post from the Blog Editor. It is useful when a new post should begin with the structure or wording of an existing one.

Before you begin

  • BlogClone is designed for Total CMS 1.

  • Install the current BlogClone stack file in Stacks App.

  • Make a complete backup of your cms-data folder before cloning content.

A backup matters because BlogClone creates and copies live CMS records. Keep that backup until you have checked the new post and its media.

Add BlogClone to the editor

  1. Add BlogClone to the page that contains the Total CMS Blog Editor.

  2. Configure the source and target blog IDs used by your editor.

  3. Choose the page that should open after a successful clone.

  4. Publish the editor page, then open the post you want to use as the source.

BlogClone adds the cloning workflow to the editor. The clone dialog lets you review the new permalink, choose the target blog, and decide whether the main image and gallery should be copied.

Create the first copy

  1. Open an existing post in the Blog Editor.

  2. Start the BlogClone action.

  3. Enter a unique permalink for the new post.

  4. Confirm the target blog ID.

  5. Choose whether to copy the main image and gallery.

  6. Select Clone.

After the copy is created, BlogClone redirects to the configured editor page. Review the title, permalink, content, dates, images, gallery, and publication state before publishing the new post.

Next: Cloning a post and choosing the target blog.