Advanced search  

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Pages: [1]   Go Down

Author Topic: Fatal error: Cannot redeclare class joomlaversion.......  (Read 5471 times)

0 Members and 1 Guest are viewing this topic.

dwaggener

  • Coppermine newbie
  • Offline Offline
  • Posts: 1
Fatal error: Cannot redeclare class joomlaversion.......
« on: March 04, 2006, 10:43:29 pm »

I am running Joomla 1.0.7 with coppermine 1.4.3.  After my initial install,  I made some errors and backed everything out.  After re-installing, I get the following error after enabling the bridge.

Fatal error: Cannot redeclare class joomlaversion in /usr/local/psa/home/vhosts/dwdigitals.com/httpdocs/joomla/includes/version.php on line 18

I've looked through the FAQs and documentation and have not found a reference to this error.  It has been awhile since I've had time to get back on this and I'd like to upgrade to 1.4.4 but not until I have this error corrected.  Any suggestions?

Thanks
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: Fatal error: Cannot redeclare class joomlaversion.......
« Reply #1 on: March 05, 2006, 01:33:27 am »

the error message comes from a Joomla file, how are we suppossed to know what it means? We know Coppermine, we don't know Joomla.
Logged

Nibbler

  • Guest
Re: Fatal error: Cannot redeclare class joomlaversion.......
« Reply #2 on: March 05, 2006, 01:58:22 am »

Change these lines in the bridge file

Code: [Select]
include($BRIDGE['relative_path_to_config_file'] . 'configuration.php');
include($BRIDGE['relative_path_to_config_file'] . 'includes/version.php');

to

Code: [Select]
include_once($BRIDGE['relative_path_to_config_file'] . 'configuration.php');
include_once($BRIDGE['relative_path_to_config_file'] . 'includes/version.php');

That's the only thing that could be causing the problem from Coppermine's end. It's probably a symptom of some other error since this would not normally be an issue.
Logged
Pages: [1]   Go Up
 

Page created in 0.02 seconds with 20 queries.