ATutor

Learning Management Tools


  1. Home



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


Im back but



  • 2015-02-26 08:06:43

    Im back but

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

    Things to describe:
    Operating system ATutor is installed on - godaddy cpanel all very up to date
    ATutor version -2.1.1
    Patch #s applied - all but captcha
    ATutor theme name - default
    PHP version - 5 something
    MySQL version - 4 somethin
    Webserver & version - apache 2
    Copies of error messages -
    Changes to default settings - no and yes
    Web browser being used - safari and chrome
    ...and anything else relevant -

    After being unable to resolve the mysql problem in 2.2, and trying several other LCMS packages, I came to the conclusion that they all had more serious negatives than ATutor does,
    and reinstalled a fresh download of 2.1.1, Now the problems are even worse.

    It can't access my old content sub-folders, nor is it creating new subfolders in the content folder even when set to 777. So beyond the few default pages, nothing else appears. After I create the course pages I get these blanks with isensei14 and isensei15 appearing on the tabs in my browser. Those aren't even the course or subfolder numbers. I can't figure out what is going on. I reinstalled several times today.

    I noticed the message in the config file regarding the content folders and a toggle that needed to be donein the install content folder, so I did that, and set the folders to 777, and loaded up fesh copies of the folder, and basically spent most of the day trying to get the site to install properly. It still isn't working. I also installed a AContent and hope I can make it work with that. Can I export the pages without the quizes? It ovewrites the question categories, and leaves me with one long list.

    Can you recommend anything before I tear my wife's hair out? I can't get a purchase on mine.


  • 2015-02-26 09:21:53

    Re: I'm back, but!

    First be sure all the system requirements are met:
    http://www.atutor.ca/atutor/docs/requirements.php

    The content folder needs to be set to "chmod -R 777" to recursively set the write permission. This allows the Web server to write to that folder, but also means the user that own the rest of ATutor can't modify files that the web server user has uploaded. Only the root user typically can make changes in the content directory.

    It sounds like you have something else going on, but I can't put my finger on it. Probably a permissions problem.

    Perhaps review the install instructions one more time to be sure you have not missed anything.
    http://atutor.ca/atutor/docs/installation.php


  • 2015-02-26 17:10:44

    Re: I'm back, but!

    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 -
    Thanks Greg,

    I have never had root access to godaddy and never needed it. I have reinstalled dozens of times without issue. It works just fine at home on MAMP without chmod 777. It must be a problem with godaddy. And they always want to charge me to fix it.


  • 2015-02-26 17:24:51

    Re: I'm back, but!

    A quick question, what should I find in the content subfolders? The most the my ATutor ones have in them is a one byte index file. But in the AContent subfolders there is a another subfolder with file names in it.

    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 -


  • 2015-02-26 17:56:24

    Re: I'm back, but!

    Godaddy I would guess is a linuz system, in which case you need to explicitely make the content directory writable. On MAMP systems you don't always need to.

    Sub folders should include a numbered folder for each course, and a bunch of others for things like backups, cache, chat, etc. for each module that needs a writable directory. And a index.html file with a dot in it, which prevents access to the directory contents list.


  • 2015-02-26 19:21:57

    Re: I'm back, but!

    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 -

    I dug into the php at godaddy. It is 5.4 native but I can set 5.5. It doesn't have curl and zlib. Are they part of php or perl or something else I need to look at?

    There is lots of stuff in the default content folders and the course folders only have index.php.


  • 2015-02-27 09:17:21

    Re: I'm back, but!

    Good catch! its now in the bug tracker
    http://atutor.ca/atutor/mantis/view.php?id=5573

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

    The password maker on cpanel demands special characters which the installer didn't like. Here is the message from the genius who fixed it for me. Might be something you could add to fix it for others.

    This is just a quick follow-up regarding your recently reported issue.

    While we do not provide any direct coding support, I did go a bit above and beyond to attempt to resolve your issue, and I believe I have figured out the problem.

    Looking at your website's files, I was able to see that the /public_html/install/install.php file has simple PHP require statements that include the "steps" for the installation at /public_html/install/includes/stepx.php (where "x" is the step number). So that indicated to me that the issue was happening in the step2.php file.

    To get the server to specifically display why the POST request was generating a 500 Internal Server Error on step 2, I added the following code to the top of the step2.php file:
    error_reporting(E_ALL);
    ini_set('display_errors', 1);

    After doing that I received the following errors when submitting on step 2:

    Warning: mysqli::mysqli(): (28000/1045): Access denied for user 'isensei'@'localhost' (using password: YES) in /home/tsc2357/public_html/include/lib/mysql_connect.inc.php on line 18

    Warning: mysqli::set_charset(): Couldn't fetch mysqli in /home/tsc2357/public_html/include/lib/mysql_connect.inc.php on line 20

    Warning: mysqli::query(): Couldn't fetch mysqli in /home/tsc2357/public_html/include/lib/mysql_connect.inc.php on line 305

    Fatal error: Call to a member function fetch_assoc() on a non-object in /home/tsc2357/public_html/include/lib/mysql_connect.inc.php on line 306

    The error message was odd, because your database "isensei" is up, and the "isensei" user is configured to access this database.

    On closer inspection, however, the issue was caused by the password on the database user "isensei". The special characters in it were acting as "escape characters"; and because the application's code was not scripted to check for them, this prevented the attempted database connection from completing successfully.

    To fix this issue I simple generated a new password with only letters and numbers in it. After doing that I was able to get through step 2 just fine.

    I recommend resetting the password again, and avoiding any special characters that may act as escape characters. This will ensure that your application's mysqli functions/methods can successfully make the connection to the database.

    Hopefully you should have no further issue going through the rest of the steps.

    Please let us know if we can assist you in any other way.