Unfortunately there just isn't a simple way. Project Manager is always a one by one operation.
However, if you are moving all the images to a folder named "ScreenShot", you could probably accomplish it by using the RoboHelp find and replace to amend all the image references. Then sneak behind RoboHelp's back and move the files using Windows Explorer.
You would likely also need to clobber the CPD file and let RoboHelp rebuild it after you were finished.
And I cannot stress this enough, make a backup for our dear friend Mr. Case before you begin.
I am moving images from the root level of project manager to an images folder. If I follow your suggestions, will all the links still move over that are associated with the image files?
Absolutely! Remember, the links are actually in the individual topic code. When you move the images, RoboHelp is simply amending that code to reference the new image location.
Thank you very much for your quick reply. Can you tell me what you mean by amend the image references in Robohelp. The search and replace function in Robohelp does not allow adding or deleting text in searched files, or none that I can see. Maybe I'm talking about the wrong thing. Can you explain the steps a bit more in detail.
When you insert an image into a topic, what you are actually inserting is just some code in the HTML that instructs the display mechanism where the image is and possibly other aspects such as size and whatnot. RoboHelp tracks all this in assorted files. So when you move an image from one location to another, RoboHelp simply changes the path so the topic can still find the image and it will present correctly in the output.
I am not having any success after following your suggestions. Here are the steps:
1. created "images" folder on RoboHelp 11 Project Manager
2. closed RoboHelp 11.
3. moved all images from root folder to images folder, in windows explorer.
4. deleted the cpd file in the project folder.
5. Open RoboHelp 11.
The result is that I have broken image icons on the project manager with red Xs on them. On the html pages, the links are broken and represented with small red boxes.
Can you please let me know what I am doing wrong.
I think if you then fix one of them, the rest will follow suit.
I tried to fix one of them by pointing to the new location. however, it copies the image back to the root folder of the project.
The whole problem here is that you have an application called RoboHelp. This application manages the project and keeps tabs on everything inside it. That means YOU MUST use RoboHelp to perform any actions such as moving things around.
Think of it this way. You are a homeowner. If you move something from room A to room B, you know where it is. Now a neighbor could come into your home and move things from room A to room B, but you would have no clue where the object was, would you? That's precisely what happens if you go behind RoboHelp's back and move images from one folder to another.
Any movements MUST be performed from inside the RoboHelp application. If you don't work this way, RoboHelp simply gets confused and has no clue where the images went. So all the references will be broken. If you really want a specific Images folder, you will have to use RoboHelp to create one, then carefully move the images from the project root to the folder. And unfortunately, it's a "move them one at a time" operation. There may be a way to accomplish it using the scripting function of RoboHelp, but it would require knowledge of how to write scripts.
Just to be clear Rick, your original reply does not work?
"However, if you are moving all the images to a folder named "ScreenShot", you could probably accomplish it by using the RoboHelp find and replace to amend all the image references. Then sneak behind RoboHelp's back and move the files using Windows Explorer.
You would likely also need to clobber the CPD file and let RoboHelp rebuild it after you were finished."
I guess I would have to leave the file as is since there are over a 1000 image files I would have to move one by one lol.
Sorry, my mistake – go with what Rick is saying you need to do.
Okay, sorry. Mea Culpa for not re-reading the entire thread and shooting from the hip.
Here's the deal. When you have a RoboHelp project, you also have the ability to create folders to organize your content. And topics (HTML pages) can be inside different folders. So let's assume the simplest arrangement. No folders at all. All topics and all images are right there in the root folder. All is well, no?
And inside each topic, the image reference HTML code would look something like this:
<img src="ImageFileName.png" alt="" style="border: none;" border="0" />
Now we create a folder named "Images" and move the image using RoboHelp. So at that point, the image reference would change and look like this:
<img src="Images/ImageFileName.png" alt="" style="border: none;" border="0" />
As long as everything is at the root, you would be totally safe in slipping behind RoboHelp's back, using Windows Explorer to move all the images, then using the find and replace tool to ensure that all references now are prefixed with "Images/". Where it gets tricksy and will fail horribly is when topics are inside folders.
So if I have a folder named RF and a topic is inside that folder and it references an image in the root of the project, the image reference looks like this:
<img src="../ImageFileName.png" alt="" style="border: none;" border="0" />
And if that topic was also inside a folder named Biff that was also inside the RF folder, it would look like this:
<img src="../../ImageFileName.png" alt="" style="border: none;" border="0" />
So when folders are introduced into the mix, it's not as simple as it might be otherwise. Because that code referencing the image will change based on where the topic using the image actually is.
Of course, doing everything in RoboHelp is the preferred way, as when you move things around, RoboHelp handles all the code tweaks to make it all still work when you are finished.
Willam may have a script (or could surely write one) that would likely help here. In that case, you could continue the path of moving to a folder, then using the script to amend the code so it all still works. You could also take things in phases. Work folder by folder. Move ONE image, note the code leading to the image, then use the find and replace to adjust the code.
Sorry for the confusion... Rick
I just saw this on Willams site. While it doesn't move the images to a single common folder, Willam can probably configure that.