Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Minor
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.0.5
-
Fix Version/s: 4.1.0
-
Component/s: Core CiviCRM, Drupal Integration Modules, Standalone CiviCRM
-
Labels:None
Description
Using:
CiviCRM 4.0.5
Drupal 7.8
Ubuntu 11.04
I have came across an incompatibility between CiviCRM's PEAR packages, and another system-installed PEAR package. The package in question is "Services Atlassian Crowd", and the conflict appears to be between the PEAR_Exception class being called independently by both packages.
/var/log/apache/error.log provides:
[error] [client 180.76.5.111] PHP Fatal error: Cannot redeclare class PEAR_Exception in /var/www/dev_OSMsite/sites/all/modules/civicrm/packages/PEAR/Exception.php on line 389
Services_Atlassian_Crowd is used by the drupal / crowd interconnect module, which provides authentication for drupal against the Atlassian stack (Confluence, Jira).
Accessing any page in the /civicrm directory results in an HTTP 500 Internal Server Error, and more log entries to /var/log/apache/errors regarding the PEAR_Exception class.
Can this be patched on the civicrm side?
Managed to fix it. As it turns out, /usr/share/php/PEAR/Exception.php and civicrm/packages/PEAR/Exception.php are virtually the same, with only minor differences.
civicrm/packages/PEAR/Exception.php was modified by placing "if(class_exists('PEAR_Exception') != true) { }" around the entire class statement. ie.
if(class_exists('PEAR_Exception') != true)
{
class PEAR_Exception extends Exception
...
...
...
}