DocBuilder Upgrade Instructions - download upgrade - changelog
  1. Back up your data.
    Please be sure to backup all your original files before upgrading.
  2. Do not just overwrite all files with the new ones.
    There is no need to re-install the program, all you need to do is upload the updated files.
  3. Follow the step-by-step Upgrade Instructions below.
    Start at your current version number and work your way up.

Using your FTP client, upload the specific files to your server, overwriting your old DocBuilder files that you have backed up. Make sure to upload each file into its respective directory. ONLY upload the files listed that are required to update your version of DocBuilder to the current version.

Your upgrade package includes all the product files, including blank data files and original templates. If you are upgrading, DO NOT just upload the data/* and templates/* files unless instructed, otherwise you will overwrite your existing data and templates.

PATH TO PERL: If your server previously required that you change the path to perl when you first installed the software, you will need change the path for the following upgrade files:

exec/admin.cgi
On most servers, the default path is correct and no change is required.

Upgrading from DocBuilder 1.xx to 1.12
Follow the upgrade steps above for all newer versions before upgrading the files below.
File Permission CHMOD Description
exec/admin.cgi Executable 755 Program File
Upload the admin.cgi file, overwriting the existing file. The permissions on this file must be world executable (chmod 755).
exec/vconfig.dat Readable 644 Vendor Data File
This file is used for encoded vendor keys when private labeling the product. The file must be added and made world readable (chmod 644).
templates/interface/
templates/interface/*.*		 Executable
Readable		 755
644

Interface Templates
All interface templates have been updated and need to be uploaded. The file permissions for these files are world readable (chmod 644), and the folder must be world executable (755). If you have the following file, you will need to remove (delete) it:

  data/interface.dat
Optional
exec/config.ini Executable 755 Config File
If you do not already have a config.ini file in your /exec/ directory, you will need to upload this file and set the file permissions for this file are world executable (chmod 755). If you already have this file, do not upload over top of it.
images/htmlarea/
images/htmlarea/images/
images/htmlarea/popups/ 		Executable 755 WYSIWIG Editor
If you do not already have the htmlArea files and folders, please upload the /images/htmlarea/ directory, sub-directories and contents. All folders should have permissions set to world executable (chmod 755) and all files should be readable (chmod 644).
images/htmlarea/*.*
images/htmlarea/images/*.*
images/htmlarea/popups/*.* 		Readable 644
images/login_copyright.gif
images/login_image.gif
images/login_logo.gif
images/sample_image.jpg 		Readable 644 Image File Updates
You'll need to upload several image files.

Private Label

With version 1.12, we've dramatically enhanced the ability to rebrand or fully private label the software.

For more information, see the Private Labeling documentation.

Collapsible menus

In version 1.07, we've enhanced the doc_menu template to show the topics using a JavaScript collapsible menu. To use the menu, you'll need to upload the following files:

images/node_dot.gif
images/node_minus.gif
images/node_plus.gif
templates/_doc_menu.html

Please note that _doc_menu.html will overwrite any template modifications you've made to that file, and you'll have to make these modifications again. The previous version of the menu file is in _doc_menu_oldstyle.html.

SSI filtering

In version 1.10, we've added SSI filtering -- that is, server side includes such <!--# ... --> will be removed from documents added through DocBuilder. (This does not apply to templates, just content added through the DocBuilder interface).

This is the default behavior because SSI's can be used by malicious users to damage your website. If you have existing SSI's that you want to preserve, you need to upload or edit the exec/config.ini file and add the following line:

allow_ssi = 1

Note that PHP includes are not filtered.