Skip to main content
Known Participant
August 19, 2009
Question

Problem Importing Topics Between Projects

  • August 19, 2009
  • 1 reply
  • 4376 views

This has fast become my new favorite place!

Ok, here's the scoop:

We had RoboHelp x5 and just moved to RoboHelp 8 a month or so ago. Shortly after the conversion, we copied all of our topics from our original project into a new project for a new product we're rolling out later this year.  The products are similar, but the names of screens and windows are different, so when a new topic is created, slightly different versions need to be created for each. I thought instead of manually changing each topic I could create the topic in one project, then open the other project, import it, and change the template to match the color scheme for the other product and be done with it.

But somehow my doing this caused almost all of the nearly 3000 topics to become "not controlled" in RoboSource Control, affecting myself and 5 other developers. What about the import would cause this to happen and is there a way to prevent this?

I was hoping that for each change we could just change one, import to the other and call it a day instead of having to manually do it twice. Is there a secret way of doing this that doesn't break the system and irritate my co-workers?

Thanks,

WD

This topic has been closed for replies.

1 reply

Captiv8r
Legend
August 19, 2009

Hi WD

I'm going to move this thread to the Source Control forum category where you might hopefully see some suggestions offered.

Cheers... Rick

Helpful and Handy Links

RoboHelp Wish Form/Bug Reporting Form

Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!

Adobe Certified RoboHelp HTML Training

SorcerStone Blog

RoboHelp eBooks

notv4meAuthor
Known Participant
August 19, 2009

Thanks!

Warren

Community Expert
August 25, 2009

The .cpd file is a machine-specific file, and should not ever be in source control (any SC product), as also the .hhp, .pss, and .ldb files.

Good luck,

Leon


We don't source control the cpd, pss or ldb. However, I believe RH incorrectly classes the hhp file as an 'output' file. As far as I'm aware, there is nothing machine specific in it and can be useful in case something goes pear-shaped with the xpj.

Without the cpd in source control, we encounter issues with files added on one computer not being recognised on another, and the only way to get RH to recognise the additions is to delete the cpd and force RH to reanalyse the project. Although to be fair, we haven't not deleted the cpd file in a while - maybe a recent version has fixed a problem since the last time we tried it.