Debugging a FishCart Installation

In most cases, error reporting is turned off in FishCart; this is 
done by setting error_reporting(0) at the top of the files.  This is
preferred for the publicly available pages of a cart, but for initial
installation it may not be the most preferable.  Here are a few things
you can do to help shake out an installation that is not working right.

1) If the error is a "Document contains no data", you may get better
   reporting by setting error_reporting(15).  This is usually done in
   the destination file (where a link ends up, or where the 'action'
   in a <form> tag points).  In some cases it may be necessary to turn
   on error_reporting(15) in the file with the link or the <form> also.

   Thus, if you are updating a zone profile and it is not working,
   set error_reporting(15) in the zone.php file; this is where 
   the <form action=> points in the zonemod.php file.
   
   Or, if you are clicking a link to show the current cart contents
   and it is not working, change to error_reporting(15) in the
   showcart.php file.

   Uninitialized variable messages are usually innocuous.  They
   may on occasion point out deeper problems, but this is not
   typically the case.

2) In a mysql installation, if the database is not being updated it
   may help to put a line like this immediately after the failing SQL
   statement:

<?php echo mysql_error(); ?>

3) If you have a CGI version of PHP available, try executing the
   following from a command line to check for PHP syntax errors.  The
   'php' name may vary depending on what the PHP script is called.
   You may also have to specify the full path to the executable file
   if it is not in your environment PATH.

php -s file.php

 OR

php -s file.php