I still am having no luck with this. Does anyone know why I am getting this when I runn the MOODLE_15_STABLE upgrade? I even tried deleting the moodle directory and database and redownloading it. I get the same result.
I am going to try MOODLE_152.
Any help for would be greatly appreciated.
Eric
Martin,
I don't have any unusal errors. I tried upgrading a totally separate installation and I get the same problem.
[Fri Jul 22 12:26:16 2005] [error] [client 67.78.234.173] File does not exist: /usr/home/moodlecoolg/moodle/favicon.ico
That's all I get for that install in the errors.
1/ check permissions of your moodledata directory
2/ add $CFG->debug = 15; to config.php
3/ comment out following from lib/setup.php
Then you should get at least some error messages, if not try adding echo("grrr"); to various places in setup.php...
skodak
2/ add $CFG->debug = 15; to config.php
3/ comment out following from lib/setup.php
error_reporting(0); // Hide errors
Then you should get at least some error messages, if not try adding echo("grrr"); to various places in setup.php...
skodak
Petr,
I followed your suggested steps above and I get the following WARNING:
Notice: Undefined property: version in /usr/home/moodlefiaa/moodle/admin/index.php on line 24
which leads to (the best I can tell):
/// This is a Moodle 1.5 hack ONLY to fix accidental bad versions from version.php
/// Do not copy this code into HEAD
if ($CFG->version == '2005072100') {
set_config('version', 2005060221);
}
There are no other errors. Since the install seems to hang up after the Scorm additions, I am thinking this is database related. Is there a .sql containing all database creations that I can manually run? I just need to get over the db creation hurdle I think?
Thank you,
Eric
This has happened to me in the past when I have had non-standard blocks or modules in my moodle installation. Was this the case? Try removing them one at a time to see which one is causing the conflict.
For example, I recently upgraded my book module, and left the old book module folder in there (called "book_old") and when I forgot to delete it, I was getting the blank admin page. As soon as I deleted it, everything was back to normal.
HTH,
Tim.
For example, I recently upgraded my book module, and left the old book module folder in there (called "book_old") and when I forgot to delete it, I was getting the blank admin page. As soon as I deleted it, everything was back to normal.
HTH,
Tim.