MoodleDocs - User contributions [en]

PHP error logs

2016-04-07T11:11:02Z

ColinFraser:

PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command.

== How to enable and check PHP error logs==
PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command.
* '''Using the php.ini file''': The log settings are contained in the php.ini file stored on the server. If you don't know where that is, edit your Moodle ''config.php'' and add the following as the second line

phpinfo();

:then reload the web page. Look for the entry '''Configuration File (php.ini) Path'''.

:When you have located php.ini open it in your favorite text editor. Find the '''Error handling and logging''' section of the php.ini file. Make sure that both '''display_errors = On''', '''display_startup_errors = On''' and '''log_errors = On''' are present and uncommented. Check the value of '''error_log''' - this tells you the location of the file errors are logged to. If it is commented out then errors will be sent to the web server error log file. Remember, if you make any changes to this file you will need to restart the web server (or just reboot the server).

* '''Using ini_set commands''': If you are using Moodle 1.7 or higher, the previous steps are not enough. In those versions error logging parameters are dependant on certain administrative settings that you specify in the debugging section. The problem is that if you can't access the administrative pages, you can't set the debugging options. So the only way to modify them is by adding the following lines to your config.php file, just before the last line (the one containing a single'?>' only):

ini_set ('display_errors', 'on');
ini_set ('log_errors', 'on');
ini_set ('display_startup_errors', 'on');
ini_set ('error_reporting', E_ALL);
$CFG->debug = DEBUG_ALL;

:This will enable the same settings specified above even if Moodle sets them otherwise.
:'''Important''': Remember to put them just before the last line of config.php.

==Error Logs==

The default settings of the PHP Error Log file varies from OS to OS. The location of the error log file itself can be set manually in the php.ini file. On a Windows server, in IIS, it may be something like "'error_log = C:\log_files\php_errors.log'" in Linux it may be a value of "'/var/log/php_errors.log'". The php_errors.log file may be required to be manually created, which would mean that the ownership and rw permissions will need to be set accordingly.

==See also==
*[[:en:Installing Moodle|Installing Moodle]]
*[[:en:Installation FAQ|Installation FAQ]]

Future

2011-04-16T12:36:31Z

ColinFraser: /* What happens if Martin gets eaten by a kangaroo? */

{{About Moodle}}

==Development==

Moodle development is increasingly influenced by our community of developers and users.

