How to setup Site Publisher by Helexis Software

I use this program to use my old Front Page on a server without any extra extensions and / or most server don't allow these extensions.
I now use Microsoft Expressions Web 4 (free) that took my entire old site with no problem.
If you are not doing real fancy stuff and don't want to start from scratch, this may be the solution.

SITE PUBLISHER BY HELEXIS SOFTWARE

Site Publisher by Helexis Software will do what Front Page used to do, allow an easy to use program to make a web site.
FIRST: This not CPanel "site publisher" where you login and change your web site by remote.  This is a installed PC program with a similar name to change the web site you have on your HD.  This PC product looks on your HD at the site files, sees what is on the server, and sends up new or changed files.  There are other options if you have newer files on the server and such.  Since you always need to work on your web site from this PC, there should be NO newer files on the server.
So your original web site must be on a PC's HD, not on the server.  This is how this works.  It sends a copy to the server.  If this program and the web site files are on a laptop, as long as you have internet access you can change the site where ever the laptop is located.  The problem is, Expressions Web 4 still uses the hundreds (or thousands) of "management" files.  These are the \_vti_cnf and \_vti_pvf files found in each folder.   In the settings of the program, you can add these files to an exclusion list.  You many need to add other exclusions as the site will look at files on the server that are not on you HD such as \cgi or \logs and ask to delete them.  When you first run Site Publisher, it will ask to delete files not on your PC.  Write down just the folder names from the server it wants to delete, say NO to delete them, then add the folder name to your exclusion list.
So if you have to download the files to a PC, it will most likely copy all the extension files.  You will need them on your HD to run FP. The first time you run Site Publisher, when the exclusions are added, it will remove all of them from the server automatically.  A large site will contain hundreds to thousands of them.
Your site may have many more of these files, watch you upload list, you can pause it while you write them down.  Then Cancel it, add the exclusions, then try again.

TWO: Site Publisher needs the standard web site name and login password.  It can be setup like a FTP program.  Your upload directory can be any folder.  You can add as many "profiles" as you like and update them at any time.  I have one "profile" per web site.  The good part is FP or Expressions 4 will try to update all your files including the hidden \_vti_cnf  files per folder, where as Site Publisher can be set to exclude them.  These file are needed on your HD as you can move files and folders and Expressions 4 will change the link when needed.  But a standard FTP program will only send up folders or files you highlight (including _vti_cnf files, this program will check the files on your HD, then check the server and sent up any new files  or remove files you deleted on the HD.  If you move or delete files or folder, this program will make all the necessary changes.  So whatever is on your HD as a site, is duplicated on the server.  Site Publisher can also Cache the server directory.  I have 54K files and it would take 10 min to check all those files on the server each time.  Site Publisher will create a Cache file of the server files.  So it only takes 15-30 seconds to check the HD then the server Cache and then start sending up / or deleting files.  Any new files that are copied to the server are added to the Cache files for the next time.  So that Server Cache is up to date, you only have to do it once. I have it set to always require a conformation to delete files.

I have been using Site Publisher for a number of  year.  I have a simple HTML site, nothing that fancy.  I just happen to have thousands of links.  No way I am going to Text editing or HTML editing.  These are he tricks I have found out over the years.  I do believe daylight savings time changes is done automatically now.  You may have to run the "check server" to match the times of the PC and server files again.  I have had individual profiles or the entire site go bad in the program.  Once or twice a year, nothing bad.  You can basically copy the PROFILE directory (users - xxx- AppData - Roaming - Helexis - Site Publisher - Profiles)     Copy the Profiles folder and put it somewhere safe.  You can replace the entire Profile folder or individual file (website) if something goes crazy.   When you do an update with the replaced file/folder, it will check the old server copy and will upload the files (again) that may have been added since you made the last copy of the Cache.  Any new files are added to the Cache files for the next time.  So that Server Cache is up to date.
So if you copied the Cache file three months ago, and you many many changes over those month, it will simple copy those files again.  This is better then remembering all the login information and file exceptions if you have multiple sites.

Initial Setup:

Fill in the host name and the password, then at the bottom press OK.  Open up the Profile again and you will see more options. You will see folders to sync and inclusion / exclusion.  You can type in the \_vti_cnf by clicking EDIT on the right side.  DO NOT LEAVE AN EMPTY FILE THERE.  The program will take that as "do nothing".  Put something there, hight it, then delete it.  Should you have capital \_VTI_CNF files on your HD file, you need to add them in the same case.   I add both _vti_cnf and \_vit_cnf to the exclusions as the second one covers all subdirectories.  Depending on your server your site is on, other folders/files will show up.  Just say "do not delete" after you write the folder name down, then add them to your exclusion list.  Run an update again, it will HAVE TO check the server again.  Any changes to that part of the system makes it check the server cache from scratch.