Robohelp Indexes

[zachary_0304]

1)I am copying updates to Robohelp where I need to isolate copying those files to those that are actually updated. Using FileZilla I added a new topic and copied its htm file into the existing URL with its associated graphics and

• whxdata Including text subfolder
• Also included in the root directory
  • index.*
  • search.htm
  • projectdata.js

One issue is my searches now only produce the results for the new topic, and the other sample are "corrupt". Unless there was an overwrite issue in FileZilla where I was unknowingly not/overwriting the wrong files, what files need to be copied for this to be resolved?

2)In another Robohelp Help file I have the same issue as above but additionally some of the links display the index overwriting the topic as well. I need to delve more into this, but any ideas on what files need to copied/deleted for this to work?
Many thanks in advance!

[Peter Grainge]

You haven't said which version of RoboHelp you are using. Please always start a thread with this information.

I have to ask why you are working this way. When you publish an output, rather than generate, there is an option to only republish what has changed. RoboHelp puts a file on the server that lets the publish process know whether or not that topic has changed.

I don't know what to suggest as you are choosing to work outside how RoboHelp was designed.

________________________________________________________

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

[zachary_0304]

I thought my message would have posted yesterday, so I am reposting my response. I am working with Robohelp version Version 2022.4.179. My apologies for not following protocol. It was demonstrated to me that I use Generate for any updates. I generate my files onto my C: drive, and then copy only the changed files onto a staging area URL where they are tested. The latter has been recently emphasized to isolate those files which are altered for ensuring testing covers only new revisions.  Once the files are tested there, I copy them into Production for the users. My understanding is that Publishing sends the results directly to the users. Can I use the Publish function to only send those files that have updated onto my c: drive? Thanks for your assistance and your timely response.

[Jeff_Coatsworth · Accepted solution]

Yeah, I'd add that if you're going to work this way, it's always safer to first wipe all the files/folders at the destination first and then transfer the new files over completely.

[zachary_0304]

Thanks. I posted a response above to the first reply which I thought I had posted yesterday. Seems like copying all the folders/files is the feasible solution.

[Amebr]

You can set up a separate publish destination that publishes to your staging area. You just need to make sure you select the correct publish destination before you right-click Publish.

You could also set up a separate output preset if you wanted to,  e.g. My_Help_Test and My_Help_Prod.  It might make it easier to ensure you don't publish to the wrong place. As with anything it has pros and cons. 🙂

[zachary_0304]

Thank you Amebr.