Edumy Demo Installation Troubleshooting

Updated

If you're having difficulty installing the Edumy Demo Installation package, please use this guide as a reference point for where things may have gone wrong.

First note: The Demo Installation package works correctly and is tested frequently. If the Demo Installation package has not worked, it is very likely that you have not followed the steps from the Edumy documentation file accurately. Please note that the documentation instructions must be followed 100% correctly and "as-is". Do not attempt to install the Demo Installation in a different way, because it will not work.

 

1. Can't find data record in database table course_categories.

If you receive this error message when you try to access your Moodle frontpage after installing the Demo Installation, it means that you have not followed the documentation correctly.

This error means that you have tried to install Moodle twice — once via the standard Moodle installer, and again via the database import via phpMyAdmin. You should not run the standard Moodle installer to install the Edumy Demo Installation package. Instead, you should follow the "Demo Installation" instructions from the documentation in your download package.

To resolve this issue, please follow the steps below:

STEP #1: Drop all tables in your Moodle database.

STEP #2: Re-import the "cocoon_edumy.sql" file from your download package.

STEP #3: Delete the demo "moodledata" directory from your server, and re-upload it from your download package. (This is important because Moodle caches error messages, so even after fixing the database you may still see errors if you don't delete and re-upload the moodledata directory).

STEP #4: Once the steps above are complete, you may re-visit your Moodle installation via the web browser. The issue should now be resolved, and you can continue the installation process by logging into your admin account using the login details from the documentation file in your download package.

2. CFG->dataroot is not accessible! Exiting

This error indicates that your moodledata directory is not accessible by Apache. Please ensure that:

  1. You have specified the correct server path to the moodledata directory in your config.php file (the path must be an absolute/full server path, not a path relative to the Moodle root directory).
  2. The Apache user has full read-write access privileges to the moodledata directory.
  3. The Apache user is the owner of the moodledata directory on the server.
  4. If you have first uploaded the moodledata.zip file, instead of first extracting and then uploading, please ensure that your server has not placed a "moodledata" directory inside another "moodledata" directory. i.e. If extracting a ZIP on the server itself, the server may have extracted to: /path/to/moodledata/moodledata, instead of /path/to/moodledata. In this case, move the inner moodledata directory up a level, or specify the moodledata directory as /path/to/moodledata/moodledata in your config.php file on the CFG->dataroot line.

3. index.php returns Internal Server Error 500, but other pages work

This is an issue we occasionally see on some web hosts, when uploading the files.zip folder and then extracting it. The root index.php becomes a little tangled. To resolve:

  1. Find the following file in the Edumy Download package: Demo Installation > files > index.php
  2. Replace the <MoodleRoot>/index.php file one on the server with the one from the download package manually.

This should resolve the issue.

Fatal error: require(): Failed opening required '../config.php' (include_path='.:/usr/local/php73/pear') in index.php on line 27

Please follow the same steps as step 3 above, and the issue should resolve.

Additional Notes

  • As per Moodle's official guidelines on the config.php file, your CFG->wwwroot should not include a trailing slash.
  • Your CFG->dataroot should be the full absolute server path to the moodledata directory that you've uploaded to your server.
  • The moodledata directory should reside outside of the public web root.
  • If your site uses SSL, your CFG->wwwroot should reflect this, with https rather than http.

     

If you still require help

Our dedicated support team work 7 days per week, and are available to assist you with installation if required.

Please reach out to us via support ticket, and we will be very happy to help!