Search Engine 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 Search Engine 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 Search Engine 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
exec/search.cgi
On most servers, the default path is correct and no change is required.

Upgrading from Search Engine 1.xx to 1.12
Back up your files before proceeding.

File Permission CHMOD Description
exec/admin.cgi
exec/search.cgi		 Executable 755 Program Files
Upload the admin.cgi and search.cgi files, overwriting the existing files. The permissions must be set world executable (chmod 755).
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
exec/vconfig.dat Readable 644 Vendor Data File - upload if not present
This file is used for encoded vendor keys when private labeling the product. The file must be added and made world readable (chmod 644).
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/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.11 and later, we've dramatically enhanced the ability to rebrand or fully private label the software.

For more information, see the Private Labeling documentation.