Skip to main content
N
notv4me
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
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

N
notv4meAuthor
Known Participant
August 19, 2009

Thanks!

Warren

A
Anonymous
August 19, 2009

Just to clarify the situation a bit, is this what happened?

1. You created project A in RH X5.

2. You converted project A to RH 8.

3. You put project A into RSC (before or after conversion?).

4. You created a new project B in RH 8 and imported all the existing topics from project A OR

    You made a copy of project A and renamed it project B.
    (Which one of these methods did you use?)

5. You put project B into RSC.

6. You have successfully been editing topics in project B and checking them back in to RSC.

7. When you need a new screen topic, you add a topic to project A (and therefore to project A in RSC).

8. You import the new topic to project B. The newly imported topic is not in RSC ("Add to source control") and all the other topics in project B are now out of RSC ("Add to source control").

9. The topics that lost their source control are still visible in project B's Project or Topics pod.

I don't have a solution (barely an inkling), but I am wondering if there is some connection between these projects in RSC that shouldn't be there.

An additional question - are you importing these topics into the root directory or into folders within project B? A couple of people have reported some RSC instability when changes are made to the content at the root level.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices