ATutor

Learning Management Tools







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


Stuck in Installer Loop


  • 2004-02-19 20:52:45

    Stuck in Installer Loop

    I just installed the new ATutor 1.3.2 and it all went well, tables installedall permissions ok I get to the finish page with the login link, I click the login and it comes back and gives me the install page again:

    ATutor does not appear to be installed. Continue on to the installation.

    I have checked the database and all tables are installed. No error messages, just can't get out of the install loop.

  • 2004-02-19 22:00:01

    More Info

    Can't reproduce the problem.

    see:
    http://www.atutor.ca/view/7/149/1.html

  • 2004-02-20 00:23:52

    install loop

    What does the index or login file look for to determine if ATutor is installed or not.

    I notice there is a conditional at the very end of the config file that has something to do with the install. I tried setting it to true but it didn't have an effect.

    I seem to remember having this problem on another installation but not sure how it was resolved.

  • 2004-02-20 08:51:24

    Help us Help you

    As I suggested in my previous message...

  • 2004-02-20 17:40:46

    Comment vitals

    Try commenting out lines 32 to 36 in include/vital.inc.php.

    -----

    Yes, it is set to true:

    /* DO NOT ALTER THIS LAST LINE */
    define('AT_INSTALL', true);


    On Feb 20, 2004, at 5:18 PM, Greg Gay wrote:

    > is the last line of config.inc.php set to "true"
    > eg
    > define('AT_INSTALL', true);

  • 2004-02-20 18:14:20

    puzzled but digging deeper

    I commented out the conditional in vitals and now it goes to login.php and gives me a cannot connect to database.

    I have checked the database with phpMyAdmin and it is totally populated, and given the database login info requested during installation. I also checked the config file and it has the appropriate db login info.

  • 2004-02-20 18:38:11

    Server Config?

    This would indicate that the db info is not correct, but you should not have been able to get through the install if that was the case.


    Do you have root access, or is this a hosted system? Show the problem to your ISP if its hosted. Perhaps your MySQL account is not configured properly. Perhaps a firewall...

    Post here an exact copy of any errors or messages you receive.

  • 2004-02-20 19:03:01

    Database checks out but...

    the exact error on the login page now is:

    "Unable to connect to db."

    I just took a good look into the database that was set up during installation. It contains 30 tables and has the instructor account I entered during setup.

    I am on a hosted server but I have close to 50 databases on it, and have never had a problem creating databases, adding deleting or editing tables etc on 100 or more scripts that access them. When I have a db connect error I can usually track it down to a typo in the config file. This is not the case here as the connect info did in fact set up the tables properly.

    I do remember a similar problem with an earlier version of ATutor, but cannot recall what combination of late night jiggling cured the problem. This time I'll take notes ;-)

  • 2004-02-21 23:08:50

    Same problem on another server

    Wierder still, I just installed the latest release of ATutor on an entirely different server and have the same install loop problem.

    Database tables get installed fine, Admin and user accounts get set up, but when I click the login link on the last page of the install script, it sends me to the not installed error page with a link to start the installation.

    I am starting to think I am just not destined to use this great script. Any other ideas what could be going on? I will send you the phpinfo page url for this second server by email.

  • 2004-02-23 10:45:43

    Same problem on another server

    There is a parse error in your config.inc.php file.

    Check to make sure that you don't have any single quotes (') or double quotes (") that are not escaped (/').

    if you have a quote in your db password then you will end up with something like:
    define('DB_PASSWORD', 'my'spass');

    which will result in a parse error since the first single quote is not escaped.

    ( i was just using "DB_PASSWORD" as an example, it could be the problem with any of the options, so double check them all).

    .joel