I maintain a Web site with H&M. Sometimes I need to make only a minor change to one or a couple pages, publish WebHelp locally, then refresh the copy on the site via FTP.
My question: supposing I don't care about having the changed page(s) included in the site's index, what are the minimum files I would have to upload to get the change reflected in the site? Just the main HTML file and its corresponding /jstopics/*.js file?
(Sorry if this isn't specifically a PP topic, but I wondered if output might be affected in this regard by using a PP skin.)
Minimum files to upload after a single topic change
Moderators: Alexander Halser, Tim Green
-
- Posts: 151
- Joined: Thu Dec 24, 2009 8:41 pm
- Contact:
-
- Posts: 202
- Joined: Mon Dec 28, 2015 7:32 pm
Re: Minimum files to upload after a single topic change
I'm wondering the same.
I have found that I always need to re-upload everything, otherwise there are wrong pages, etc...
There seem to be multiple cache files, etc.
I have found that I always need to re-upload everything, otherwise there are wrong pages, etc...
There seem to be multiple cache files, etc.
- Tim Green
- Site Admin
- Posts: 23189
- Joined: Mon Jun 24, 2002 9:11 am
- Location: Bruehl, Germany
- Contact:
Re: Minimum files to upload after a single topic change
As so often, the answer here is "it depends". Here are some basic rules of thumb:
- If you change or update the skin you are using, it's best to upload everything.
- If you add new topics or make changes in the TOC, it's best to upload everything.
- If you update Help+Manual itself, it's best to upload everything.
- If you only make changes in individual topics and nowhere else, then you may be able to get away with uploading the corresponding HTML and jstopics files and all the zoom search files (the search index changes whenever you change anything).
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Re: Minimum files to upload after a single topic change
I use the invaluable Beyond Compare utility from scootersoftware.com to upload to our website, configured to display only "orphans and newer" files on my machine, compared against the (FTP) files on the website, with the folder structure maintained. I think it would be harder to replicate this safely if I did FTP uploads manually.
To make it work, I need to keep to the following simple rules.
1. Make no new help changes between building the help and uploading. Our web server sets the file time to the time of upload.
2. Make sure that H&M is set to transfer the timestamp of the source to the destination. This has to be done in the PP skin as well as in the main project.
3. In our case, one topic shows a version number from a variable held in a file, which gets updated on each build: so in our Finalbuilder project I 'touch' the timestamp of the XML file for this topic (which rarely needs editing otherwise) before the help build, to ensure that its HTML file gets a new timestamp.
4. Set Beyond Compare to ignore the file sizes: they are always different because the upload changes the end-of-line sequences.
After this it is only necessary to open the Beyond Compare saved task and copy everything visible as unmatched or newer from the left to the right, which usually takes under a minute, most of which is uploading new index files. Never had a problem yet. I only ever need to re-upload everything after an H&M upgrade, or if I make a style change or other change which is clearly going to affect all topics. Beyond Compare is very affordable and has a demo version available.
To make it work, I need to keep to the following simple rules.
1. Make no new help changes between building the help and uploading. Our web server sets the file time to the time of upload.
2. Make sure that H&M is set to transfer the timestamp of the source to the destination. This has to be done in the PP skin as well as in the main project.
3. In our case, one topic shows a version number from a variable held in a file, which gets updated on each build: so in our Finalbuilder project I 'touch' the timestamp of the XML file for this topic (which rarely needs editing otherwise) before the help build, to ensure that its HTML file gets a new timestamp.
4. Set Beyond Compare to ignore the file sizes: they are always different because the upload changes the end-of-line sequences.
After this it is only necessary to open the Beyond Compare saved task and copy everything visible as unmatched or newer from the left to the right, which usually takes under a minute, most of which is uploading new index files. Never had a problem yet. I only ever need to re-upload everything after an H&M upgrade, or if I make a style change or other change which is clearly going to affect all topics. Beyond Compare is very affordable and has a demo version available.
-
- Posts: 151
- Joined: Thu Dec 24, 2009 8:41 pm
- Contact:
Re: Minimum files to upload after a single topic change
Tim & Tim,
Thanks to you both.
Thanks to you both.