Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Archive /

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo

PHP memory limit problem


Go to End


11 Posts   9514 Views

Avatar
Tyssen

Community Member, 3 Posts

13 January 2007 at 7:16pm

I'm trying to test Silverstripe out on my Windows machine running XAMPP and I can't get rid of the

"SilverStripe needs a minimum of 20M allocated to PHP, but recommends 32M. You only have allocated"

error message. I've edited both php.ini and php5.ini to be 32M but it doesn't make any difference.

Any idea what I can do?

Avatar
Ingo

Forum Moderator, 801 Posts

14 January 2007 at 6:48pm

Can you confirm that the ini-change was actually recognized? You might be editing the wrong php.ini (xampp has zend optimizer enabled by default, which uses its own file). see http://www.apachefriends.org/en/faq-xampp-windows.html#phpini

Avatar
gakenny

Community Member, 153 Posts

16 January 2007 at 11:16am

Hello,

Sorry to duplicate my post. I am having a similar issue but on a Linux box running Apache. My host has increased the memory limit to 32M but this is still not being detected by the installation script.

Note that this message is not showing the current allocation:
'SilverStripe needs a minimum of 20M allocated to PHP, but recommends 32M. You only have allocated'

Cheers,

Gary

Avatar
Tyssen

Community Member, 3 Posts

19 January 2007 at 1:47am

Edited: 19/01/2007 1:48am

You were right Ingo, I hadn't modified the right .ini file. I have now, but still getting the same error message.

Avatar
gakenny

Community Member, 153 Posts

19 January 2007 at 8:59am

Hello,

I may be wrong but I believe that if the function phpinfo() does not show '--enable-memory-limit' in the configure command then this issue will prevail.

I'm not sure what additional step is required for this but I know my host has 'cracked' it and it works now.

Cheers,

Gary

Avatar
Tyssen

Community Member, 3 Posts

19 January 2007 at 2:18pm

Edited: 19/01/2007 2:21pm

I remember now why I tried installing it locally - cos I couldn't log into the demo when I first tried.

I'm in now and it all looks very impressive but unfortunately, I'm not going to be able to use it unless I change hosting company because my current one has a 10Mb memory limit set.

I'm wondering if the memory limit is going to affect how many take up this CMS?

Avatar
Enlightened_One

Community Member, 18 Posts

19 January 2007 at 4:17pm

I too am unable to get passed the PHP memory limit problem. I am using Apache 1.3.29 on OpenBSD 3.8. I have set my /var/www/conf/php.ini
memory_limit= 32M

Please advise.

Avatar
Enlightened_One

Community Member, 18 Posts

20 January 2007 at 10:30am

Edited: 20/01/2007 4:20pm

I tested the output of

echo 'memory_limit = ' . (ini_get('memory_limit') . "\n";
and I recieve a null value. Looking up the function ini_get at
###########################
http://ca.php.net/manual/en/function.ini-get.php
###########################
shows that PHP v 5.1 is required. I am running PHP v 5.04

By commenting out the line
$this->requireMemory(20*1024*1024, 32*1024*1024, array("PHP Configuration", "Memory allocated (PHP config option 'memory_limit')", "SilverStripe needs a minimum of 20M allocated to PHP, but recommends 32M.", ini_get("memory_limit")));

I was able to bypass the memory_limit test, as I know it is set to 32M

Obviously, this is not a solution. I have "worked around" this problem. I will look into a more "serious" solution later.

In the meantime, I am happy to see the message
"You're ready to install! "

In the future, I will refrain from posting to "Bugs" until I really find a "bug".

Go to Top