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
No edit summary
 
No edit summary
Line 1: Line 1:
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
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 [http://moodle.org/bugs/ bug tracker] against the affected code. There are currenly none of these abominations anywhere in the Moodle core code.

Revision as of 21:33, 24 July 2006

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.