RoboHelp 2022: Publish Profiles Not Appearing

Forum|Forum|9 months ago
April 9, 2025
3 replies
527 views

Hi Peter. I am having this issue and have tried all the solutions I have found--deleting the Publish folder and copying the files. Deleting the Output Preset from within RH and copying it anew. When I open the project, all of the Publish profiles are intact in the Output Preset. All of the files show synced on our SharePoint site for both of us--the other writer can see the exact same file date / time for the preset. However, when she opens the RH project and navigates to the Output Preset and clicks the Publish link to see the Publish profiles, the entire list is missing ... but I can see the list when I open the same exact project. Again, it appears that the preset file is the same file for both of us--everything shows synced--we can even update a topic separately and see the other's updates--so I know the syncing is working. Do you have any other ideas what we can try or why she might not be seeing the list of Publish profiles? We have several children projects with a parent, and I can see the Publish profiles in all of them--she can see none.
[Moderator Note - thread split off from original post on different thread - https://community.adobe.com/t5/robohelp-discussions/robohelp-2022-output-presets-disappeared-can-t-create-new/m-p/13457947#M147718]

Peter Grainge

Community Expert

I'll look in the morning but this thread was about missing presets and you are talking about publishing profiles. This should have been a new thread.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.

G

Gina39036576znwoAuthor

Known Participant

Thanks. My apologies--I guess because my coworker is missing all of the Publish profiles for the same, synced Output Preset ... but I am not missing any, I thought it was potentially related to this problem.