Yesterday I deleted about 10 images from RSC because (1) they were no longer used in the help project and (2) RH had not deleted them from source control itself. Note: I did not just hide these files - I deleted them.
Today when I try to "get" the whole project, I get error messages for each of those files. Caption: RoboSource Error. Message: "Error - path '[path & filename]' is invalid."
Since these files are in various subdirectories of the project, and RSC refuses to continue getting the rest of the files after it encounters this type of problem, this means I now have to "get" the project directory by directory. Grr.
Ok, so RSC did not like me deleting the files from RSC Explorer. So how do I fix this problem? I tried adding the files back into RSC, but I get a different error message: "Error - node '[path & filename]' already exists." (Um, which is it -- is the path invalid, as claimed by the first error message, or does it already exist, as claimed by the second one?)
I don't know what else to try.
The other (less urgent) question is, if I can't delete old images from RSC Explorer, and RH doesn't see to it that unused images are deleted from source control, then how do I get unused images out of source control?
Any help would be appreciated -- especially quick help! :-)
Eileen, this is very similar to a situation my team faced a few weeks ago, though our error was related to deleted topics and not images.
I'm not sure why exactly RoboSource throws up this error, but we did notice that the root.fpj file retains references to the deleted files, which makes RoboSource look for them, and when it doesn't find them it starts acting all wonky. Adding the files back doesn't work b'se for some reason RoboSource recognizes the deleted files as still being part of the project. Talk about ghosts in the system!
However, we did find a workaround that worked in our case. Open the root.fpj file in a text editor like TextPad, and remove *all* references to the deleted files. (In case of our topic, this also included the HHC file.)
Do post back if this solution worked for you, or if you found another fix for this issue!
Actually, we were using RH 8 with 802 applied when this error cropped up. We've moved on to RH9 and a whole different set of problems since.
Just to clarify, my topics didn't really go missing - I deleted a couple of troublesome topics from RSC (instead of being good and deleting from within RH as I should have) and then tried recreating them using RH, but I simply could not create them b'se RSC detected them as "already exists". When I tried retrieving these supposedly extant files, I couldn't retrieve them either b'se RSC prclaimed them "invalid".
Removing references from root.fpj worked for us - I think it made sure RSC wouldn't expect those files in the project.
P.S. - Your site is one of my first stops when I run into any RH-related issue. Thanks for all your help!
We had already applied the 802 patch.
I don't remember now how I solved this problem (it was back in April I posted it), but it was probably by editing the root.fpj file.
Thank you for your replies!
Europe, Middle East and Africa