Wednesday, January 21, 2009

Php core configuration memory_limit

 
 
 
  1 Question by You Jan 15, 2009 at 04:50 PM (5 days 8 hours ago)

edit message
view raw message

Hi, good day, I am having a problem with the php memory_limit.

One of my sites is running in a subdirectory of my root directory(public_html). Say it's running in directory public_html/siteone/ . I am wondering How could I make the subdirectory "siteone" have the same "memory_limit" as the root directory "public_html". I ran phpinfo.php in both directories. For the "public_html" I got 128M memory_limit, for the "public_html/siteone/" I got only 32M memory_limit.

Is there anyway that like put a .htaccess and php.ini file in the related directory to make this work, to make the subdirectory, and sub subdirectory to work in higher memory_limit. Thanks a lot for your time, I look forward to hearing from you.

Kind regards,

Alan

 

 

  2 Response by Danny Nolan Jan 15, 2009 at 05:34 PM (5 days 7 hours ago)

view raw message

Hello,

Please insert the following code in your .htaccess:

suPHP_ConfigPath /home/username/public_html/

where "username" is your cPanel username.

In your php.ini file, please add the following lines of text:

upload_max_filesize = 10M
post_max_size = 10M
max_execution_time = 120
memory_limit = 64M

Both files should be in your root public_html folder, if either of the files is not present, go ahead and create it.

--

Please do not hesitate to contact us for further assistance or if you have any other questions.

--

Dan Nolan
CSR 1

--

Support Forums - http://www.lunarforums.com/ Help Desk - https://support.lunarpages.com/ Tutorials - http://www.lunarpages.com/content/tutorials/ Know Base - https://support.lunarpages.com/knowledge_bases Packages - http://www.lunarpages.com/solutions/

support@lunarpages.com Telephone: 1-714-521-8150
Fax: 1-714-521-8195
24 hour Network Status Line: 1-562-697-8106

  3 Response by You Jan 16, 2009 at 12:16 AM (5 days 51 minutes ago)

edit message
view raw message

thanks a lot it's fixed

0 comments: