New patch 2003-02-23-15-07-16 PENDING.

A patch was submitted to the patch system:
by a user Chris at host huiskamer.
This patch is now in the PENDING state and 
needs to be checked in (committed) 

For this you need to log on to the server and execute
the following commands in the xaraya-patches repository:
1. cd PENDING
2. bk sfiles -x | bk new -
3. bk commit
4. bk push

This will change the state of the patch to REGISTERED
it wil *NOT* apply the patch. Alternatively, you may
wait for the next run of the cron job which will 
automatically check in PENDING patches.

Once a patch is in the REGISTERED state it will be 
propagated by push/pull operations and patch handling
can be done remotely from that point on in any clone
from the main repository once properly synchronized.

Patch system status:
---------------------------------------------
PENDING   :       2
REGISTERED: 14
---------------------------------------------

The patch contains the following changesets:

ChangeSet
  1.554 03/02/23 16:06:21 Chris@huiskamer. +2 -0
  xarModIsAvailable() will always return null if an error 
  exists on the stack (even php-notices).
  This patch fixes this, though I guess the whole error-line
  check could be removed.. since it will always return Null
  if xarMod_getBaseInfo returns null, so it will never get inside
  this if-block :DxarModIsAvailable

  BitKeeper/etc/logging_ok
    1.66 03/02/23 16:06:21 Chris@huiskamer. +1 -0
    Logging to [email protected] accepted

  html/includes/xarMod.php
    1.140 03/02/23 16:05:54 Chris@huiskamer. +4 -5
    xarModIsAvailable() will always return null if an error 
    exists on the stack (even php-notices).
    This patch fixes this, though I guess the whole error-line
    check could be removed.. since it will always return Null
    if xarMod_getBaseInfo returns null, so it will never get inside
    this if-block :D