Publishing in RoboHelp 2019.05 fails to copy all files

I was unable confirm, even with further testing, if the problem was caused by SharePoint source control and multiple editor PCs, but I suspect I was because I had trouble getting the SharePoint connection to work in one location (I added a comment to Re: RoboHelp 2019 and SharePoint Online connection profile ). The problem might also be related also to setting the output folder path in Preferences. At one site where I work, the default location in your profile ends up on a slower WAN share so I experimented with setting it in the preferences to use a local path and also on a removable SSD that I could take with me to other sites.

I couldn't find a way to remove source control from a project in RH 2019 once it was enabled to rule that out as being the cause. To work around that, I started to build a new project without source control being active by re-converting the original one from RH 2017 to RH 2019 again, but I had to give up in the end because I ran out of time.

It is a huge effort to convert to a project of any size from RH 2017 to RH 2019. In my case, I had about 100 videos embedded in various pages, but none of these came across properly in the conversion. They get added in RH 2019 as "Flash objects" that simply don't work. I had to go though each page and replace the HTML using the source code view with the simpler <video> tags that RH 2019 would itself normally use when you add a Video File using the new UI. I also had issues with header being physically copied from the Master Page into some individual pages but not others, so I ended up with double headers on some pages. I think this must be related to having a footer with a "Date Last Modified". In RH 2017, you could change the date for an individual page without affecting the other pages in the site. I'm not sure how this works in RH 2019 where it seems you can only use the Master Page globally (so both header and footer are repeated across the entire site). Finally, I also found that there was a fair bit of work needed to update the Azure_blue skin to match the 2017 project design, which had been customized sightly. I wasn't game to simply copy the skin from RH 2017 to RH 2019.

I think I'll have to stick with RH 2017 (or use RH 2019 Classic) for the foreseeable future until the new version becomes more mature and Adobe irons out some remaining problems with the new design. There are some nice features in RH 2019, but the simplification of the UI seems to remove some flexibility that we had with the classic design.