Talk:File upload size
The steps I have detailed here are tried and tested for both Windows and Ubuntu installations. I do not have access to other systems, so can not provide tried and tested ways to accomplish this on those systems. Anyone with those details, please add them to this page!
I have tried to link to all other areas of the docs that talk about achieving this; but appreciate I may have missed some. as you can see from the See Also section, this topic is addressed in lots of areas in the docs. My feeling was that whilst it was addressed in a lot of places there was no one single place with all the information in. In my mind, it would be easiest if we had one page that we could point all the other pages at, rather than the novice user having to navigate through multiple pages to find the situation that relates to their set-up.
I have marked the sections with the stub tag that need expending - please do so if you have something to add. :-)
Jon Witts 08:41, 19 September 2009 (UTC)
Thanks Jon, I have just edited the Beginning Administration FAQ to jump straight here. So much simpler and easier than what I had there. Cheers : Colin Faser 09:00 20 September 2009
Structure and content issues
Marc Grober 01:16, 20 September 2009 (UTC) Some issues.... In as much as I don't use Ubuntu, I can't comment on whether the directory structure that is mentioned in the Ubuntu install with apt-get is only created through the use of apt-get, and in any case, is that more confusing than setting out standard instructions for addressing php.ini, with exceptions identified or links to explanations elsewhere.
Bottom line is that you say your method is to be used with an Ubuntu apt-get install as I read it, but you don't mention the type of Moodle install, which would arguably totally confuse the user as to what to do..... especially if he does not understand that he needs to look in different places deending on how things are installed.... so maybe for ther ubuntu user he should have a small script which checks how things are installed and then makes recommendations as to what to do..... ahhhh, but there is an app that could be used to do this, find, so maybe we should look for php.ini, but then if changes in that file once we find it don;t work, what do we do next?
Frankly, I think it most important that users know how php.ini is sourced and how they are running php, especially in as much as one need not restart apache if one is running php as cgi.
One issue I continue to run into is well meaning folk telling people what to do without knowing how the target system is configured or is working.
In the Ubuntu case, is there always going to be an /etc/php5/apache2 directory? How is that determined (by user or by virtue of a distro specific rpm install, etc)? Doesn't your method presuppose that the user is running mod_php and what if he isn't? If there is an existing php.ini present, what put it there and shouldn't the user back up a copy before editing?
Your caveat regarding shared servers can be very confusing as many have full access though they are on a shared server.... and if users come to this page first as C says he is doing is this page simply going to confuse them even more? SHould the user work through a more robust key and if so, what are the elements of the key..... and shouldn't the key be appropriately structured, so that the user is access: do you know if you have a php.ini? go to A if you do and B if you don;t.... etc.
btw, you can have as many php.ini files as you want in a php5 installation, the issue is that php5 will only source one and it will source the first one it finds, though you could have a dozen all in legal locations that might be sourced if the system got that far...,.
____
Jon Witts 12:32, 20 September 2009 (UTC)
I thought I had stated the set-up with Ubuntu that my instructions applied too - PHP5 and Apache2 installed via apt-get and the Standard Moodle package downloaded and installed.
I think you may have a point regarding directing users to search for php.ini rather than point to exact directory structures. I will change the docs to reflect such a method. The issue here is that if PHP4 is being used there can be multiple active php.ini files - so which one do we direct them to edit? With PHP5; as you state there can be multiple ini files and only one active; so we must check which is the active one first...
If Apache2 and PHP5 are installed by apt-get, then as far as I know the locations will always be the same and PHP will be running as mod_php. The directory structure is determined by the package that apt-get downloads. This install method is the same as the one detailed in the docs page for a standard Ubuntu install.
I thing I agree regarding structure - this is still a work in progress... Let's get it right, and hopefully help more users through it.
