2
Replies
As I have said in the other thread, sometimes generating the parent does trigger generation. It's unusual and for you that seems to happen every time. However, with responsive help you need to generate the parent and all the child project, as I think I have explained in another thread.
I don't have the PDF version of the help so I can't look up what you quote but I had to chuckle at being told to publish to the correct folder. Maybe the theory is you can just generate a child but practice overrules theory and we are not all experiencing the same thing. That's why it appears that we are not all on the same page, it's simply that we have had different experiences, as you are having.
1] Here’s a regular scenario for my co-workers: a new child project is created and merged to an existing merged Help, so the existing parent must be published to add the new child project.
2] In this scenario, from what I can tell, any unpublished changes to any child will be published.
1] Yes, when you add a new child, the parent must be generated again. Note I said generated not published.
2] As to the other child projects, that may happen when you add a new child but when you want to update the output you have to generate all of them anyway with responsive help.If Adobe's help is saying otherwise for responsive help, test it and use the search. Put a different non-dictionary string in each project such as redzebra, greenzebra and so on to see if they get found if you don't generate all of them. I am not saying they won't, just that is what people have found is necessary, regardless of theory.
There is a difference between generating and publishing and only generating will be affected by this issue where generating the parent auto-generates the children.
Are you only finding this happens when you add a child?
It's late here now but I'll create another merge tomorrow and generate just the parent. I haven't seen auto-generate happen for quite a while but another test won't hurt.
I'm happy to test your setup if it can be shared.
BTW. Remind me why you are merging with only 1,000 topics.
See www.grainge.org for free RoboHelp and Authoring information.
I took an existing merge (the demo on my site) and added a new child and linked to it in the parent.
I then generated the parent to a new folder to ensure there were no false results because of existing content. It did not generate the child projects.
Same in both 2015 and 2017.
The more I think about this, the more I am thinking auto-generate was a webhelp issue. Certainly I haven't seen it for a long time.
Are you also getting this if generate my demo project?
As above, if you can share your project privately, I will be happy to take a look. See the Contact page on my site and send the project as instructed there. Do make sure you include a link to this thread and please do not email the project direct.
See www.grainge.org for free RoboHelp and Authoring information.
AdChoices