We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
We upgraded our merged HTML5 project from Classic to 2019. The child projects seem not to be communicating with the parent on their "look". The upper right corner should be a search box but instead it says "Click to see this page in full context". Additionally, the header is not displaying the favicon that I set up in the parent. Instead, it's displaying a light blue dot that I suspect is the default for Azure Blue, which is what all the child projects are set to. Even if I add the correct favicon in the child project, the light blue dot still displays. I'm not sure if I'm having problems with settings, problems with parent/child communication, or both.
In the new UI the skin for the parent applies to all the projects. You have to set a skin for each child to be able to generate but it doesn't matter which one you set, the parent skin rules.
It's all explained in the merged help section of my site.
The parent skin isn't being reflected in the child projects, though. I checked my generate folder and everything seems to be in order there. This must mean there's something getting lost between generating and testing.
This must mean there's something getting lost between generating and testing.
Do you mean when you test this locally it's all fine but it goes wrong later? If it's right locally then what has been copied to wherever is not the same.
Download the demo on my site. Experiment with that by setting one skin for the parent and different skins for the children.
To focus on something specific, I downloaded your demo (thank you!) and created my own responsive skin and successfully generated a merged project. I understand that the "Click to see this page in full context" appears when a child project topic is opened directly. In my own project, the topic opens successfully but the "Click to see this page in full context" link fails (error that the file could not be accessed either moved, edited, deleted). This happens from my local generate folder as well as when published via my company's software (we use CSH). I didn't see anything different between the demo and my project, except for the default topic, which points to a page in a specific project. What allows the "Click to see this page in full context" link to work?
If it helps, here's an example URL of the successful page:
Here's an example "Click to see this page in full context" link that doesn't work:
Are your projects stored in the machine's Program Data folder?
That folder is not something I would use. Try moving the whole lot to something like C:\MyProject and then see what happens.
I set my merged project up as instructed on your site, originally with RH Classic and we recently upgraded to RH 2019. I did some comparisons between the RH Classic generate folder and the RH 2019 folder. In the RH Classic generate folder, I'm able to open a topic (as an .htm) from the mergedProjects folder and everything works perfectly: the parent skin shows on the child and the search works. In the RH 2019 generate folder, the child shows the skin established in the child project, not the parent. The search does not work either (probably because of a disconnect between the parent and child). Additionally in this parent folder, the index.htm opens great and I can click through the child project topics, though the search does not work.
My question is: with RH 2019, should I be able to see a fully functional project? If so, I have something not set up correctly in my parent/child projects and need to identify it. I've combed through the TOC in the parent and that looks to be correct.
Are you finding this when you open the generated full merge or when you open a child project independently? If the latter you will see the child project's skin. That is explained in the topic on my site.
@Peter Grainge thank you so much for your help. Unfortunately, we still have not resolved the problem and management has deemed we've spent enough time on it. We'll be switching back to Classic for now and will likely look into different authoring options for the future.
I'm sorry management has taken that line. In terms of getting something out of the door I understand but I would have been happy to look at the new merge to get to the bottom of it. I'm sure it is something simple and a lot easier than switching to another tool. Right now this merge is a learning curve for you but learning another tool will be even steeper.
If you are thinking about going to Flare, their method of creating cross project links is not as easy.
Merged help is something I specialise in so it you want me to take a look, let me know. It's not going to cost you anything and it might save your firm money in the long run. Up to you.
My apologies for the late reply. We got the Classic 2019 back to working order--thank you for the generous offer! The header logo was mysteriously using the Azure Blue default logo but after I reset to use ours, it's working again. I'm not sure how the search corrected itself but I'm not going to look a gift horse in the mouth. Now we're testing with a trial of RH 2020, specifically to see how it integrates with Zendesk (we're already using the platform for the company's other products).
Copy link to clipboard
I suspect you opened the help from the start page rather than direct to a topic. Calling a topic directly will get the Click to see... message.