Errors upgrading from 0.13 to 1.0.2 -- RESOLVED

[badfrog@w00tz!]

Hey all -- just tried updating my test site from 0.13 to 1.02 and am getting these errors:
Upgrading config.php...[done]

Cleaning cache dirs...[done]

Adding Cross Reference tables...

Warning: newdatadictionary(/home/w00tz/public_html/test/lib/adodb/adodb-datadict.inc.php): failed to open stream: No such file or directory in /home/w00tz/public_html/test/lib/adodb/adodb.inc.php on line 3821

Warning: newdatadictionary(): Failed opening '/home/w00tz/public_html/test/lib/adodb/adodb-datadict.inc.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/w00tz/public_html/test/lib/adodb/adodb.inc.php on line 3821

Fatal error: Call to a member function on a non-object in /home/w00tz/public_html/test/install/upgrades/upgrade.20.to.21.php on line 16

erm... lets see... my process was: FTP up new cmsms files, run /install/upgrade.php, which told me I needed an upgrade. I *can* get into the admin site after upgrade, but my site is only partially functional, only about 1/3 of the index page renders, but there are no errors.

I'm running on Apache 1.3.36 (Unix/Linux), PHP version 4.4.2, MySQL 4.1.21-standard
The only non-standard module I'm running is Cataloger which is 0.2 (I know, it's been updated).

Since this is my test site, I'm not panicking or anything, but I'd like to update the main site soon. So... uhm.. help?

UPDATE: Just wanted to add some additional info after poking around the forums around a bit...

Cataloger is not used on the index page, so I'm thinking that's not the source of the problem despite being waaaay out of date.

The index page is a static menu, banner, etc added into the template via Global Content Blocks, some (homebrewed) user-defined tags that grab random Gallery2 images and a couple news listings, one using a db template, another using a disk template. Only the user-defined "random image" tags appear to render any content, and those formatted correctly. The rest of the page is blank.

Did something change that prevents module/global content calls from within a template maybe?  'cuz that's the only probably out-of-the-ordinary thing I'm doing.

[Dee]

It looks like $config['use_adodb_lite']  is set to false in config.php (lib/adodb is used, not lib/adodb_lite) and adodb gives errors (adodb-datadict.inc.php cannot be found).
Try uploading a new full adodb version (or switch to adodb_lite).

[badfrog@w00tz!]

I checked config.php and found this line:

$config['use_adodb_lite'] = true;

Checking further, it looks like some of the path settings were incorrect in config.php -- they don't include the full path to the test site's installation folder.

After updating the following settings to point in the right spot (they all were previously missing the /test portion):
$config['root_url'] = 'http://w00tzgames.com/test';
$config['root_path'] = '/home/w00tz/public_html/test';
$config['previews_path'] = '/home/w00tz/public_html/test/tmp/cache';
$config['uploads_path'] = '/home/w00tz/public_html/test/uploads';
$config['uploads_url'] = 'http://w00tzgames.com/test/uploads';
$config['image_uploads_path'] = '/home/w00tz/public_html/test/uploads/images';
$config['image_uploads_url'] = 'http://w00tzgames.com/test/uploads/images';

and re-running install.php, I now have these results:

Code: Select all

Upgrading config.php...[done]

Cleaning cache dirs...[done]

Adding Cross Reference tables...
Warning: newdatadictionary(/home/w00tz/public_html/test/lib/adodb/adodb-datadict.inc.php): failed to open stream: No such file or directory in /home/w00tz/public_html/test/lib/adodb/adodb.inc.php on line 3821

Warning: newdatadictionary(): Failed opening '/home/w00tz/public_html/test/lib/adodb/adodb-datadict.inc.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/w00tz/public_html/test/lib/adodb/adodb.inc.php on line 3821

Fatal error: Call to a member function on a non-object in /home/w00tz/public_html/test/install/upgrades/upgrade.20.to.21.php on line 16

There is no file called adodb-datadict.inc.php in my test installation, or on my main site, which is still running 0.13. I'm confused as to why the error paths reference /adodb/ since the config file sets use_adodb_lite to true?

/test/lib/adodb/adodb.inc.php has this version number: @version V4.65 22 July 2005
/test/lib/adodb_lite/adodb.inc.php has this version number: V1.20 ADOdb Lite 2 April 2006

[badfrog@w00tz!]

I've apparently exhausted the available supply of help 

I'm obviously missing at least one required file. I'll try uploading everything again and upgrading, see if that changes things.

Question, though -- if $config['use_adodb_lite'] is set to true, does that mean CMSMS is supposed to be using ADODB_LITE? If so, why does CMSMS appear to be looking in /lib/adodb for files instead of /lib/adodb_lite?

-------------------------------------------------------UPDATE:-------------------------------------------------------------------------

