0.13beta1 error - Cannot redeclare class mysql_cmsms_extender

[kevin360]

Currently I have running version 0.12 and it works fine.  I just downloaded 0.13beta1 and did a fresh install to a test directory and a test database to make sure it would work proper.  Everything installed fine, everything came back saying it was ok.  When I tried to then click on the final link to go to the site I get this:

Fatal error: Cannot redeclare class mysql_cmsms_extender in /usr/local/apache2/htdocs/cmstest/lib/adodb_lite/adodbSQL_drivers/mysql/mysql_cmsms_module.inc(7) : eval()'d code on line 1

I've compared the two config.php files from 0.12 and 0.13beta1 and they are setup similarly.  Both are have the dbms set as follows:

$config['dbms'] = 'mysql';

This is a Slackware 10.2 machine, running Apache 2.2.0, php 4.4.2, and mysql 5.0.20a.  Any ideas on why the beta version gives this error and 0.12 works fine?

[Piratos]

You have the full adodb - version AND adodb lite version - they have the same class names.

delete one of them.

[kevin360]

You have the full adodb - version AND adodb lite version - they have the same class names.

delete one of them.

Can you provide a little more information on this please? 

The config.php for version 0.12 I have set to use adodb lite and it works fine.  I only downloaded 0.13beta1 and installed it, nothing extra.  I tried a search for adodb with slocate and it only comes back with directories to adodb_lite.  I tried renaming the directory for adodb_lite in 0.13beta1 and then changing the config.php to use just adodb and I get this error:

main(/usr/local/apache2/htdocs/cmstest/lib/adodb/adodb.inc.php): failed to open stream

[kevin360]

Solved the problem!  I'm running php_accelerator and when I deleted all the accelerator files in /tmp/phpa_* then it came up fine.  Might be something worth noting in the documentation.

[sloop]

I had the exact same problem under the current 0.13 release.  A new site install would come up blank pages, both the site itself, and the admin pages as well.

The solution was one I'd never have stumbled upon in a million years: deleting /tmp/phpa_* - just as kevin360 reported.

While this probably isn't a CMS bug, it sure is affected by it.

Something needs to be to the README, otherwise you'd never know, and be stuck with a dead CMS installation.