Your [[Credits|contributions]] in the form of ideas, code, feedback and promotion are all very welcome - see the [[Development:Developer documentation|Developer documentation]] and the [http://moodle.org/help community forums] for more details on our software development life cycle. A dynamic database of proposed features and their status can be found at [http://tracker.moodle.org/ tracker.moodle.org]. You can also pay to have certain features developed sooner - see [http://moodle.com/development/ moodle.com/development] for information and a quote.

For more detailed information, see our [[Roadmap]] for developers.

==Moodle Project==

Naturally people like to consider risks when committing something as important as education to a particular piece of software. This is particularly so with open source where they aren't paying for anything.

Here are answers to some of the frequent questions that we hear about this.

===What happens if Company X offers to buy Moodle?===

# The copyrights to Moodle software can never be "sold" like they can for proprietary software. All our code is completely open source. The copyrights belong to hundreds of authors and they would ALL need to agree to any change in the license. Even if that happened, it would only apply to future code - all existing versions would remain under the existing GPL license and our large and very capable community of developers would simply fork from there and continue using and developing the GPL version.
# The core company Moodle Pty Ltd has no interest in selling themselves, at any price. Martin Dougiamas has already dismissed cash offers of US$20 million for the company because he knows any such move would only damage the trust of the community and slow down growth. Note that Moodle Pty Ltd also has over 50 Moodle Partner companies worldwide who depend on Moodle and they would also all need to agree! Even if this doesn't reassure you enough, please remember that EVEN if the company was sold the software would not be affected - the Moodle user community (including thousands of large Universities and companies) would organise new management among themselves and continue.

===What happens if Martin gets eaten by a kangaroo?===

# Moodle is well beyond being driven by any single person. The company Moodle Pty Ltd has a stable foundation now, and would continue to be managed as a viable business.
# Martin has been progressively delegating more and more of his roles and there are enough managers and enough processes in the project now to continue without him.
# Kangaroos are herbivores. :)
## Except for the Kalangadoo Kangaroo, but Martin is extremely unlikely to visit Kalangadoo.

[[pt:Futuro do Moodle]]
[[es:Futuro]]
[[nl:Toekomst]]
[[de:Zukunft]]
[[fr:Futur]]
[[ja:未来]]
[[de:Zukunft]]

Upgrading to Moodle 2.0

2010-12-30T13:18:09Z

ColinFraser: /* Known and Discovered Issues */

{{Moodle 2.0}}When upgrading to Moodle 2.0, you must have Moodle 1.9 or later. if you are using an earlier version of Moodle (eg 1.8.x) then you need to upgrade to Moodle 1.9.x first.

We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.

==System requirements==

* PHP must be '''5.2.8 or later'''
* Databases should be one of the following:
** MySQL 5.0.25 or later (InnoDB storage engine highly recommended)
** PostgreSQL 8.3 or later
** Oracle 10.2 or later
** MS SQL 2005 or later
* Any standards-supporting browser from the past few years, for example:
** Firefox 3 or later
** Safari 3 or later
** Google Chrome 4 or later
** Opera 9 or later
** MS Internet Explorer 7 or later (Even [http://googleenterprise.blogspot.com/2010/01/modern-browsers-for-modern-applications.html Google does not support IE6 any more])

==Before upgrading please... ==
* Always check your site to make sure it meets all system requirements for 2.0 in ''Administration > Server > [[Environment]]''
* '''Do a full database backup!'''
* Remember to purge PHP cache if using any PHP accelerator

==Now upgrade==

Once you have satisfied the requirements for Moodle 2.0, follow the instructions on the [[Upgrading|upgrading]] page.

Moodle 2.0 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

Note, if you get a strange error about 'handling of PHP float numbers', please see [[Installation_FAQ#Moodle_claims_PHP_float_handling_is_not_compatible|this FAQ entry]].

== Verify the upgrade (optional) ==
If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].

== Known and Discovered Issues ==
Many people are concerned that their install/upgrade is reporting the php extension '''intl''' is not installed or available. The intl.dll file is available in later releases of PHP but many hosts may not have a later release. To remedy this problem, discuss with your host the issue you are having and inform them that the problem is easy fixed by either upgrading their php to a newer version or to download the intl.dll and copy it to the php/ext folder. Add to the php.ini file the line:
extension=php_intl.dll
in the ''Dynamic Extensions'' section of the file. The problem should then be resolved.

Moodle 2.0 also requires the use of the PHP zip extension. For most installs this is not an issue, but for some, all it needs is for the line:
extension=php_zip.dll
in the ''Dynamic Extensions'' section to be uncommented.

==See also==

*[[Moodle 2.0 release notes]]

*[[:Category:Moodle 2.0]]

[[Category:Installation]]

[[de:Auf Moodle 2.0 aktualisieren]]
[[fr:Mise à jour à Moodle 2.0]]

Upgrading to Moodle 2.0

2010-12-30T13:17:34Z

ColinFraser: /* Known and Discovered Issues */

{{Moodle 2.0}}When upgrading to Moodle 2.0, you must have Moodle 1.9 or later. if you are using an earlier version of Moodle (eg 1.8.x) then you need to upgrade to Moodle 1.9.x first.

We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.

==System requirements==

* PHP must be '''5.2.8 or later'''
* Databases should be one of the following:
** MySQL 5.0.25 or later (InnoDB storage engine highly recommended)
** PostgreSQL 8.3 or later
** Oracle 10.2 or later
** MS SQL 2005 or later
* Any standards-supporting browser from the past few years, for example:
** Firefox 3 or later
** Safari 3 or later
** Google Chrome 4 or later
** Opera 9 or later
** MS Internet Explorer 7 or later (Even [http://googleenterprise.blogspot.com/2010/01/modern-browsers-for-modern-applications.html Google does not support IE6 any more])

==Before upgrading please... ==
* Always check your site to make sure it meets all system requirements for 2.0 in ''Administration > Server > [[Environment]]''
* '''Do a full database backup!'''
* Remember to purge PHP cache if using any PHP accelerator

==Now upgrade==

Once you have satisfied the requirements for Moodle 2.0, follow the instructions on the [[Upgrading|upgrading]] page.

Moodle 2.0 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

Note, if you get a strange error about 'handling of PHP float numbers', please see [[Installation_FAQ#Moodle_claims_PHP_float_handling_is_not_compatible|this FAQ entry]].

== Verify the upgrade (optional) ==
If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].

== Known and Discovered Issues ==
Many people are concerned that their install/upgrade is reporting the php extension '''intl''' is not installed or available. The intl.dll file is available in later releases of PHP but many hosts may not have a later release. To remedy this problem, discuss with your host the issue you are having and inform them that the problem is easy fixed by either upgrading their php to a newer version or to download the intl.dll and copy it to the php/ext folder. Add to the php.ini file the line:
extension=php_intl.dll
in the ''Dynamic Extensions'' section of the file. The problem should then be resolved.

Moodle 2.0 also requires the use of the PHP zip extension. For most installs this is not an issue, but for some, all it needs to for the line:
extension=php_zip.dll
in the ''Dynamic Extensions'' section to be uncommented.

==See also==

*[[Moodle 2.0 release notes]]

*[[:Category:Moodle 2.0]]

[[Category:Installation]]

[[de:Auf Moodle 2.0 aktualisieren]]
[[fr:Mise à jour à Moodle 2.0]]

Upgrading to Moodle 2.0

2010-12-30T13:16:11Z

ColinFraser: /* Known and Discovered Issues */

{{Moodle 2.0}}When upgrading to Moodle 2.0, you must have Moodle 1.9 or later. if you are using an earlier version of Moodle (eg 1.8.x) then you need to upgrade to Moodle 1.9.x first.

We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.

==System requirements==

* PHP must be '''5.2.8 or later'''
* Databases should be one of the following:
** MySQL 5.0.25 or later (InnoDB storage engine highly recommended)
** PostgreSQL 8.3 or later
** Oracle 10.2 or later
** MS SQL 2005 or later
* Any standards-supporting browser from the past few years, for example:
** Firefox 3 or later
** Safari 3 or later
** Google Chrome 4 or later
** Opera 9 or later
** MS Internet Explorer 7 or later (Even [http://googleenterprise.blogspot.com/2010/01/modern-browsers-for-modern-applications.html Google does not support IE6 any more])

==Before upgrading please... ==
* Always check your site to make sure it meets all system requirements for 2.0 in ''Administration > Server > [[Environment]]''
* '''Do a full database backup!'''
* Remember to purge PHP cache if using any PHP accelerator

==Now upgrade==

Once you have satisfied the requirements for Moodle 2.0, follow the instructions on the [[Upgrading|upgrading]] page.

Moodle 2.0 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

Note, if you get a strange error about 'handling of PHP float numbers', please see [[Installation_FAQ#Moodle_claims_PHP_float_handling_is_not_compatible|this FAQ entry]].

== Verify the upgrade (optional) ==
If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].

== Known and Discovered Issues ==
Many people are reporting that their install/upgrade is reporting that php extension '''intl''' is not installed or available. The intl.dll file is available in later releases of PHP but many hosts may not have a later release. To remedy this problem, discuss with your host the issue you are having and inform them that the problem is easy fixed by either upgrading their php to a newer version or to download the intl.dll and copy it to the php/ext folder. Add to the php.ini file the line:
extension=php_intl.dll
in the ''Dynamic Extensions'' section of the file. The problem should then be resolved.

Moodle 2.0 also requires the use of the PHP zip extension. For most installs this is not an issue, but for some, all it needs to for the line:
extension=php_zip.dll
in the ''Dynamic Extensions'' section to be uncommented.

==See also==

*[[Moodle 2.0 release notes]]

*[[:Category:Moodle 2.0]]

[[Category:Installation]]

[[de:Auf Moodle 2.0 aktualisieren]]
[[fr:Mise à jour à Moodle 2.0]]

Upgrading to Moodle 2.0

2010-12-30T13:15:54Z

ColinFraser: /* Known and Discovered Issues */

{{Moodle 2.0}}When upgrading to Moodle 2.0, you must have Moodle 1.9 or later. if you are using an earlier version of Moodle (eg 1.8.x) then you need to upgrade to Moodle 1.9.x first.

We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.

==System requirements==

* PHP must be '''5.2.8 or later'''
* Databases should be one of the following:
** MySQL 5.0.25 or later (InnoDB storage engine highly recommended)
** PostgreSQL 8.3 or later
** Oracle 10.2 or later
** MS SQL 2005 or later
* Any standards-supporting browser from the past few years, for example:
** Firefox 3 or later
** Safari 3 or later
** Google Chrome 4 or later
** Opera 9 or later
** MS Internet Explorer 7 or later (Even [http://googleenterprise.blogspot.com/2010/01/modern-browsers-for-modern-applications.html Google does not support IE6 any more])

==Before upgrading please... ==
* Always check your site to make sure it meets all system requirements for 2.0 in ''Administration > Server > [[Environment]]''
* '''Do a full database backup!'''
* Remember to purge PHP cache if using any PHP accelerator

==Now upgrade==

Once you have satisfied the requirements for Moodle 2.0, follow the instructions on the [[Upgrading|upgrading]] page.

Moodle 2.0 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

Note, if you get a strange error about 'handling of PHP float numbers', please see [[Installation_FAQ#Moodle_claims_PHP_float_handling_is_not_compatible|this FAQ entry]].

== Verify the upgrade (optional) ==
If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].

== Known and Discovered Issues ==
Many people are reporting that their install/upgrade is reporting that php extension '''intl''' is not installed or available. The intl.dll file is available in later releases of PHP but many hosts may not have a later release. To remedy this problem, discuss with your host the issue you are having and inform them that the problem is easy fixed by either upgrading their php to a newer version or to download the intl.dll and copy it to the php/ext folder. Add to the php.ini file the line:
extension=php_intl.dll
in the ''Dynamic Extensions'' section of the file. The problem should then be resolved.

Moodle 2.0 also requires the use of the PHP zip extension. For most installs this is not an issue, but for some, all it needs to for the line:
extension=php_zip.dll
in the Dynamic Extensions section to be uncommented.

==See also==

*[[Moodle 2.0 release notes]]

*[[:Category:Moodle 2.0]]

[[Category:Installation]]

[[de:Auf Moodle 2.0 aktualisieren]]
[[fr:Mise à jour à Moodle 2.0]]

Upgrading to Moodle 2.0

2010-12-30T13:14:53Z

ColinFraser: /* Known and Discovered Issues */

{{Moodle 2.0}}When upgrading to Moodle 2.0, you must have Moodle 1.9 or later. if you are using an earlier version of Moodle (eg 1.8.x) then you need to upgrade to Moodle 1.9.x first.

We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.

==System requirements==

* PHP must be '''5.2.8 or later'''
* Databases should be one of the following:
** MySQL 5.0.25 or later (InnoDB storage engine highly recommended)
** PostgreSQL 8.3 or later
** Oracle 10.2 or later
** MS SQL 2005 or later
* Any standards-supporting browser from the past few years, for example:
** Firefox 3 or later
** Safari 3 or later
** Google Chrome 4 or later
** Opera 9 or later
** MS Internet Explorer 7 or later (Even [http://googleenterprise.blogspot.com/2010/01/modern-browsers-for-modern-applications.html Google does not support IE6 any more])

==Before upgrading please... ==
* Always check your site to make sure it meets all system requirements for 2.0 in ''Administration > Server > [[Environment]]''
* '''Do a full database backup!'''
* Remember to purge PHP cache if using any PHP accelerator

==Now upgrade==

Once you have satisfied the requirements for Moodle 2.0, follow the instructions on the [[Upgrading|upgrading]] page.

Moodle 2.0 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

Note, if you get a strange error about 'handling of PHP float numbers', please see [[Installation_FAQ#Moodle_claims_PHP_float_handling_is_not_compatible|this FAQ entry]].

== Verify the upgrade (optional) ==
If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].

== Known and Discovered Issues ==
Many people are reporting that their install/upgrade is reporting that php extension '''intl''' is not installed or available. The intl.dll file is available in later releases of PHP but many hosts may not have a later release. To remedy this problem, discuss with your host the issue you are having and inform them that the problem is easy fixed by either upgrading their php to a newer version or to download the intl.dll and copy it to the php/ext folder. Add to the php.ini file the line:
extension=php_intl.dll
in the ''Dynamic Extensions'' section of the file. The problem should then be resolved.

Moodle 2.0 also requires the use of the PHP zip extension. For most installs this is not an issue, but for some, all it needs to for the line:
extension=php_zip.dll
to be uncommented.

==See also==

*[[Moodle 2.0 release notes]]

*[[:Category:Moodle 2.0]]

[[Category:Installation]]

[[de:Auf Moodle 2.0 aktualisieren]]
[[fr:Mise à jour à Moodle 2.0]]

Upgrading to Moodle 2.0

2010-12-30T12:55:24Z

ColinFraser: /* Verify the upgrade (optional) */

{{Moodle 2.0}}When upgrading to Moodle 2.0, you must have Moodle 1.9 or later. if you are using an earlier version of Moodle (eg 1.8.x) then you need to upgrade to Moodle 1.9.x first.

We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.

==System requirements==

* PHP must be '''5.2.8 or later'''
* Databases should be one of the following:
** MySQL 5.0.25 or later (InnoDB storage engine highly recommended)
** PostgreSQL 8.3 or later
** Oracle 10.2 or later
** MS SQL 2005 or later
* Any standards-supporting browser from the past few years, for example:
** Firefox 3 or later
** Safari 3 or later
** Google Chrome 4 or later
** Opera 9 or later
** MS Internet Explorer 7 or later (Even [http://googleenterprise.blogspot.com/2010/01/modern-browsers-for-modern-applications.html Google does not support IE6 any more])

==Before upgrading please... ==
* Always check your site to make sure it meets all system requirements for 2.0 in ''Administration > Server > [[Environment]]''
* '''Do a full database backup!'''
* Remember to purge PHP cache if using any PHP accelerator

==Now upgrade==

Once you have satisfied the requirements for Moodle 2.0, follow the instructions on the [[Upgrading|upgrading]] page.

Moodle 2.0 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

Note, if you get a strange error about 'handling of PHP float numbers', please see [[Installation_FAQ#Moodle_claims_PHP_float_handling_is_not_compatible|this FAQ entry]].

== Verify the upgrade (optional) ==
If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].

== Known and Discovered Issues ==
Many people are reporting that their install/upgrade is reporting that php extension '''intl''' is not installed or available. The intl.dll file is available in later releases of PHP but many hosts may not have a later release. To remedy this problem, discuss with your host the issue you are having and inform them that the problem is easy fixed by either upgrading their php to a newer version or to download the intl.dll and copy it to the php/ext folder. Add to the php.ini file the line:
extension=php_intl.dll
in the ''Dynamic Extensions'' section of the file. The problem should then be resolved.

==See also==

*[[Moodle 2.0 release notes]]

*[[:Category:Moodle 2.0]]

[[Category:Installation]]

[[de:Auf Moodle 2.0 aktualisieren]]
[[fr:Mise à jour à Moodle 2.0]]

Talk:Creating a theme

2010-10-02T13:10:20Z

ColinFraser: /* Is this what??? */

Wow! Is the code for this theme available in a file, say in Modules and Plugins? Or did I miss it in my quick look. I can see my next project at work. --[[User:chris collman|chris collman]] 12:07, 6 April 2010 (UTC)

Hi Chris, the code in this tutorial isn't available anywhere the reason being that it is entirely based on the base theme :) check out ''theme/base/*'' you'll notice that what is in there is very close to the code I wrote for this tutorial. --[[User:Sam Hemelryk|Sam Hemelryk]] 01:33, 7 April 2010 (UTC)
::Hi Sam, I did not look, why get confused by reality and numb about :) I sort of got here by creating a 1.9.8 localhost that I could do screenshots for [[Standard themes]] and then tried my first complete install package of 2.0 in 3 months. My primary goal is to revamp the 'navigation' and organization of Category:Themes pages, your instructions are going to help me. Thanks for all your time and efforts. --[[User:chris collman|chris collman]] 11:26, 7 April 2010 (UTC)

Good crisp documentation!! Thank you Sam for this :) You ve made our lives easier with 2.0 themes!! ;)

Cheers!! --[[User:Navin Dutta|Navin Dutta]] 03:12, 13 April 2010 (UTC)

==Question about instruction==
Sam, your instructions say there will only be one layout php file called standard.php. What is the general.php file pointer doing in config.php under base? If I understand things, it should be pointed to the theme base (which has a general.php) or the file should be called standard.php. Is that correct?

It is snowing, so I thought I would see if I could follow your instructions and do something like standardlogo in 1.9 for fun. No doubt will crash and burn with this part time project over the next 2 years :) Thanks --[[User:chris collman|chris collman]] 13:12, 16 April 2010 (UTC)

== Broken :-( ==

Hello,

Thanks for the tutorial, but with - Moodle 2.0 Preview 2 (Build: 20100531) - I get the error 'Coding error detected, it must be fixed by a programmer: Trying to reference an unknown block region side-post' when trying to select the theme for modern browsers.

Update: I've made the changes required to solve the problem after reading: http://moodle.org/mod/forum/discuss.php?d=150190

Cheers,

Gareth

== Layouts ==

The need for the layout definitions is mentioned but not what they or what they do. This either needs explained or a link to where it is explained. It certainly isn't obvious --[[User:Howard Miller|Howard Miller]] 17:18, 12 July 2010 (UTC)

== Is this what??? ==

Sorry guys, I think this is confusing Please understand that I am not that technically literate so I need things said a lot clearer:

config.php
All of our settings will go here.
/style/
This directory will contain all of our stylesheets.
/style/excitement.css
All of our css will go in here.
/pix/
Into this directory we'll put a screen shot of our theme as well as our favicon and any images we use in CSS.
/layout/
Our layout files will end up in this directory.
/layout/standard.php
This will be our one basic layout file.

There is a clear difference between a file and a directory - but the manner in which the above example is set up does not appear to make that distinction. Could it not be better put like:

Create the theme directory/folder, which we are calling "excitement". Into that directory/folder we create a file:
config.php
All of our settings will go here.
Then we create the directories/folders
/style/
This directory/folder will contain all of our stylesheets.
/pix/
Into this directory/folder we'll put a screen shot of our theme as well as our favicon and any images we use in CSS.
/layout/
Our layout files will end up in this directory/folder.

Into the style directory/folder we create a file:
excitement.css
Where we place All of our css rules.
And in the layout directory/folder we create a file:
standard.php
This will be our one basic layout file.

For me, not being that smart, this is a far more easily understood structure than has been shown.

Talk:Creating a theme

2010-10-02T13:06:41Z

ColinFraser:

Wow! Is the code for this theme available in a file, say in Modules and Plugins? Or did I miss it in my quick look. I can see my next project at work. --[[User:chris collman|chris collman]] 12:07, 6 April 2010 (UTC)

Hi Chris, the code in this tutorial isn't available anywhere the reason being that it is entirely based on the base theme :) check out ''theme/base/*'' you'll notice that what is in there is very close to the code I wrote for this tutorial. --[[User:Sam Hemelryk|Sam Hemelryk]] 01:33, 7 April 2010 (UTC)
::Hi Sam, I did not look, why get confused by reality and numb about :) I sort of got here by creating a 1.9.8 localhost that I could do screenshots for [[Standard themes]] and then tried my first complete install package of 2.0 in 3 months. My primary goal is to revamp the 'navigation' and organization of Category:Themes pages, your instructions are going to help me. Thanks for all your time and efforts. --[[User:chris collman|chris collman]] 11:26, 7 April 2010 (UTC)

Good crisp documentation!! Thank you Sam for this :) You ve made our lives easier with 2.0 themes!! ;)

Cheers!! --[[User:Navin Dutta|Navin Dutta]] 03:12, 13 April 2010 (UTC)

==Question about instruction==
Sam, your instructions say there will only be one layout php file called standard.php. What is the general.php file pointer doing in config.php under base? If I understand things, it should be pointed to the theme base (which has a general.php) or the file should be called standard.php. Is that correct?

It is snowing, so I thought I would see if I could follow your instructions and do something like standardlogo in 1.9 for fun. No doubt will crash and burn with this part time project over the next 2 years :) Thanks --[[User:chris collman|chris collman]] 13:12, 16 April 2010 (UTC)

== Broken :-( ==

Hello,

Thanks for the tutorial, but with - Moodle 2.0 Preview 2 (Build: 20100531) - I get the error 'Coding error detected, it must be fixed by a programmer: Trying to reference an unknown block region side-post' when trying to select the theme for modern browsers.

Update: I've made the changes required to solve the problem after reading: http://moodle.org/mod/forum/discuss.php?d=150190

Cheers,

Gareth

== Layouts ==

The need for the layout definitions is mentioned but not what they or what they do. This either needs explained or a link to where it is explained. It certainly isn't obvious --[[User:Howard Miller|Howard Miller]] 17:18, 12 July 2010 (UTC)

== Is this what??? ==

Sorry guys, I think this is confusing Please understand that I am not that technically literate so I need things said a lot clearer:

config.php
All of our settings will go here.
/style/
This directory will contain all of our stylesheets.
/style/excitement.css
All of our css will go in here.
/pix/
Into this directory we'll put a screen shot of our theme as well as our favicon and any images we use in CSS.
/layout/
Our layout files will end up in this directory.
/layout/standard.php
This will be our one basic layout file.

There is a clear difference between a file and a directory - but the manner in which the above example is set up does not appear to make that distinction. Could it not be better put like:

Create the theme folder, in this we are calling it "excitement"
Into that folder we create the file
config.php
All of our settings will go here.
Then we create the directories
/style/
This directory will contain all of our stylesheets.
/pix/
Into this directory we'll put a screen shot of our theme as well as our favicon and any images we use in CSS.
/layout/
Our layout files will end up in this directory.

Into the style folder we create a file:
excitement.css
Where we place All of our css rules.
And in the layout folder we create a file:
standard.php
This will be our one basic layout file.

For me, not being that smart, this is a far more easily understood structure than has been shown.

Talk:Using images in a theme

2010-10-02T09:07:07Z

ColinFraser:

Just had a quick browse through this, I have not tested this but are there file extensions missing in the examples?

e.g. -
<code css>
body {background-image:url([[pix:theme|gradient]]);}
</code>

shouldn't this read -
<code css>
body {background-image:url([[pix:theme|gradient.png]]);}
</code>

--Matthew Cannings

No. It is intentional.

It is not really important for theme images. After all, if you are making a theme, you probably do know what type your images are. However, suppose in your theme you want to override one of the standard icons, for example i/edit. Well, even though the standard images is i/edit.gif, you might want to replace it with i/edit.png in your theme, and you can, and Moodle will find the image as long as it is one of the supported formats. We use the same basic system for all images (theme, core and plugin) so that is why you must not specify the extension when you link to the image, and you can use any format you like.--[[User:Tim Hunt|Tim Hunt]] 18:50, 10 June 2010 (UTC)

These documents are essentially for developers, but is there going to be a plainer version for us who do not speak the necessary jargon? I have been trying to figure out how to explain this in the [[Front Page FAQ]] to provide people looking at Moodle 2.0 with a hope of including their own logos onto their selected themes. Seriously, I do not have either the time or the patience to learn PHP to the point where I might be able to explain it in a non-technical manner. From what I am able to decipher, it might be easier than earlier versions, but I cannot be sure. --[[User:Colin Fraser|Colin Fraser]] 09:02, 2 October 2010 (UTC)

Talk:Using images in a theme

2010-10-02T09:06:28Z

ColinFraser:

Just had a quick browse through this, I have not tested this but are there file extensions missing in the examples?

e.g. -
<code css>
body {background-image:url([[pix:theme|gradient]]);}
</code>

shouldn't this read -
<code css>
body {background-image:url([[pix:theme|gradient.png]]);}
</code>

--Matthew Cannings

No. It is intentional.

It is not really important for theme images. After all, if you are making a theme, you probably do know what type your images are. However, suppose in your theme you want to override one of the standard icons, for example i/edit. Well, even though the standard images is i/edit.gif, you might want to replace it with i/edit.png in your theme, and you can, and Moodle will find the image as long as it is one of the supported formats. We use the same basic system for all images (theme, core and plugin) so that is why you must not specify the extension when you link to the image, and you can use any format you like.--[[User:Tim Hunt|Tim Hunt]] 18:50, 10 June 2010 (UTC)

These documents are essentially for developers, but is there going to be a plainer version for us who do not speak the necessary jargon? I have been trying to figure out how to explain this in the Front Page FAQ to provide people looking at Moodle 2.0 with a hope of including their own logos onto their selected themes. Seriously, I do not have either the time or the patience to learn PHP to the point where I might be able to explain it in a non-technical manner. From what I am able to decipher, it might be easier than earlier versions, but I cannot be sure. --[[User:Colin Fraser|Colin Fraser]] 09:02, 2 October 2010 (UTC)

Talk:Using images in a theme

2010-10-02T09:02:44Z

ColinFraser:

Just had a quick browse through this, I have not tested this but are there file extensions missing in the examples?

e.g. -
<code css>
body {background-image:url([[pix:theme|gradient]]);}
</code>

shouldn't this read -
<code css>
body {background-image:url([[pix:theme|gradient.png]]);}
</code>

--Matthew Cannings

No. It is intentional.

It is not really important for theme images. After all, if you are making a theme, you probably do know what type your images are. However, suppose in your theme you want to override one of the standard icons, for example i/edit. Well, even though the standard images is i/edit.gif, you might want to replace it with i/edit.png in your theme, and you can, and Moodle will find the image as long as it is one of the supported formats. We use the same basic system for all images (theme, core and plugin) so that is why you must not specify the extension when you link to the image, and you can use any format you like.--[[User:Tim Hunt|Tim Hunt]] 18:50, 10 June 2010 (UTC)

These documents are essentially for developers, but is there going to be a plainer version for us who do not speak the necessary jargon? --[[User:Colin Fraser|Colin Fraser]] 09:02, 2 October 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-04-18T08:35:37Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
Oh, and what is the "Other"??? IIS and Apache, and... What about Mac? Has anyone given any consideration to Macs?--[[User:Colin Fraser|Colin Fraser]] 08:35, 18 April 2010 (UTC)

I also found this M$ Knowledge base article that is about as clear as mud. However, it does name a variable that can be reset, all the user has to do is to find where the variable resides. I have linked the actual article, but it seems this variable is named in several places. Why can it not be simple? --[[User:Colin Fraser|Colin Fraser]] 08:32, 18 April 2010 (UTC)

I have found this little site that configures FastCGI, something I understand nothing about actually, but that has never stopped me in the past..:) I have included a link, I understand that is is connected to PHP and IIS, so it should be there. --[[User:Colin Fraser|Colin Fraser]] 11:29, 29 March 2010 (UTC)

The revamp works a lot better than I proposed. The basic information and invitation to read on does what it should do, differentiates between people who know what they are doing, like a lot of network admins and superusers, and beginners without being patronizing, well done, whoever did it..:) --[[User:Colin Fraser|Colin Fraser]] 10:59, 18 March 2010 (UTC)

Hi Chris, I looked at that, what a great idea, can we develop these two docs to make some serious sense? It would certainly make doing this one a lot easier, and smaller. What do you think Jon? --[[User:Colin Fraser|Colin Fraser]] 11:36, 16 March 2010 (UTC)
::the two docs being ?? Just to make sure we are clear with each other :)--[[User:chris collman|chris collman]] 19:56, 17 March 2010 (UTC)

::This one [[Installing Moodle/Creating custom php.ini files]] and the upload file sizes doc, if that is OK with you and Jon, if he is interested, and whoever wrote the php ini files doc, of course. --[[User:Colin Fraser|Colin Fraser]] 09:34, 18 March 2010 (UTC).

Hi Jon, I do not disagree with your logic, and did consider it, but for me, the issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. BTW, if I have it right, IIS uses the php.ini file in the same way as Apache, and it is directly editable. I am going to test this out as soon as I get a new machine and turn my oldest one into a server. I am thinking of creating a Linux box with a Windows virtual server, but time is against me at the moment.--[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

::Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]
----
Just noticed [[Installing Moodle/Creating custom php.ini files]] a subpage created by Marc and visited by Jon. Plus the Administration FAQs have a section. I think the FAQ can be reduced once we get our version of this page together. I did put a link to the File upload size page.--[[User:chris collman|chris collman]] 15:33, 14 March 2010 (UTC)

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-04-18T08:32:47Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
I also found this M$ Knowledge base article that is about as clear as mud. However, it does name a variable that can be reset, all the user has to do is to find where the variable resides. I have linked the actual article, but it seems this variable is named in several places. Why can it not be simple? --[[User:Colin Fraser|Colin Fraser]] 08:32, 18 April 2010 (UTC)

I have found this little site that configures FastCGI, something I understand nothing about actually, but that has never stopped me in the past..:) I have included a link, I understand that is is connected to PHP and IIS, so it should be there. --[[User:Colin Fraser|Colin Fraser]] 11:29, 29 March 2010 (UTC)

The revamp works a lot better than I proposed. The basic information and invitation to read on does what it should do, differentiates between people who know what they are doing, like a lot of network admins and superusers, and beginners without being patronizing, well done, whoever did it..:) --[[User:Colin Fraser|Colin Fraser]] 10:59, 18 March 2010 (UTC)

Hi Chris, I looked at that, what a great idea, can we develop these two docs to make some serious sense? It would certainly make doing this one a lot easier, and smaller. What do you think Jon? --[[User:Colin Fraser|Colin Fraser]] 11:36, 16 March 2010 (UTC)
::the two docs being ?? Just to make sure we are clear with each other :)--[[User:chris collman|chris collman]] 19:56, 17 March 2010 (UTC)

::This one [[Installing Moodle/Creating custom php.ini files]] and the upload file sizes doc, if that is OK with you and Jon, if he is interested, and whoever wrote the php ini files doc, of course. --[[User:Colin Fraser|Colin Fraser]] 09:34, 18 March 2010 (UTC).

Hi Jon, I do not disagree with your logic, and did consider it, but for me, the issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. BTW, if I have it right, IIS uses the php.ini file in the same way as Apache, and it is directly editable. I am going to test this out as soon as I get a new machine and turn my oldest one into a server. I am thinking of creating a Linux box with a Windows virtual server, but time is against me at the moment.--[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

::Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]
----
Just noticed [[Installing Moodle/Creating custom php.ini files]] a subpage created by Marc and visited by Jon. Plus the Administration FAQs have a section. I think the FAQ can be reduced once we get our version of this page together. I did put a link to the File upload size page.--[[User:chris collman|chris collman]] 15:33, 14 March 2010 (UTC)

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User:Jon Witts/file-upload-v2

2010-04-18T08:29:02Z

ColinFraser: /* IIS */

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. So to increase the file upload size in Moodle we must first adjust this setting. You will need to find out where the active php.ini is located and if another program is over riding it.

==Php.ini changes==
Here are the changes you might make to a php.ini file. For those who need more information, please continue reading other sections in this page.

After find the correct php.ini file, look for and change two variables. In the example below, we found the following lines set the max file size to 512 megabytes.

upload_max_filesize = 512M
post_max_size = 512M

This may seem large, but do not forget, the Administrator can go to '''Front Page ► Administration ► Courses ► Course default settings''' and reset the maximum file upload size to whatever level required. It also means that if someone needs a maximum file size temporarily, say a multimedia teacher uploading a large file, the Administrator can reset these values in the same location, and set them back again later.

==Find php.ini control information==
For those who are continuing on and need more information, you may need to find the php.ini file that controls the size of the upload files.

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
The easiest way to find the location of the controlling php.ini files in Moodle 1.7 onward is to call up Site administration block>Server>PHP info. This will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

Add the below to your .htaccess file
* php_value upload_max_filesize 512M
* php_value post_max_size 512M

===IIS===
There seems to be a double whammy for IIS. Not only is there a restriction in file size uploads for PHP there is also one for IIS. To change the PHP limit is the same as is described above, at the start, change those two variables already mentioned. The next issue is with IIS. This comes from [http://msdn.microsoft.com/en-us/library/ms524953.aspx Microsoft's knowledge base.] Unfortunately, like most Microsoft documentation, it is not all that clear.

MaxRequestEntityAllowed
The MaxRequestEntityAllowed property specifies the maximum number of bytes allowed in the entity body of a request.
If a Content-Length header is present and specifies an amount of data greater than the value of
MaxRequestEntityAllowed, IIS sends a 403 error response.

The metabase represents unlimited as the DWORD value of 4294967295 (0xFFFFFFFF); however, VBScript represents unlimited in hexadecimal format as &HFFFFFFFF.
Previous versions of IIS represented unlimited as -1.

There is a lot more, but this should provide you with the basic knowledge you need to be able to change the upload file size limits.

====FastCGI====
To make PHP work a little better in IIS, you can utilize the FastCGI component, information about which can be found in this [http://www.iis.net/ConfigReference/system.webServer/fastCgi php.iis.net] site.

===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==See also==
*[[Installing Moodle/Creating custom php.ini files]]
*[[Beginning Administration FAQ]]

User:Jon Witts/file-upload-v2

2010-04-18T08:28:03Z

ColinFraser: /* IIS */

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. So to increase the file upload size in Moodle we must first adjust this setting. You will need to find out where the active php.ini is located and if another program is over riding it.

==Php.ini changes==
Here are the changes you might make to a php.ini file. For those who need more information, please continue reading other sections in this page.

After find the correct php.ini file, look for and change two variables. In the example below, we found the following lines set the max file size to 512 megabytes.

upload_max_filesize = 512M
post_max_size = 512M

This may seem large, but do not forget, the Administrator can go to '''Front Page ► Administration ► Courses ► Course default settings''' and reset the maximum file upload size to whatever level required. It also means that if someone needs a maximum file size temporarily, say a multimedia teacher uploading a large file, the Administrator can reset these values in the same location, and set them back again later.

==Find php.ini control information==
For those who are continuing on and need more information, you may need to find the php.ini file that controls the size of the upload files.

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
The easiest way to find the location of the controlling php.ini files in Moodle 1.7 onward is to call up Site administration block>Server>PHP info. This will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

Add the below to your .htaccess file
* php_value upload_max_filesize 512M
* php_value post_max_size 512M

===IIS===
There seems to be a double whammy for IIS. Not only is there a restriction in file size uploads for PHP there is also one for IIS. To change the PHP limit is the same as is described above, at the start, change those two variables already mentioned. The next issue is with IIS. This comes from [http://msdn.microsoft.com/en-us/library/ms524953.aspx Microsoft's knowledge base.]

MaxRequestEntityAllowed
The MaxRequestEntityAllowed property specifies the maximum number of bytes allowed in the entity body of a request.
If a Content-Length header is present and specifies an amount of data greater than the value of
MaxRequestEntityAllowed, IIS sends a 403 error response.

The metabase represents unlimited as the DWORD value of 4294967295 (0xFFFFFFFF); however, VBScript represents unlimited in hexadecimal format as &HFFFFFFFF.
Previous versions of IIS represented unlimited as -1.

There is a lot more, but this should provide you with the basic knowledge you need to be able to change the upload file size limits.

====FastCGI====
To make PHP work a little better in IIS, you can utilize the FastCGI component, information about which can be found in this [http://www.iis.net/ConfigReference/system.webServer/fastCgi php.iis.net] site.

===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==See also==
*[[Installing Moodle/Creating custom php.ini files]]
*[[Beginning Administration FAQ]]

User:Jon Witts/file-upload-v2

2010-04-18T08:26:54Z

ColinFraser: /* IIS */

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. So to increase the file upload size in Moodle we must first adjust this setting. You will need to find out where the active php.ini is located and if another program is over riding it.

==Php.ini changes==
Here are the changes you might make to a php.ini file. For those who need more information, please continue reading other sections in this page.

After find the correct php.ini file, look for and change two variables. In the example below, we found the following lines set the max file size to 512 megabytes.

upload_max_filesize = 512M
post_max_size = 512M

This may seem large, but do not forget, the Administrator can go to '''Front Page ► Administration ► Courses ► Course default settings''' and reset the maximum file upload size to whatever level required. It also means that if someone needs a maximum file size temporarily, say a multimedia teacher uploading a large file, the Administrator can reset these values in the same location, and set them back again later.

==Find php.ini control information==
For those who are continuing on and need more information, you may need to find the php.ini file that controls the size of the upload files.

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
The easiest way to find the location of the controlling php.ini files in Moodle 1.7 onward is to call up Site administration block>Server>PHP info. This will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

Add the below to your .htaccess file
* php_value upload_max_filesize 512M
* php_value post_max_size 512M

===IIS===
There seems to be a double whammy for IIS. Not only is there a restriction in file size uploads for PHP there is also one for IIS. To change the PHP limit is the same as is described above, at the start, change those two variables already mentioned. The next issue is with IIS. This comes from [http://msdn.microsoft.com/en-us/library/ms524953.aspx The dark side itself.]

MaxRequestEntityAllowed
The MaxRequestEntityAllowed property specifies the maximum number of bytes allowed in the entity body of a request.
If a Content-Length header is present and specifies an amount of data greater than the value of
MaxRequestEntityAllowed, IIS sends a 403 error response.

The metabase represents unlimited as the DWORD value of 4294967295 (0xFFFFFFFF); however, VBScript represents unlimited in hexadecimal format as &HFFFFFFFF.
Previous versions of IIS represented unlimited as -1.

There is a lot more, but this should provide you with the basic knowledge you need to be able to change the ulopad file size limits.

====FastCGI====
To make PHP work a little better in IIS, you can utilise the FastCGI component, information about which can be found in this [http://www.iis.net/ConfigReference/system.webServer/fastCgi php.iis.net] site.

===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==See also==
*[[Installing Moodle/Creating custom php.ini files]]
*[[Beginning Administration FAQ]]

User:Jon Witts/file-upload-v2

2010-04-18T08:26:15Z

ColinFraser: /* IIS */

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. So to increase the file upload size in Moodle we must first adjust this setting. You will need to find out where the active php.ini is located and if another program is over riding it.

==Php.ini changes==
Here are the changes you might make to a php.ini file. For those who need more information, please continue reading other sections in this page.

After find the correct php.ini file, look for and change two variables. In the example below, we found the following lines set the max file size to 512 megabytes.

upload_max_filesize = 512M
post_max_size = 512M

This may seem large, but do not forget, the Administrator can go to '''Front Page ► Administration ► Courses ► Course default settings''' and reset the maximum file upload size to whatever level required. It also means that if someone needs a maximum file size temporarily, say a multimedia teacher uploading a large file, the Administrator can reset these values in the same location, and set them back again later.

==Find php.ini control information==
For those who are continuing on and need more information, you may need to find the php.ini file that controls the size of the upload files.

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
The easiest way to find the location of the controlling php.ini files in Moodle 1.7 onward is to call up Site administration block>Server>PHP info. This will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

Add the below to your .htaccess file
* php_value upload_max_filesize 512M
* php_value post_max_size 512M

===IIS===
There seems to be a double whammy for IIS. Not only is there a restriction in file size uploads for PHP there is also one for IIS. To change the PHP limit is the same as is described above, at the start, change those two variables already mentioned. The next issue is with IIS. This comes from [http://msdn.microsoft.com/en-us/library/ms524953.aspx The dark side itself.]

MaxRequestEntityAllowed
The MaxRequestEntityAllowed property specifies the maximum number of bytes allowed in the entity body of a request. If a Content-Length header is present and specifies an amount of data greater than the value of MaxRequestEntityAllowed, IIS sends a 403 error response.

The metabase represents unlimited as the DWORD value of 4294967295 (0xFFFFFFFF); however, VBScript represents unlimited in hexadecimal format as &HFFFFFFFF.
Previous versions of IIS represented unlimited as -1.

There is a lot more, but this should provide you with the basic knowledge you need to be able to change the ulopad file size limits.

====FastCGI====
To make PHP work a little better in IIS, you can utilise the FastCGI component, information about which can be found in this [http://www.iis.net/ConfigReference/system.webServer/fastCgi php.iis.net] site.

===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==See also==
*[[Installing Moodle/Creating custom php.ini files]]
*[[Beginning Administration FAQ]]

User:Jon Witts/file-upload-v2

2010-04-18T08:24:23Z

ColinFraser: /* IIS */

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. So to increase the file upload size in Moodle we must first adjust this setting. You will need to find out where the active php.ini is located and if another program is over riding it.

==Php.ini changes==
Here are the changes you might make to a php.ini file. For those who need more information, please continue reading other sections in this page.

After find the correct php.ini file, look for and change two variables. In the example below, we found the following lines set the max file size to 512 megabytes.

upload_max_filesize = 512M
post_max_size = 512M

This may seem large, but do not forget, the Administrator can go to '''Front Page ► Administration ► Courses ► Course default settings''' and reset the maximum file upload size to whatever level required. It also means that if someone needs a maximum file size temporarily, say a multimedia teacher uploading a large file, the Administrator can reset these values in the same location, and set them back again later.

==Find php.ini control information==
For those who are continuing on and need more information, you may need to find the php.ini file that controls the size of the upload files.

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
The easiest way to find the location of the controlling php.ini files in Moodle 1.7 onward is to call up Site administration block>Server>PHP info. This will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

Add the below to your .htaccess file
* php_value upload_max_filesize 512M
* php_value post_max_size 512M

===IIS===
There seems to be a double whammy for IIS. Not only is there a restriction in file size uploads for PHP there is also one for IIS. To change the PHP limit is the same as is described above, at the start, change those two variables already mentioned. The next issue is with IIS. This comes from [http://msdn.microsoft.com/en-us/library/ms524953.aspx The dark side itself.]

MaxRequestEntityAllowed

The MaxRequestEntityAllowed property specifies the maximum number of bytes allowed in the entity body of a request. If a Content-Length header is present and specifies an amount of data greater than the value of MaxRequestEntityAllowed, IIS sends a 403 error response.

The metabase represents unlimited as the DWORD value of 4294967295 (0xFFFFFFFF); however, VBScript represents unlimited in hexadecimal format as &HFFFFFFFF. Previous versions of IIS represented unlimited as -1.

====FastCGI====
To make PHP work a little better in IIS, you can utilise the FastCGI component, information about which can be found in this [http://www.iis.net/ConfigReference/system.webServer/fastCgi php.iis.net] site.

===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==See also==
*[[Installing Moodle/Creating custom php.ini files]]
*[[Beginning Administration FAQ]]

User:Jon Witts/file-upload-v2

2010-04-18T07:50:49Z

ColinFraser: /* Apache */

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. So to increase the file upload size in Moodle we must first adjust this setting. You will need to find out where the active php.ini is located and if another program is over riding it.

==Php.ini changes==
Here are the changes you might make to a php.ini file. For those who need more information, please continue reading other sections in this page.

After find the correct php.ini file, look for and change two variables. In the example below, we found the following lines set the max file size to 512 megabytes.

upload_max_filesize = 512M
post_max_size = 512M

This may seem large, but do not forget, the Administrator can go to '''Front Page ► Administration ► Courses ► Course default settings''' and reset the maximum file upload size to whatever level required. It also means that if someone needs a maximum file size temporarily, say a multimedia teacher uploading a large file, the Administrator can reset these values in the same location, and set them back again later.

==Find php.ini control information==
For those who are continuing on and need more information, you may need to find the php.ini file that controls the size of the upload files.

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
The easiest way to find the location of the controlling php.ini files in Moodle 1.7 onward is to call up Site administration block>Server>PHP info. This will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

Add the below to your .htaccess file
* php_value upload_max_filesize 512M
* php_value post_max_size 512M

===IIS===

====FastCGI====
To make PHP work a little better in IIS, you can utilise the FastCGI component, information about which can be found in this [http://www.iis.net/ConfigReference/system.webServer/fastCgi php.iis.net] site.

===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==See also==
*[[Installing Moodle/Creating custom php.ini files]]
*[[Beginning Administration FAQ]]

User:Jon Witts/file-upload-v2

2010-04-18T07:43:18Z

ColinFraser: /* Php.ini changes */

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. So to increase the file upload size in Moodle we must first adjust this setting. You will need to find out where the active php.ini is located and if another program is over riding it.

==Php.ini changes==
Here are the changes you might make to a php.ini file. For those who need more information, please continue reading other sections in this page.

After find the correct php.ini file, look for and change two variables. In the example below, we found the following lines set the max file size to 512 megabytes.

upload_max_filesize = 512M
post_max_size = 512M

This may seem large, but do not forget, the Administrator can go to '''Front Page ► Administration ► Courses ► Course default settings''' and reset the maximum file upload size to whatever level required. It also means that if someone needs a maximum file size temporarily, say a multimedia teacher uploading a large file, the Administrator can reset these values in the same location, and set them back again later.

==Find php.ini control information==
For those who are continuing on and need more information, you may need to find the php.ini file that controls the size of the upload files.

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
The easiest way to find the location of the controlling php.ini files in Moodle 1.7 onward is to call up Site administration block>Server>PHP info. This will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

===IIS===

====FastCGI====
To make PHP work a little better in IIS, you can utilise the FastCGI component, information about which can be found in this [http://www.iis.net/ConfigReference/system.webServer/fastCgi php.iis.net] site.

===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==See also==
*[[Installing Moodle/Creating custom php.ini files]]
*[[Beginning Administration FAQ]]

User:Jon Witts/file-upload-v2

2010-04-18T07:37:20Z

ColinFraser: /* Php.ini changes */

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. So to increase the file upload size in Moodle we must first adjust this setting. You will need to find out where the active php.ini is located and if another program is over riding it.

==Php.ini changes==
Here are the changes you might make to a php.ini file. For those who need more information, please continue reading other sections in this page.

After find the correct php.ini file, look for and change two variables. In the example below, we found the following lines set the max file size to 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==Find php.ini control information==
For those who are continuing on and need more information, you may need to find the php.ini file that controls the size of the upload files.

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
The easiest way to find the location of the controlling php.ini files in Moodle 1.7 onward is to call up Site administration block>Server>PHP info. This will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

===IIS===

====FastCGI====
To make PHP work a little better in IIS, you can utilise the FastCGI component, information about which can be found in this [http://www.iis.net/ConfigReference/system.webServer/fastCgi php.iis.net] site.

===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==See also==
*[[Installing Moodle/Creating custom php.ini files]]
*[[Beginning Administration FAQ]]

User talk:Jon Witts/file-upload-v2

2010-03-29T11:29:24Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
I have found this little site that configures FastCGI, something I understand nothing about actually, but that has never stopped me in the past..:) I have included a link, I understand that is is connected to PHP and IIS, so it should be there. --[[User:Colin Fraser|Colin Fraser]] 11:29, 29 March 2010 (UTC)

The revamp works a lot better than I proposed. The basic information and invitation to read on does what it should do, differentiates between people who know what they are doing, like a lot of network admins and superusers, and beginners without being patronizing, well done, whoever did it..:) --[[User:Colin Fraser|Colin Fraser]] 10:59, 18 March 2010 (UTC)

Hi Chris, I looked at that, what a great idea, can we develop these two docs to make some serious sense? It would certainly make doing this one a lot easier, and smaller. What do you think Jon? --[[User:Colin Fraser|Colin Fraser]] 11:36, 16 March 2010 (UTC)
::the two docs being ?? Just to make sure we are clear with each other :)--[[User:chris collman|chris collman]] 19:56, 17 March 2010 (UTC)

::This one [[Installing Moodle/Creating custom php.ini files]] and the upload file sizes doc, if that is OK with you and Jon, if he is interested, and whoever wrote the php ini files doc, of course. --[[User:Colin Fraser|Colin Fraser]] 09:34, 18 March 2010 (UTC).

Hi Jon, I do not disagree with your logic, and did consider it, but for me, the issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. BTW, if I have it right, IIS uses the php.ini file in the same way as Apache, and it is directly editable. I am going to test this out as soon as I get a new machine and turn my oldest one into a server. I am thinking of creating a Linux box with a Windows virtual server, but time is against me at the moment.--[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

::Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]
----
Just noticed [[Installing Moodle/Creating custom php.ini files]] a subpage created by Marc and visited by Jon. Plus the Administration FAQs have a section. I think the FAQ can be reduced once we get our version of this page together. I did put a link to the File upload size page.--[[User:chris collman|chris collman]] 15:33, 14 March 2010 (UTC)

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User:Jon Witts/file-upload-v2

2010-03-29T11:26:50Z

ColinFraser: /* IIS */

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. So to increase the file upload size in Moodle we must first adjust this setting. You will need to find out where the active php.ini is located and if another program is over riding it.

==Php.ini changes==
Here are the changes you might make to a php.ini file. For those who need more information, please continue reading other sections in this page.

After find the correct php.ini file, look for and change two vairables. In the example below, we found the following lines set the mex file size to 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==Find php.ini control information==
For those who are continuing on and need more information, you may need to find the php.ini file that controls the size of the upload files.

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
The easiest way to find the location of the controlling php.ini files in Moodle 1.7 onward is to call up Site administration block>Server>PHP info. This will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

===IIS===

====FastCGI====
To make PHP work a little better in IIS, you can utilise the FastCGI component, information about which can be found in this [http://www.iis.net/ConfigReference/system.webServer/fastCgi php.iis.net] site.

===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==See also==
*[[Installing Moodle/Creating custom php.ini files]]
*[[Beginning Administration FAQ]]

User:Jon Witts/file-upload-v2

2010-03-29T11:25:29Z

ColinFraser: /* IIS */

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. So to increase the file upload size in Moodle we must first adjust this setting. You will need to find out where the active php.ini is located and if another program is over riding it.

==Php.ini changes==
Here are the changes you might make to a php.ini file. For those who need more information, please continue reading other sections in this page.

After find the correct php.ini file, look for and change two vairables. In the example below, we found the following lines set the mex file size to 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==Find php.ini control information==
For those who are continuing on and need more information, you may need to find the php.ini file that controls the size of the upload files.

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
The easiest way to find the location of the controlling php.ini files in Moodle 1.7 onward is to call up Site administration block>Server>PHP info. This will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

===IIS===
To make PHP work a little better in IIS, you can utilise the FastCGI component, information about which can be found in this [http://www.iis.net/ConfigReference/system.webServer/fastCgi php.iis.net] site.

===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==See also==
*[[Installing Moodle/Creating custom php.ini files]]
*[[Beginning Administration FAQ]]

User talk:Jon Witts/file-upload-v2

2010-03-18T10:59:42Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
The revamp works a lot better than I proposed. The basic information and invitation to read on does what it should do, differentiates between people who know what they are doing, like a lot of network admins and superusers, and beginners without being patronizing, well done, whoever did it..:) --[[User:Colin Fraser|Colin Fraser]] 10:59, 18 March 2010 (UTC)

Hi Chris, I looked at that, what a great idea, can we develop these two docs to make some serious sense? It would certainly make doing this one a lot easier, and smaller. What do you think Jon? --[[User:Colin Fraser|Colin Fraser]] 11:36, 16 March 2010 (UTC)
::the two docs being ?? Just to make sure we are clear with each other :)--[[User:chris collman|chris collman]] 19:56, 17 March 2010 (UTC)

::This one [[Installing Moodle/Creating custom php.ini files]] and the upload file sizes doc, if that is OK with you and Jon, if he is interested, and whoever wrote the php ini files doc, of course. --[[User:Colin Fraser|Colin Fraser]] 09:34, 18 March 2010 (UTC).

Hi Jon, I do not disagree with your logic, and did consider it, but for me, the issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. BTW, if I have it right, IIS uses the php.ini file in the same way as Apache, and it is directly editable. I am going to test this out as soon as I get a new machine and turn my oldest one into a server. I am thinking of creating a Linux box with a Windows virtual server, but time is against me at the moment.--[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

::Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]
----
Just noticed [[Installing Moodle/Creating custom php.ini files]] a subpage created by Marc and visited by Jon. Plus the Administration FAQs have a section. I think the FAQ can be reduced once we get our version of this page together. I did put a link to the File upload size page.--[[User:chris collman|chris collman]] 15:33, 14 March 2010 (UTC)

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User:Jon Witts/file-upload-v2

2010-03-18T10:55:34Z

ColinFraser: /* See also */

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. So to increase the file upload size in Moodle we must first adjust this setting. You will need to find out where the active php.ini is located and if another program is over riding it.

==Php.ini changes==
Here are the changes you might make to a php.ini file. For those who need more information, please continue reading other sections in this page.

After find the correct php.ini file, look for and change two vairables. In the example below, we found the following lines set the mex file size to 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==Find php.ini control information==
For those who are continuing on and need more information, you may need to find the php.ini file that controls the size of the upload files.

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
The easiest way to find the location of the controlling php.ini files in Moodle 1.7 onward is to call up Site administration block>Server>PHP info. This will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

===IIS===
.... edit php.ini ?! ...
===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

==See also==
*[[Installing Moodle/Creating custom php.ini files]]
*[[Beginning Administration FAQ]]

User talk:Jon Witts/file-upload-v2

2010-03-18T10:52:02Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
Hi Chris, I looked at that, what a great idea, can we develop these two docs to make some serious sense? It would certainly make doing this one a lot easier, and smaller. What do you think Jon? --[[User:Colin Fraser|Colin Fraser]] 11:36, 16 March 2010 (UTC)
::the two docs being ?? Just to make sure we are clear with each other :)--[[User:chris collman|chris collman]] 19:56, 17 March 2010 (UTC)

::This one [[Installing Moodle/Creating custom php.ini files]] and the upload file sizes doc, if that is OK with you and Jon, if he is interested, and whoever wrote the php ini files doc, of course. --[[User:Colin Fraser|Colin Fraser]] 09:34, 18 March 2010 (UTC).

Hi Jon, I do not disagree with your logic, and did consider it, but for me, the issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. BTW, if I have it right, IIS uses the php.ini file in the same way as Apache, and it is directly editable. I am going to test this out as soon as I get a new machine and turn my oldest one into a server. I am thinking of creating a Linux box with a Windows virtual server, but time is against me at the moment.--[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

::Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]
----
Just noticed [[Installing Moodle/Creating custom php.ini files]] a subpage created by Marc and visited by Jon. Plus the Administration FAQs have a section. I think the FAQ can be reduced once we get our version of this page together. I did put a link to the File upload size page.--[[User:chris collman|chris collman]] 15:33, 14 March 2010 (UTC)

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-18T09:34:11Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
Hi Chris, I looked at that, what a great idea, can we develop these two docs to make some serious sense? It would certainly make doing this one a lot easier, and smaller. What do you think Jon? --[[User:Colin Fraser|Colin Fraser]] 11:36, 16 March 2010 (UTC)
::the two docs being ?? Just to make sure we are clear with each other :)--[[User:chris collman|chris collman]] 19:56, 17 March 2010 (UTC)
::This one [[Installing Moodle/Creating custom php.ini files]] and the upload file sizes doc, if that is OK with you and Jon, if he is interested, and whoever wrote the php ini files doc, of course. --[[User:Colin Fraser|Colin Fraser]] 09:34, 18 March 2010 (UTC).

Hi Jon, I do not disagree with your logic, and did consider it, but for me, the issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. BTW, if I have it right, IIS uses the php.ini file in the same way as Apache, and it is directly editable. I am going to test this out as soon as I get a new machine and turn my oldest one into a server. I am thinking of creating a Linux box with a Windows virtual server, but time is against me at the moment.--[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

::Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]
----
Just noticed [[Installing Moodle/Creating custom php.ini files]] a subpage created by Marc and visited by Jon. Plus the Administration FAQs have a section. I think the FAQ can be reduced once we get our version of this page together. I did put a link to the File upload size page.--[[User:chris collman|chris collman]] 15:33, 14 March 2010 (UTC)

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-18T09:32:10Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
Hi Chris, I looked at that, what a great idea, can we develop these two docs to make some serious sense? It would certainly make doing this one a lot easier, and smaller. What do you think Jon? --[[User:Colin Fraser|Colin Fraser]] 11:36, 16 March 2010 (UTC)
::the two docs being ?? Just to make sure we are clear with each other :)--[[User:chris collman|chris collman]] 19:56, 17 March 2010 (UTC)
;;This one [[Installing Moodle/Creating custom php.ini files]] and the upload file sizes doc.

Hi Jon, I do not disagree with your logic, and did consider it, but for me, the issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. BTW, if I have it right, IIS uses the php.ini file in the same way as Apache, and it is directly editable. I am going to test this out as soon as I get a new machine and turn my oldest one into a server. I am thinking of creating a Linux box with a Windows virtual server, but time is against me at the moment.--[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

::Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]
----
Just noticed [[Installing Moodle/Creating custom php.ini files]] a subpage created by Marc and visited by Jon. Plus the Administration FAQs have a section. I think the FAQ can be reduced once we get our version of this page together. I did put a link to the File upload size page.--[[User:chris collman|chris collman]] 15:33, 14 March 2010 (UTC)

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-16T11:36:47Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
Hi Chris, I looked at that, what a great idea, can we develop these two docs to make some serious sense? It would certainly make doing this one a lot easier, and smaller. What do you think Jon? --[[User:Colin Fraser|Colin Fraser]] 11:36, 16 March 2010 (UTC)

Hi Jon, I do not disagree with your logic, and did consider it, but for me, the issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. BTW, if I have it right, IIS uses the php.ini file in the same way as Apache, and it is directly editable. I am going to test this out as soon as I get a new machine and turn my oldest one into a server. I am thinking of creating a Linux box with a Windows virtual server, but time is against me at the moment.--[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

::Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]
----
Just noticed [[Installing Moodle/Creating custom php.ini files]] a subpage created by Marc and visited by Jon. Plus the Administration FAQs have a section. I think the FAQ can be reduced once we get our version of this page together. I did put a link to the File upload size page.--[[User:chris collman|chris collman]] 15:33, 14 March 2010 (UTC)

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-13T12:40:22Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
Hi Jon, I do not disagree with your logic, and did consider it, but for me, the issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. BTW, if I have it right, IIS uses the php.ini file in the same way as Apache, and it is directly editable. I am going to test this out as soon as I get a new machine and turn my oldest one into a server. I am thinking of creating a Linux box with a Windows virtual server, but time is against me at the moment.--[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

----------

Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-13T12:39:37Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
Hi Jon, I do not disagree with your logic, and did consider it, but the for me issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. BTW, if I have it right, IIS uses the php.ini file in the same way as Apache, and it is directly editable. I am going to test this out as soon as I get a new machine and turn my oldest one into a server. I am thinking of creating a Linux box with a Windows virtual server, but time is against me at the moment.--[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

----------

Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-13T12:38:40Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
I do not disagree with your logic, and did consider it, but the for me issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. BTW, if I have it right, IIS uses the php.ini file in the same way as Apache, and it is directly editable. I am going to test this out as soon as I get a new machine and turn my oldest one into a server. I am thinking of creating a Linux box with a Windows virtual server, but time is against me at the moment.--[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

----------

Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-13T12:33:20Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Colin,

I am not to happy with that generic statement. There are far too many users that will not have access to the php.ini file and this could just lead to confusion. We need to be able to guide the user to how their particular server set-up is configured first; and then instruct them what changes to make, or we will be making the issue worse. [[User:Jon Witts|Jon Witts]] 09:19, 13 March 2010 (UTC)

Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
I do not disagree with your logic, and did consider it, but the for me issue is still that users can be drowned in detail before they get to what they are looking for. Suggest we consider the other option, give them the information first, then explain how it works. --[[User:Colin Fraser|Colin Fraser]] 12:33, 13 March 2010 (UTC)

I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

----------

Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-13T08:57:51Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

Jon, I certainly agree with your last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

----------

Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-13T08:57:20Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
I added a short generic comment about what needs be changed, I suggest that this comes first, irrespective of anything else. The way it was there was no mention of what needs be changed until well down the page. The structure this imposes makes what follows a little awkward, or rather what I put in is awkward and does not sit well there, but that is where I think it needs to be. My wording is a little clumsy, and may not be technically correct, so please yourself. Cheers.--[[User:Colin Fraser|Colin Fraser]] 08:57, 13 March 2010 (UTC)

I certainly agree with that last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

----------

Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User:Jon Witts/file-upload-v2

2010-03-13T08:53:37Z

ColinFraser:

Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?" Uploading files in Moodle is controlled both externally, within the server environment, and internally by Moodle - this is the nature of the Internet and cannot be avoided. While this page will primarily focus upon making changes in on the server environment, outside of the Moodle interface, it will also look at the changes you can make inside Moodle.

There are different web server operating systems, thus the method of increasing the uploaded file limit can be different in each. Typically this process is controlled directly by PHP, but some web server systems can override php settings.

==Basic Changes==

The fundamental changes to increase file upload sizes are simple and fairly straightforward, but unfortunately, it is not always simple or straightforward to achieve the changes required. In the php.ini file, look for these values and change them to suit your need:

upload_max_filesize = 512M
post_max_size = 512M

These values control the file upload size but can be overwritten or otherwise ignored by the Server by different methods. What follows is a far more detailed explanation of what you may actually find and how to increase the size of the files you can upload in Moodle.

==Overview==

File Upload sizes can be restricted in a number of different places. The list below shows the order of inheritance that file upload sizes follow.

#PHP Server level - [[File_upload_size|File upload size]] (which is this page)
#Moodle site level - [[Site_policies|Site Policies]]
#Course level - [[Course_settings|Course Settings]]
#Activity level - [[Adding/editing_a_forum|Adding/Editing a Forum]], [[Upload_a_single_file_assignment|Upload a Single File Assignment]] and [[Advanced_uploading_of_files_assignment|Advanced Uploading of Files Assignment]]

As you can see, it is the PHP server level that has the greatest precedence. You will need to find out where the active php.ini is located and if another program is over riding it to make changes that will work.

==Find php.ini control information==

*In PHP 4.x there must be a php.ini file in every directory that has php scripts.
*In PHP 5.x there is only one php.ini file that is active. There maybe many php.ini files on the server, but only one will effect the file upload size. You can find this file by writing a php script or using the Moodle interface.
*Some Application Programming Interface (API) servers will handle php settings differently

===Moodle php info===
In Moodle 1.7 onward, administrators run an information script by
Site administration block>Server>PHP info will run an information script.

*Server API - shows the server type
*Configuration File (php.ini) Path - show the location of the file.
*Loaded Configuration File (if there)- will over ride the above location.

===Phpinfo script===
For Moodles prior to 1.7 or on any server, you can create your own information page. Follow the instruction at [[phpinfo]] for more information.

At the very top of the phpinfo page you will see the version of PHP that your server is running.

* Loaded Modules: For example Apache2Handler
*

==What web server are you using?==
===Apache===
If you are using an Apache web server you can use .htaccess files to override the php.ini settings, or you can edit the active php.ini files on your server. Look for the API as Apache Handler. After making changes, you will have to restart your server.

===IIS===
.... edit php.ini ?! ...
===Other===
??

==How is php running on your web server?==
PHP can interact with other programs on your web server. If PHP is being controlled by an Apache Handler, you will have to restart your server. The changes will take place immediately if you are running API server using say CGI/FastCGI .

You can find out how your web server is running PHP by looking at:
*Site administration>Server>PHP info "Server API"
*phpinfo page: Apache2Handler > Loaded Modules Section.

===??===

==What access do you have to the server?==
To make changes to the main php.ini file you will need administrative access to the server...
===Local / Full access to server===
...
===Shared / Hosted access to server===
==Hosted Server==
Things can be a little different with a hosted server for uploaded and downloaded file size. You are probably going to to be told to create or change a .htaccess file, or to modify a php.ini file.

:It might be a good idea to talk to with your service provider before you attempt anything. They probably have instructions on "how to" and may have their own limits for uploaded file size. Some hosts measure the file size in gigabytes and others in megabytes. If you are unhappy with their limits, then check your contract and consider changing your provider to one that has a limit and price that you like.

===.htaccess with hosted server===
The one purpose of an .htaccess file is to override the the current limitations of both the server and the php.ini file. Your hosted server should inform you where that file needs be placed in your Moodle, but generally in the root is sufficient. They should already have a standard file in place or you can copy it from another location.

To the .htaccess file find or add the lines:
php_value upload_max_filesize 128M
php_value post_max_size 128M

This will limit uploads to 128MB, but you can make it any size you agree with your provider. The wording may vary slightly, according to the demands of the server.

===php.ini with hosted server===
Some servers will not allow you to change the moodle root .htaccess file and will tell you to use a php.ini file for php directives. The steps are basically the same as we covered above and your host will probably be running PHP 5.x
*Locate the key php file. It probably will not be located with your Moodle code.
*Using a file edit program, change the upload max and post max size in the active php file.

For example we found the following lines and the max file size is 20 megabytes.

upload_max_filesize = 20M
post_max_size = 20M

User talk:Jon Witts/file-upload-v2

2010-03-12T09:12:55Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
I certainly agree with that last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

----------

Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-12T09:11:29Z

ColinFraser: /* Comments from Colin */

==Note from Jon to Colin==
Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
Later: The question "How is php running on your web server?", to me, looks to be a loaded question, like "when did you stop beating your wife?", or an open ended question, like "how far is up?" or perhaps it is one of those golf ball questions, get a strand and it does not stop unraveling. I would suggest this is, perhaps, worthy of a page on its own. This seems to be getting into the seriously technical aspects of PHP which may not be appropriate on this page. I like the idea of an explanation, but if it is going to appear in Moodle Docs, then it had better be right, detailed enough to be accurate, and simple enough in language so most people can grasp its concepts easily. This is a hugely demanding task, and is certainly outside my abilities.--[[User:Colin Fraser|Colin Fraser]] 09:11, 12 March 2010 (UTC)

I certainly agree with that last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

----------

Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User:Jon Witts/file-upload-v2

2010-03-12T08:55:36Z

ColinFraser: /* Overview */

User:Jon Witts/file-upload-v2

2010-03-12T08:55:02Z

ColinFraser: /* Overview */

User:Jon Witts/file-upload-v2

2010-03-12T08:54:40Z

ColinFraser: /* Overview */

User:Jon Witts/file-upload-v2

2010-03-12T08:45:41Z

ColinFraser: /* Apache */

User talk:Jon Witts/file-upload-v2

2010-03-11T21:16:27Z

ColinFraser: /* Comment from Colin */

==Note from Jon to Colin==
Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comments from Colin==
I certainly agree with that last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

----------

Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-11T21:11:45Z

ColinFraser: /* Comment from Colin */

==Note from Jon to Colin==
Hi Colin,

I am editing the links as I type, and I too was thinking about the overall size and complexity of this page. What I am aiming to do with this is get a single Docs page that gives people the information needed to set their server up to allow greater file size uploads. The language and settings should transcend OS and / or web server versions; as we are dealing with either / or Apache and PHP settings; these are common across all OS.

Where we are going to run into difficulty is going to be trying to provide a document for all the hundreds of variations of ways of doing this on hosted servers. I think for these cases we need to arm the reader with enough information to take back to their hosting provider to find out how they will allow it to be done... [[User:Jon Witts|Jon Witts]] 21:24, 8 March 2010 (UTC)

==Comment from Colin==
I certainly agree with that last comment, the myriad of servers is creating a myriad of problems. This is going to mean that whatever is written has to be as generic as possible, which will not please anyone. This also has implications for the next part too.

I doubt there should be any consideration of PHP 4.x apart from the general comment that "what is included here is suitable for later versions of Moodle, post 1.7 PHP 5.x and higher." I do understand that some people are still using older versions, and are unwilling to upgrade, but at what point can they no longer be supported? We could tear our hair out arguing this, but I suggest seriously that a line be drawn and it be acknowledged that older versions are excluded. We all run into this issue, and we should be mindful of the huge changes to be made in the next major upgrade. A lot of what is being written now is going to be obsolete within the year - which will bring further challenge to what we think we should be supporting or not.

To get back on point, there is three references to finding the PHP info, suggest it be shrunk into one. One line to deal with using the PHP Infor link in Administration > Server and the other the link to the manual creation of the php info file. Oops, Late for work now.. cheers --[[User:Colin Fraser|Colin Fraser]] 21:11, 11 March 2010 (UTC)

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

==Comment by Chris==
Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

----------

Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]

==Chris jumped in==
Hi spent some time this morning with my coffee doing edits. I check some local hosts of mine from 1.6 to 1.9.7, plus looked a "popular" webhosting service that uses cpanel and another 1.9.7 production site. I ran out of time, but you can see where I am going and that I am learning some stuff.

*I have not run the phpinfo() script, but note that Moodle will give this info from 1.7 onward, so I would put the emphasis there. Jon will need to state where information is about API is and the key php.ini file.
*Not sure if we should worry about PHP 4.x but why not.
*I gather the Server API adds more potential variables, at this moment I am not sure how to treat them in an outline. My "popular" webhost uses CGI/FastCGI, they told me to set the cpanel PHP Config program to "single php.ini" and it told me the active file there. Later I saw our documentation that talked about php 5.x and one file, which meant I was messing with the wrong one :)
*My vague understanding is that Apache as an API uses .htaccess to override php.ini . However, my "popular" would not let me modify this file in the moodle code directory. I did not try to modify it elsewhere.

Best --[[User:chris collman|chris collman]] 13:17, 9 March 2010 (UTC)

User talk:Jon Witts/file-upload-v2

2010-03-11T20:59:20Z

ColinFraser: /* Comment from Colin */

User:Jon Witts/file-upload-v2

2010-03-11T20:55:42Z

ColinFraser:

User talk:Jon Witts/file-upload-v2

2010-03-08T21:06:46Z

ColinFraser:

Hi Jon,
I agree with Chris there, the placing of a link off to other pages for those elements makes sense, leads people to using the Docs a little better. This would also reduce the eventual size of this page a lot - something I have become more aware of recently as a consideration I should be making.

The main block still, I suggest, should be first and that discusses what values need be changed, with a brief explanation of how those values control the upload process possibly, and what they can be changed to. These values, I think, are constant throughout Apache/PHP environment, and I am not sure what they would be in the IIS/PHP environment. Do they retain the same names throughout all environments? What differences are there between different Linux Apache implementations? Are there differences? Or is it just a matter of different approaches to editing? Cheers. --[[User:Colin Fraser|Colin Fraser]] 21:06, 8 March 2010 (UTC)

Hi Jon,
I would put links to the list of levels (excellent) so users can view other pages.

Server level (this page)
Moodle site level (site administration block>security>site policies)
Course level (course administration block>settings
Activity level (for some activities, update activity link)
--[[User:chris collman|chris collman]] 20:44, 8 March 2010 (UTC)

Hi Chris - good idea. I will add those links in... [[User:Jon Witts|Jon Witts]]