Re-uploaded all the 1.02 files, visually verified that lib/adodb_lite included a file named adodb-datadict.inc.php, visually verified that config.php had a line like this:

$config['use_adodb_lite'] = true;

Verified the db connection settings, passwords, paths, etc were correct. Ran install/upgrade.php and....

Upgrading config.php...[done]

Cleaning cache dirs...[done]

Adding Cross Reference tables...
Warning: newdatadictionary(/home/w00tz/public_html/test/lib/adodb/adodb-datadict.inc.php): failed to open stream: No such file or directory in /home/w00tz/public_html/test/lib/adodb/adodb.inc.php on line 3821

Warning: newdatadictionary(): Failed opening '/home/w00tz/public_html/test/lib/adodb/adodb-datadict.inc.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/w00tz/public_html/test/lib/adodb/adodb.inc.php on line 3821

Fatal error: Call to a member function on a non-object in /home/w00tz/public_html/test/install/upgrades/upgrade.20.to.21.php on line 16


So... I'm stuck here. You'll note that CMSMS is still looking in lib/adodb. Should I just rename the adodb_lite dictionary to adodb?

[hotze]

Hi,

I too have upgraded to 1.0.2
the site itself seems to work ok, but a admin login fails.
I already reuploaded the admin directory and it seems that the config.php is ok.

site is www.paulinum.at - german site.

what has to be done to get the admin menu working again?

thanks, martin

[hotze]

as a follow-up: I've put adodb back from an old cmsms version to no avail. Also the debug mode hasn't brought up anything noticable, at least for me. php.ini is set to 20M, still: the admin page is blank, the frontend is OK.

any help is appreciated, I've searched other related postings here, but this brought no workable solution.



tia, hand, martin

[badfrog@w00tz!]

Thanks for the replies hotze, but since your issue seems... well... unrelated to mine, I'm not sure what you hoped to accomplish by hijacking my thread. 

I'm still seeking a solution here... any help would be appreciated. I can give a member of the dev team access to my test installation if that'll help....

[badfrog@w00tz!]

Hello? *waves* Yeah, over here. Been very happy using CMSMS for some time now. Since early betas as a matter of fact. Would like to use the latest version. Having a deuce of a time getting some help with my upgrade problem though.

To review -- upgrading from 0.13 to 1.0.2 doesn't seem to be working. I get errors about a missing adodb-datadict.inc.php file. CMSMS is supposed to be using adodb_lite, per my config file, but it insists on looking in lib/adodb for this file. My admin site, as far as I'm able to test, seems to be fine. My content pages only partially render some of the static content in my template.

I've posted lots of info regarding what's going on and what I've tried to do to fix the problem. I've searched these forums, but haven't found any other posts from people who seem to be having the same issue.  The only help that's been offered here has been either a) incorrect or b) completely unrelated to my problem. I've been nice and not spammed the same question repeatedly. I read the "How to get Answers" sticky and tried to cover everything in my original post.... Am I missing some crucial piece(s) of information in my posts? Am I posting in the wrong forum? Is what I'm trying to do simply not possible? Am I just a complete idiot? What?

Can someone at least tell me why CMSMS is not looking in the correct folder for the adodb_lite files and/or how to make CMSMS look in lib/adodb_lite for includes since that's the library it's supposed to be using? That seems to be the crux of my issue.

Thanks...

[tsw]

[me=tsw]waves back[/me]

sorry to say, but I don't have any idea whats happening with your installation.

the loading happens in include.php lines 95 -> 126 (first checks if full adodb is to be loaded and either loads it or not, then checks is adodb is already loaded and loads lite if not)

I would add some echo "debug: we are loading full adodb here" lines around that code and see whats happening (cheap debug ;)

and maybe you could stop by at #cms @ freenode so we can have a realtime chat (this forum has a java chat which will take you directly to right channel)

and have you tried doing a clean install on the same server? on a different folder and db of course...

hope this helps

[badfrog@w00tz!]

Thanks for the reply and suggestions... I added some echos to include.php starting at line 94.

Code: Select all

f( $config['use_adodb_lite'] == true )
{
	echo "DEBUG -- Supposed to be using adodb_lite";
}
if ($config['use_adodb_lite'] == false || (isset($USE_OLD_ADODB) && $USE_OLD_ADODB == 1))
{
# CMSMS is configured to use full ADOdb
    $full_adodb = cms_join_path(dirname(__FILE__),'lib','adodb','adodb.inc.php');
	echo("DEBUG - Loading adodb from path $full_adodb");
    if (! file_exists($full_adodb))
    {

        # Full ADOdb cannot be found, show a debug error message
        $gCms->errors[] = 'CMS Made Simple is configured to use the full ADOdb Database Abstraction library, but it\'s not in the lib' .DIRECTORY_SEPARATOR. 'adodb directory. Switched back to ADOdb Lite.';
    }
    else
    {
        # Load (full) ADOdb
        require($full_adodb);
        $loaded_adodb = true;
    }
}
if (!$loaded_adodb)
{
    $adodb_light = cms_join_path(dirname(__FILE__),'lib','adodb_lite','adodb.inc.php');
	echo "DEBUG -- Loading adodb_lite from path $adodb_light";
    
}

