Note: You are currently viewing documentation for Moodle 2.0. Up-to-date documentation for the latest stable version is available here: Installation FAQ.

Talk:Installation FAQ: Difference between revisions

From MoodleDocs
(Added section on debugging before config.php created)
Line 29: Line 29:
   
   
--[[User:John Walling|John Walling]] 14:56, 11 May 2007 (CDT)
--[[User:John Walling|John Walling]] 14:56, 11 May 2007 (CDT)
== PHP Debugging Configuration Confusion ==
The FAQ about getting a blank page during installation refers the reader to the FAQ about checking your error logs, which tells him/her to add ini_set calls to config.php if using Moodle 1.7 or higher. Problem is, during installation ''there is no config.php file''! This leaves the reader in a quandry, and so the instructions should be clarified. See http://moodle.org/mod/forum/discuss.php?d=87473
--[[User:Richard Enison|Richard Enison]] 08:00, 4 January 2008 (CST)

Revision as of 14:00, 4 January 2008

I just added a bunch of questions/answers to the generic FAQ page, and then looked at this to see how it was done (backwards, I know). Clicking on the item jumps you down to the question... but should we add a link to jump back to the top? -- D.I. 29jan06


Someone said, under : My pages show fatal errors such as : Parse error, call to undefined function: get_string()

"You may also be running a php script which uses short open tags, e.g. instead of <?PHP ?> it uses <? ?>. Either replace short tags with conventional ones, or set this line in php.ini:

" short_open_tag = On"

However, this should never be necessary with Moodle code. If you find any short tags anywhere, file a bug in the bug tracker against the affected code. There are currenly none of these abominations anywhere in the Moodle core code.Tim Hunt 01:19, 26 July 2006 (WST)

--- Agreed. Such an "abomination" should not be in Moodle core code but the person who deleted it doesn't appreciate the point. This comment was added to help those who are having problems with code which is not part of Moodle core, e.g some of the third party blocks which are mentioned frequently in forums. There is no reason, IMHO, why fellow Moodlers in such a predicament would not turn to this FAQ for help. - Ken Wilson 25 July 06

--- Sorry, my mistake. I had not reallised that this actually happened with contrib modules. I'll reinstate the that bit (but keep my point about reporting the problem so it can be fixed).Tim Hunt 01:19, 26 July 2006 (WST)

Memory limit limitations

Each method of increasing memory limit has limitations.

.htaccess
directive php_value memory_limit may be disabled by the host
php.ini
no root access

There is a third way which may or may not work:

php function ini_set
Example: ini_set("memory_limit","24M");
It will not work if phpinfo() does not show Configure Command '--enable-memory-limit'
see http://us.php.net/manual/en/ini.core.php#ini.memory-limit

On my host, none of the three methods will work. I am limited to 8M memory per PHP session. I am able run the basic installation. I haven't seen the dreaded error "Allowed memory size of Xxx bytes exhausted" but I expect it at some point.

--John Walling 14:56, 11 May 2007 (CDT)

PHP Debugging Configuration Confusion

The FAQ about getting a blank page during installation refers the reader to the FAQ about checking your error logs, which tells him/her to add ini_set calls to config.php if using Moodle 1.7 or higher. Problem is, during installation there is no config.php file! This leaves the reader in a quandry, and so the instructions should be clarified. See http://moodle.org/mod/forum/discuss.php?d=87473

--Richard Enison 08:00, 4 January 2008 (CST)