Image files being renamed during publish

[PMG TennCare 16]

When I publish, Madcap is renaming some of my image files by adding the size of the file at the end of the file’s name. And so my hosting website is, in some cases, looking in the applicable folder for file names that do not exist. In the example below, the file is “AC … .png.” After the publish, it is renamed “AC … _480x230.png.”

The simplest solution I can think of is to edit the code line by line; the other option is to go into the drive where the files are physically located and rename these files to conform to what the website is looking for.

If you can offer some insight into why Madcap is renaming my files during publishing, and how to stop it, please share.

Here is a snapshot of what the code looks like after the publish:

<img src="../Re…/Im…/Re…/AC…_480x230.png" style="visibility: visible;mso-wrap-style: square;width: 480;height: 230;" />


Jake

[wclass]

In your target check the Advanced tab for the "Generate resized copies of scaled images" checkbox.
If this is set, and you have resized images, you'll get extras as you have observed.
You can clear this but you should also check your images as you may not need to resize them.

[PMG TennCare 16]

In your target check the Advanced tab for the "Generate resized copies of scaled images" checkbox.
If this is set, and you have resized images, you'll get extras as you have observed.
You can clear this but you should also check your images as you may not need to resize them.

We unchecked this and did a "practice publish" web output and still had the same issue. Essentially when we publish to our host website it's not publishing the images and we're seeing the image box below instead of the actual image. In order for the images to display we had to delete the image size added to the end of the code in every topic of the output.

We're just looking for help to fix this from occurring. We've had the Advanced tab's "Generate resized copies of scaled images" checkbox checked during previous outputs and had no issues before this.