config/debug-config.php

   1 <?php
   2 /**
   3 * The configuration settings detailed here should probably not appear in most
   4 * most people's configuration files, but they can be useful to have available
   5 * to assist with debugging problems.
   6 */
   7
   8 /**
   9 * if this is set then any e-mail that would normally be sent by DAViCal will be
  10 * sent to this e-mail address for debugging.
  11 */
  12 //$c->debug_email
  13
  14
  15 /**
  16 * If you want to debug you have to set to 1 one of this variable
  17 * and then you can look at the error log of PHP for example :
  18 * $c->dbg["ALL"] = 1;
  19 * and then tail -f /var/log/apache2/error_log (or wherever PHP errors are logged).
  20 *
  21 * in the code a line like this:
  22 * dbg_error_log( "Login", "blabla %s blalba %s",first_string, second_string );
  23 * will produce in apache error log and if $c->dbg['Login'] ==1 : "blabla first_string blalba second_string"
  24 * using format rules as for printf and related functions.
  25 */
  26 // $c->dbg["ALL"] = 1;
  27 // $c->dbg["request"] = 1;   // The request headers & content
  28 // $c->dbg['response'] = 1;  // The response headers & content
  29 // $c->dbg["component"] = 1;
  30 // $c->dbg['caldav'] = 1;
  31 // $c->dbg['querystring'] = 1;
  32 // $c->dbg['icalendar'] = 1;
  33 // $c->dbg['ics'] = 1;
  34 // $c->dbg['login'] = 1;
  35 // $c->dbg['options'] = 1;
  36 // $c->dbg['get'] = 1;
  37 // $c->dbg['put'] = 1;
  38 // $c->dbg['propfind'] = 1;
  39 // $c->dbg['proppatch'] = 1;
  40 // $c->dbg['report'] = 1;
  41 // $c->dbg['principal'] = 1;
  42 // $c->dbg['user'] = 1;
  43 // $c->dbg['vevent'] = 1;
  44 // $c->dbg['rrule'] = 1;
  45
  46 /**
  47 * default is 'davical' used to prefix debugging messages but will only need to change
  48 * if you are running multiple DAViCal servers logging into the same place.
  49 */
  50 // $c->sysabbr = 'davical';
  51
  52 /**
  53 * As yet we only support quite a limited range of options.  When we see clients looking
  54 * for more than this we will work to support them further.  So we can see clients trying
  55 * to use such methods there is a configuration option to override and allow lying about
  56 * what is available.
  57 * ex : $c->override_allowed_methods = "PROPPATCH,OPTIONS, GET, HEAD, PUT, DELETE, PROPFIND, MKCOL, MKCALENDAR, LOCK, UNLOCK, REPORT"
  58 * Don't muck with this unless you are trying to write code to support a new option!
  59 */
  60 // $c->override_allowed_methods = "PROPPATCH, OPTIONS, GET, HEAD, PUT, DELETE, PROPFIND, MKCOL, MKCALENDAR, LOCK, UNLOCK, REPORT"
  61