When I run open the the test site's index page, the debug lines print thusly:

DEBUG -- Supposed to be using adodb_lite
DEBUG -- Loading adodb_lite from path /home/w00tz/public_html/test/lib/adodb_lite/adodb.inc.php

However, when I open install/upgrade.php, this is what prints:
DEBUG -- Supposed to be using adodb_lite
DEBUG - Loading adodb from path /home/w00tz/public_html/test/lib/adodb/adodb.inc.php

It does appear there is some kind of a problem with the upgrade script -- I'd guess $USE_OLD_ADODB is set to 1 in that case. I'll leave it up to someone with more experience with the code than I to decide if this is a bug or feature...

As I mentioned, this is my test site, which I'm trying to upgrade preparatory to upgrading my live site. The test site was created via a backup copy of the live site and database, which is as close to a "fresh install" as I can get. I'll restore the backups again and attempt an upgrade with some additional debug code inserted and post here.

[badfrog@w00tz!]

Just recreated my test site and attempted an upgrade from 0.13 to 1.0.2... Not much changed...

My config.php file contains this line:
$config['use_adodb_lite'] = true;

You'll notice that the upgrade process insists on using adodb, not adodb_lite, and chokes attempting to find the same non-existant file....

/install/upgrade.php
DEBUG -- Supposed to be using adodb_liteDEBUG -- USE_OLD_ADODB = 1DEBUG - Loading adodb from path /home/w00tz/public_html/test/lib/adodb/adodb.inc.php
CMS Banner Logo
Upgrade System
Welcome to the CMS Upgrade System!

In order to upgrade properly, upgrade needs to have write access to your config.php file. This is so any extra settings that have been introduced in this version can be set to their defaults.

Upgrading config.php...[done]

Cleaning cache dirs...[done]

CMS is in need of an upgrade.

You are now running schema version 20 and you need to be upgraded to version 25.

Please click here to complete the upgrade.




/install/upgrade.php?doupgrade=true
DEBUG -- Supposed to be using adodb_liteDEBUG -- USE_OLD_ADODB = 1DEBUG - Loading adodb from path /home/w00tz/public_html/test/lib/adodb/adodb.inc.php
CMS Banner Logo
Upgrade System

Upgrading config.php...[done]

Cleaning cache dirs...[done]

Adding Cross Reference tables...
Warning: newdatadictionary(/home/w00tz/public_html/test/lib/adodb/adodb-datadict.inc.php): failed to open stream: No such file or directory in /home/w00tz/public_html/test/lib/adodb/adodb.inc.php on line 3821

Warning: newdatadictionary(): Failed opening '/home/w00tz/public_html/test/lib/adodb/adodb-datadict.inc.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/w00tz/public_html/test/lib/adodb/adodb.inc.php on line 3821

Fatal error: Call to a member function on a non-object in /home/w00tz/public_html/test/install/upgrades/upgrade.20.to.21.php on line 16

[Debon]

Badforg for what its worth - I am also running 0.13 at http://www.kareempanton.net and I believe it is much safer to upgrade in stages e.g. from 0.13 you should first upgrade to 1.0 then apply whatever upgrade is available to take it from 1.0 to the next release and so on. When they wrote the upgrade to 1.02 it may have been assumed that persons would be upgrading from 1.01 but since you are coming from as far down as 0.13, hence the problems. Just my humble opinion.

[badfrog@w00tz!]

OK... I'll try going 0.13->1.0->1.02... at a point where trying anything sounds good.

I figured that since there are files in the install/upgrade path with names like upgrade.13.to.14.php and upgrade.14.to.15.php and so on that this wouldn't cause a problem.

[hotze]

Thanks for the replies hotze, but since your issue seems... well... unrelated to mine, I'm not sure what you hoped to accomplish by hijacking my thread. 

I'm still seeking a solution here... any help would be appreciated. I can give a member of the dev team access to my test installation if that'll help....

sorry if you felt this was hijacking. It seemed that I had (!) similar problems. I found great help on the Chat.
As a follow-up I promised to add the solution: Problem was a modul (namely the FormFeedback). After renaming this module everything worked like a charm.

hth, martin

[Debon]

OK... I'll try going 0.13->1.0->1.02... at a point where trying anything sounds good.

Badfrog, sorry to be doing this to you but I believe the order should be 0.13 -> 1.0 -> 1.01 -> 1.02. Hope this helps.