This document is copyright Vince Wooll/Woollyinwales IT, 2011. All rights reserved.
Jomres has a number of different log types available but only the error logging is enabled by default. Other logs are gateway logs, request logs and logging information captured by the booking engine. Unless you've got a specific need it's not recommended that you enable these logs as they'll slow your system down and possibly expose sensitive information.
All logs are saved by default in xml format in the /jomres/temp folder. If you need to use the logging you can enable logging by going to Site Configuration -> Logging tab in your Jomres control panel.
Error logs are available by default and useful for tracking down behaviour within the system. If you get an error message in the frontend of Jomres look at the error log to see if it advises what went wrong. A typical example is where a property manager hasn't been assigned to a property, if they try to log in and view a Jomres page they'll get an error, and this will be reflected in the error log.
When you click on the control panel icon to view the log files you'll be taken to a list of available log files. If there are none available then there will be a message to that effect. To view a log file click on the relevant link, e.g. Request. This will take you to an output page for that log file. The logs are recorded in xml format then read in by a function that builds a more human readable output. The log file is viewed in reverse chronological order; therefore the most recent entries are first. The view will provide each log file in a table showing an information icon, the date and time of the log, the task that was being performed and the message. If you click on the information icon another (green) line is revealed to show the session id and the query string of the call.
Each error log has 2 links in the 'Available logs' page. The first one takes you to a new screen where the log gets updated automatically with the last 10 logs as they're created, and one (the 'noupdate' link) that just lists everything in the log file.
This logs all of the requests sent to Jomres (so gets very big very quickly). It will record contents of the $_REQUEST variable. This script is useful particularly if you wish to confirm that a remote server is indeed communicating with the Jomres server.
This logs activity performed when somebody is using the booking form. Because the booking process is all Ajax based it can be very difficult to track how the system is calculating its prices. To make this a little easier to follow the booking system maintains the ability to log its actions. Whilst it's still complex, the log does help to break the booking engine steps down into manageable bites.
This is a separate log for tracking gateway communications. It will record what was sent to and from the gateway system. It is absolutely vital that you keep this log file secure at all times.
This log file tracks miscellaneous system activity. As of 2.6 its main task is to perform logging of the booking insertion process, but its use is likely to expand in later version.
Logs php errors thrown up. Note, it cannot manage php compilation errors, so if you've introduced an error in the code (e.g. forgotten to include a ";" at the end of a line) then the script will still fail, but otherwise it will attempt to write an error report to the error log file and send the user to an error page.
Logs all that`s happening when a booking is made. This log is useful for debugging booking problems.
Used for commissions logging
When a log file gets to appx 1Mb in size it will be automatically renamed by the system as large log files will slow your system down.