Hi,
Should I manually configure config.php as by default there is config-dist.php and I renamed it to config.php but now I need to update many paths in it in order to enalbe,
Should I manually configure config.php as by default there is config-dist.php and I renamed it to config.php but now I need to update many paths in it in order to enalbe,
ini_set ('display_errors', 'on');
ini_set ('log_errors', 'on');
ini_set ('display_startup_errors', 'on');
ini_set ('error_reporting', E_ALL);
as yet my config.php is not created so I can't put these lines there. Pl guide. thanks
SH,
I see from your php info file that you are using PHP version 5.2.3. That's good. That's the latest major version (5.2). That also tells me you only have one active PHP configuration file (php.ini). The php info file also tells me where it is: C:\PHP\php.ini. This would seem to suggest that the server is yours (not a commercial web host) and that you should have access to that file. So you should be able to edit php.ini to enable the four settings you mention in your latest post.
Editing config-dist.php and saving it as config.php is usually a last resort, as an alternative to allowing the Moodle installation script (install.php) create config.php. You should not have to do that at this point. But you will need to rename it back or else the installation script won't run.
EDIT: I just looked at the instructions at http://docs.moodle.org/en/Installation_FAQ#How_to_enable_and_check_PHP_error_logs
that tell you to use those ini_set statements. That must be why you were trying to manually create config.php. These instructions will need to be clarified, but I suspect that they do not apply at this point since config.php has not been created yet. So I would try just editing php.ini and try running the installation script again (with config.php renamed back to config-dist.php as I said above). If that doesn't work, I would try temporarily adding the ini_set statements to the beginning of install.php in the main Moodle folder where config-dist.php is, between the line that says
/// If config.php exists already then we are not needed.
and the one that says
if (file_exists('./config.php')) {
When you have found the problem and fixed it, you can delete the ini_set lines that you added, or comment them out by putting "// " at the beginning of each of those lines. Alternatively, you could make a copy of the install.php file in another folder (directory) before adding the lines, and afterwards copy it back.
If that doesn't work, then I guess you will have to use config-dist.php as you had planned to do after all, but I would be very surprised if it comes to that. Please let us know which of these methods works best, so we can clarify the instructions properly.
RLE
I see from your php info file that you are using PHP version 5.2.3. That's good. That's the latest major version (5.2). That also tells me you only have one active PHP configuration file (php.ini). The php info file also tells me where it is: C:\PHP\php.ini. This would seem to suggest that the server is yours (not a commercial web host) and that you should have access to that file. So you should be able to edit php.ini to enable the four settings you mention in your latest post.
Editing config-dist.php and saving it as config.php is usually a last resort, as an alternative to allowing the Moodle installation script (install.php) create config.php. You should not have to do that at this point. But you will need to rename it back or else the installation script won't run.
EDIT: I just looked at the instructions at http://docs.moodle.org/en/Installation_FAQ#How_to_enable_and_check_PHP_error_logs
that tell you to use those ini_set statements. That must be why you were trying to manually create config.php. These instructions will need to be clarified, but I suspect that they do not apply at this point since config.php has not been created yet. So I would try just editing php.ini and try running the installation script again (with config.php renamed back to config-dist.php as I said above). If that doesn't work, I would try temporarily adding the ini_set statements to the beginning of install.php in the main Moodle folder where config-dist.php is, between the line that says
/// If config.php exists already then we are not needed.
and the one that says
if (file_exists('./config.php')) {
When you have found the problem and fixed it, you can delete the ini_set lines that you added, or comment them out by putting "// " at the beginning of each of those lines. Alternatively, you could make a copy of the install.php file in another folder (directory) before adding the lines, and afterwards copy it back.
If that doesn't work, then I guess you will have to use config-dist.php as you had planned to do after all, but I would be very surprised if it comes to that. Please let us know which of these methods works best, so we can clarify the instructions properly.
RLE
Hi,
Thanks for such a detailed reply. Well let me clear few things,
1- It is not my server but a shared hosting and the hosting guys said that they have placed the php.ini in my root folder so will that help?
2- My setup is on windows, IIS, Mysql and PHP. Someone told me that I must use LAMP?
3- The hosting guys replied that "The memory requirements of this software is unbelievable and not feasible in a shared hosting environment. 1GB of memory per 50 users???"
Waiting for guidance. thanks
Thanks for such a detailed reply. Well let me clear few things,
1- It is not my server but a shared hosting and the hosting guys said that they have placed the php.ini in my root folder so will that help?
2- My setup is on windows, IIS, Mysql and PHP. Someone told me that I must use LAMP?
3- The hosting guys replied that "The memory requirements of this software is unbelievable and not feasible in a shared hosting environment. 1GB of memory per 50 users???"
Waiting for guidance. thanks
SH,
- That depends on whether they have made it the active php.ini. Ask the hosting guys whether, if you make changes to that file, will they be recognized by PHP? If not, you will have to have them copy the file after you edit it back to C:\PHP. But then that file is probably shared by all their users, so that's not going to happen. In that case, since you are using IIS and not Apache, you can't use .htaccess instead. Looks like you will need to use those ini_set statements. Put them in install.php as I described before.
- Who is requiring you to use LAMP? Because it certainly isn't Moodle. Moodle can run on LInux, Unix, Mac, Windows, and Netware systems, at least. It can use Apache or IIS and maybe others. It can use three other database servers besides MySQL. See http://docs.moodle.org/en/Installing_Moodle#Requirements
- I know that Moodle is being used in shared hosting environments, although it probably is not suitable to be run that way if you have a very large school. The docs (see #2 above) say 1 GB per 50 concurrent users, i.e., you need that much memory if you expect 50 users to be accessing your site at the same time.
SH,
Aside from the standard answer (Moodle Partners), which is for those with more money than they know what to do with, I have accumulated over the centuries a number of links to discussions on that subject in this forum (and other link(s)):
http://moodle.org/mod/forum/discuss.php?d=42688
also http://moodle.org/mod/forum/discuss.php?d=74789#p341332
http://moodle.org/mod/forum/discuss.php?d=80523#p357343 (former 1and1 cust.)
http://moodle.org/mod/forum/discuss.php?d=85344#p378170
http://tracker.moodle.org/browse/MDL-11743
http://moodle.org/mod/forum/discuss.php?d=64066#289234
http://moodle.org/mod/forum/discuss.php?d=66651#p299941
http://moodle.org/mod/forum/discuss.php?d=66651#p304553
http://moodle.org/mod/forum/discuss.php?d=67930#p305566
http://moodle.org/mod/forum/discuss.php?d=67930#p305577
http://moodle.org/mod/forum/discuss.php?d=74789#p341281 (anti-Siteground)
RLE
Aside from the standard answer (Moodle Partners), which is for those with more money than they know what to do with, I have accumulated over the centuries a number of links to discussions on that subject in this forum (and other link(s)):
http://moodle.org/mod/forum/discuss.php?d=42688
also http://moodle.org/mod/forum/discuss.php?d=74789#p341332
http://moodle.org/mod/forum/discuss.php?d=80523#p357343 (former 1and1 cust.)
http://moodle.org/mod/forum/discuss.php?d=85344#p378170
http://tracker.moodle.org/browse/MDL-11743
http://moodle.org/mod/forum/discuss.php?d=64066#289234
http://moodle.org/mod/forum/discuss.php?d=66651#p299941
http://moodle.org/mod/forum/discuss.php?d=66651#p304553
http://moodle.org/mod/forum/discuss.php?d=67930#p305566
http://moodle.org/mod/forum/discuss.php?d=67930#p305577
http://moodle.org/mod/forum/discuss.php?d=74789#p341281 (anti-Siteground)
RLE