ATutor

Learning Management Tools


  1. Home



Pages:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15


Fatal error after upgrade from 153 to 161pl1



  • 2008-11-20 17:56:51

    Fatal error after upgrade from 153 to 161pl1

    Hello.

    I downloaded and upgraded successfully. When I clicked on the Log in link after the upgrade was finished I get:

    "Fatal error: Call to a member function printErrors() on a non-object in .../public_html/training/include/phpCache/phpCache.inc.php on line 527.

    I tested the login using the old atutor backup on my browser and it resolves to the right page.

    Should I restore the old database backup and try it again? Any other suggestions?

    Thanks in advance.

    If you are asking for help, provide lots of detail so problems can be reproduced.

    Things to describe:
    operating system - Linux
    version of ATutor - 1.5.3.3 upgraded to 1.61-pl1
    versions of php - 5.2.5
    version of mysql - 5.0.45-community-
    log
    webserver & version -
    apache ver 1.3.37 (Unix)
    shared hosting - Siteground.com
    Changes to default settings - none
    Web browser being used - IE 7
    ...and anything else relevant -


  • 2008-11-20 18:07:04

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    Perhaps, don't reload any pages during upgrade.


  • 2008-11-21 06:04:05

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    webmark, there could be a whole lot of reasons.

    If you've backed up, then yes, the easiest thing you can do is to restore the backup and try once (few times?) more -- upgrade paths between versions so long apart could be undertested and tricky.


  • 2008-11-28 23:33:44

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    Thank you for your replies. I inherited this site without documentation and it is old and unstable. I think he had tweaked several things because it is integrated with Joomla ecommerce...
    I have tried the upgrade several times with no luck.
    Should I just go to a fresh install instead of trying to upgrade? The site has about 300 active students with current classes in progress. Is it possible to upload the db from 1.53 into a fresh 1.61?

    Thanks again.


  • 2008-11-29 08:49:53

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    I suppose it is possible to copy a 1.5.3 database into 1.6.1, but it will take some care. You probably should not try this while courses are going on. Wait for some down time, when you can afford to have your courses down for a while.

    The upgrade from 1.5.3 should work fine, but if there have been manual changes to the db, that may no longer be the case.

    I might suggest waiting until 1.6.2, a couple weeks away (Dec 10 +/-), and try upgrading then. I'll make a note trying the an upgrade from 1.5.3 to 1.6.2 before the release to be sure it works okay.


  • 2008-11-29 09:06:10

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    Thanks Greg. I will wait to 1.62 to upgrade. Your help is much appreciated.


  • 2008-11-29 12:28:15

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    Murphy's law... the db backup is corrupted (all 3 copies that I made). I have an older backup that works but it is 3 months old. My host restored the old db as a new one named _test and left the upgraded _atutor db also. The site now has the upgraded db and another db with the 3 mo. old data.

    I restored the old atutor (1.53) directory and deleted the upgraded one. The restored old atutor works now. My questions are, does it make a difference to atutor what the db name is, and is it writing in the _test db or the upgraded _atutor db?

    I'm really sorry for my ignorance, I am new to this and have to take it over and fix it for the company.

    Many thanks.


  • 2008-11-29 12:44:42

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    It does not matter what the db is called. Adjust it in the include/config.inc.php file.

    It will be read from whichever db is listed in the file.


  • 2008-12-01 13:20:12

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    Hi,

    I am going to give a test on this. You have specified the ATutor version as both 1.5.3.3 and 1.5.3, can you tell me which one is it exactly please?


    Thanks,

    Harris


  • 2008-12-01 14:27:42

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    Hi Harris.

    The version that is listed when I log in as admin is 1.5.3.3

    One other question... can I continue to use the upgraded database with the old files that I restored?


    Thanks,




    If you are asking for help, provide lots of detail so problems can be reproduced.

    Things to describe:
    Operating system ATutor is installed on -
    ATutor version -
    Patch #s applied -
    ATutor theme name -
    PHP version -
    MySQL version -
    Webserver & version -
    Copies of error messages -
    Changes to default settings -
    Web browser being used -
    ...and anything else relevant -


  • 2008-12-01 15:37:50

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    Do you mean old ATutor files (1.5.3.3) or your content files? The latter is fine. 1.5.3.3 ATutor files with 1.6.1 database may generate unwanted database entries or even triggers unwanted errors. This is due some of the changes within the database structure through out 1.5.3.3 to 1.6.1.

    [reply][b]In reply to:[/b]
    One other question... can I continue to use the upgraded database with the old files that I restored?..
    [op]forums/view.php?fid=7;pid=15774;page=1#15849[/op][/reply]


  • 2008-12-01 16:13:32

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    I have upgrading 1.5.3.3 to 1.6.1 with a 1.4.3 backup file successfully.

    Looking at your error, it could very well be caused by a customization you made to your system; it also suggests to me that the $msg variable has not been declared somewhere in your code, or if it has and is inside a function, make sure it is declared as "global $msg". You can try debugging this in your system by searching all "print_errors()" under your ATutor installation, and just look though them and see which of them is missing the variable $msg.

    Hope this helps.


  • 2008-12-01 16:30:11

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    Thank you harris. This site was created by a person who is not with the company any longer and the site was integrated to joomla with the bridge. There were errors everywhere and I'm not familiar with the code.

    I have a restored 1.5.3.3 content folder and a database that was upgraded in the 1.6.1 attempt. I also have an old 1.5.3.3 database which is 3 months old. The current backup I did prior to upgrade is corrupted.

    I was hoping to be able to upgrade without customizations and just use both parts of the site individually but the site courses fees are collected in the Joomla site and somehow were written to the atutor site dynamically. My guess is there are customizations there too. I am not able to log in to atutor site as a student or anything but admin.

    I'm thinking of buying the atutor support ticket option to see if an expert could restore this back to where it was or help me figure this out. What do you think?

    Thank you again.


  • 2008-12-02 13:44:10

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    Thank you so much for all your help.

    I have successfully restored the site to the old 1.5.3.3 version of atutor but I found that it is integrated using a cusomized "enroll_mambo.php" which is connecting to the atutor db which is now upgrded to 1.6.1pl but I have modified the atutor config to connect to the old 1.5.3.3 db.

    Everything seems to be working, I can manully enroll the students from joomla to atutor. I'm guessing, since the modified enroll is connected to the 'wrong' db, that all the student's progress will now be in that db. Should I edit all the customized files to connect to the 1.5.3.3 db or can I later just export the data and import it to the db once I upgrade to 1.6.2.

    Any suggestions are greatly appreciated.


  • 2008-12-03 09:03:24

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    You can copy data over, but it may not be an easy task.

    The upgrade to 1.6.2 should should be fine from 1.5.3.3. But, if you've been using a 1.6.1 db for a while before reverting, you are likely going to loose that data. I would not want to be faced with the task of trying to merge data from it, into the 1.5.3.3 to 1.6.2 upgrade.


  • 2008-12-03 22:18:36

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    Greg, When I convert I want to use atutor stand alone, without the integration and use the paypal module for payment.

    I'm going to do a fresh install of atutor on another account to learn the system as it should be used.

    How can I tell if the other admin has made db changes to this old version ?


  • 2008-12-04 08:26:11

    Re: Fatal error after upgrade from 1.53 to 1.61-pl1

    Look at the administrator log to see what admins have been doing. In the admin area

    User>Administrators>Administrator Activity

    [reply][b]In reply to:[/b]
    Greg, When I convert I want to use atutor stand alone, without the integration and use the paypal module for payment.

    I'm going to do a fresh install of atutor on another account to learn the sys...
    [op]forums/view.php?fid=7;pid=15774;page=2#15878[/op][/reply]