Migrating from kissdx 0.13-10a to kissdx 0.14

Migration Guide

Migrating from one release of kissdx to the next is easy. Only the following steps are needed for most upgrades:

   1. Make a backup copy of your current kissdx.conf file.
   2. Download and install kissdx as per the instructions for the new release and 
      for your platform. Install the new release to the same directory as the current installation.
   3. Read carefuly the kissdx.conf new location section to ease your first start.
   4. Edit the newly installed kissdx.conf, copying settings from your original configuration as needed.
   5. Run first time in verbose mode to check for messages: ./kissdx -v
   6. Once everything is correct, you could let a launch script do the job itself. 

For some releases other steps may be needed, as outlined below.

Enabling hidden files: -a / --all command line switch has been removed

With release 0.14 the method of initially showing hidden content has been changed.

• Previously, a command line switch was used to specify that hidden content should be displayed: -a or --all
• In release 0.14 this command line switch is no longer supported, and a new configuration setting has been introduced for the same purpose:

   listhiddenentries = yes

This means that the following must be considered when upgrading:

• If you currently have -a or --all on the kissdx command line in a startup file, you must remove it.
• If you still want to enable hidden content when kissdx starts, you must set listhiddenentries = yes in kissdx.conf.
• As listhiddenentries provide a permanent display of hidden file (starting with a dot), a more dynamic way may be to control the display of hidden files from the player menu, using the enablehiddenfilestext and enablehiddenfilesminutes settings in the configuration file.

NOTE: This change breaks compatibility with the original kissd.

KML forwarding: -k / --kml command line switch has been removed

The -k / --kml command line switch was redundant and has been removed. Whether kissdx acts as a kml forwarder is now determined by the presence or absence of the kmlforwardurl setting in the configuration file. This means that you must remove the switch from any kissdx startup file.

NOTE: This change breaks compatibility with the original kissd.

KML forwarding: kmlurl configuration setting has been renamed

Release 0.14 introduces a name change for the kmlurl option – it is now kmlforwardurl. So you must edit your kissdx.conf, e.g. like this:

   kmlforwardurl = http://tinystocks.com/k/kiss.php

Background: kmlforwardurl is more descriptive and we want to keep kmlurl free for possible future use.

NOTE: This change breaks compatibility with the original kissd.

The strategy for locating kissdx.conf has been changed

See the new search order. Make sure you don't have a kissdx.conf in the current directory that you do not want to be loaded. In particular, after a make install, move out of the source directory to avoid loading the sample kissdx.conf that accompanies the source:

   cd /
   kissdx -v

NOTE: This change breaks compatibility with the original kissd. Retrieved from "http://www.famille-kahn.com/kissdxmanual/Kissdx_user_manual:_Migration_Guide"