We are having constant issues with RoboHelp 11 when attempting to publish a Project to SharePoint 2010. The error message just states 'Unknown Error' and references an image file for a recently imported topic. As there appear to be no settings in the import function to specify how to handle image names the only remedy we have found is to manually amend the path for every image loaded during the import routine to be ../IMAGENAME rather than the full file path for the Image. In addition we have had to rename each image to avoid over writing existing images. As you can image this is extremely frustrating and time consuming.
Any assistance would be appreciated as we are getting to the point of looking for an alternative product as it is clear that RoboHelp 11 does not work well with SharePoint.
Unknown errors are always a pain as it's hard to find where the problem is. Are you using the publish option to SharePoint of the native sharePoint integration for HTML5?
The Publish option basically requires you to publish to a network drive that happens to be a mapped SharePoint library. Only the HTML5 native method works by talking to SharePoint directly. At least, that's my experience,.
What is the output you're creating? If it's HTML5, try to go to the SharePoint options and expand the Advanced section at the bottom of the dialog. Make sure to enable the option to 'Generate SharePiont Native output.' and try again.
Thanks for the reply.
We are using the Responsive HTML5 output format and have the option 'Generate Share Point Native output before Publishing' flag set.
Too bad. We can rule that one out.
Does the output work if you manually copy it to SharePoint? Or is it broken in that case? (Quickest is by using File Explorer.)
I'm wondering about the images you mention: after amended the path: are the images in the project? Or are you referencing external images with a relative path?
As for a sanity check: if you make a copy of the project and throw out the offending topics, are you then able to publish to SP?
Thanks for the reply
Having had an online discussion with Adobe it appears that we can get around the issue if the folder created when a topic is imported is renamed from 'importedfilename_images' to 'importedfilename'. We can also get the project to publish if we remove the tick from 'republish all'. This obviously helps out but ideal we need a software fix - I have asked Adobe if this will be done but not had a reply as yey.
I'm curious as to why you would want the Republish all enabled all the time?
The beauty of the publishing process is that it saves time. And part of that is achieved by tracking what has been published and only publishing what is actually needed during subsequent publishing sessions.
It is just a habit we have! If not publishing all gets around the current issue we will make stick with doing that. I