Hi, mmphillipstx.
We actually have two issues here and I think we need to
separate them.
1. One is the best practice and procedure to reconstruct a
RoboHelp project when a hard drive fails, etc.
2. The other is to diagnose why the FTP failed - because even
when you published the Customer Care project, it didn't work. These
issues may or may not be related?
The only reason I brought up the RoboHelp Server possibility
(I know you're not using it) was because when I tried last night to
publish a WebHelp project to my RoboHelp Server 7, I got the
*identical* error message! I guess this was merely a coincidence.
But it suggests some lack of communication with the server on the
other end and thus my wondering if the FTP publishing wizard
settings are accurate. Make sure your permissions, firewalls, etc.
allow you to FTP from your PC to the server.
To narrowly answer your question about the three files you
mention:
1. All three files are NOT part of your source material.
Rather, they are OUTPUT files generated when you publish a project
to a server. (therefore you would not import them to your project
if you are trying to reconstruct it)
2. The cshdat_webhelp.htm and cshdat_robohelp.htm contain
ready-made JavaScript functions to assist in the event the help
system is asked to deliver any topics called as part of Context
Senstive Help (CSH). These functions are generated whether you
actually have Map IDs and CSH or not. The functions are sort of
there just in case they are needed.
3. The bsscftp.txt is a control file generated during the
publishing process. It is essentially a "log file" that is
generated ONLY in the output of a published help system. (i.e., you
won't find it in the WebHelp folder under !SSL!. You would only
find it on the destination website.) I *think* it is used to keep
the files "in synch" during a file comparison when you republish.
The idea is that when you publish to a site, it will only send
across files that are "new" in order to save time.
BTW, the bssc goes way back to the beginnings of RoboHelp.
BSSC stands for Blue Sky Software Corporation. (Now you know
)
Because these are OUTPUT files, generated during the publish
process, it would be illogical to import them to your RoboHelp
project if you are trying to reconstruct a crashed project.
I'm afraid I may not have solved any problems, but perhaps
this will help you diagnose the situation better. It seems to me
your first step is to create the Publishing wizard FTP site
settings and publish the Customer Care project successfully to make
sure that problem is solved. Then you can go back to the repair
work on your post-crash reconstruction.
If I trip over something else, I'll chime in.
Thanx,
john
John Daigle
Adobe Certified RoboHelp and Captivate Instructor
Newport, Oregon