Hello friends,

 

 

 

 

I had this problem before when i was using older ver of wp that i cant access my plugin admin page and i see this error

 

 

 

 

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 76 bytes) in /home/webdesi1/public_html/blog/wp-settings.php on line 307

 

but now when i manually upgraded to wp 2.9.2 i even cant access my posts page i see the same error dont know what to do

Try contacting your host?

Open up your .htaccess file and insert this:

 

php_value memory_limit 64M

 

Try changing "64MB" to 128MB if it's not enough

 

Open up your .htaccess file and insert this:

 

php_value memory_limit 64M

 

Try changing "64MB" to 128MB if it's not enough

 

i already tried it it dint worked?

 

 

 

have you tried upgrading you version of php.. that may help...

or you could edit you php.ini file if your allowed access to it - not many hosting companies do...

 

if you can edit the following line...

 

memory_limit = 128M (add the line if it is missing)

failing that you could add this to the wordpress php file that's causing the error and that should help...

 

ini_set("memory_limit","24M");

<br />failing that you could add this to the wordpress php file that's causing the error and that should help...<br /><br />ini_set("memory_limit","24M");<br />

<br /><br /><br />

 

you mean wp config file?

have you tried updating this line in wp-settings.php or wp-config.php

 

define('WP_MEMORY_LIMIT', '64M');

 

try upping it to 96m

 

have you tried updating this line in wp-settings.php or wp-config.php

 

define('WP_MEMORY_LIMIT', '64M');

 

try upping it to 96m

 

 

no i tried

 

//**Increasing memory allocated to PHP**//

define('WP_MEMORY_LIMIT', '96M');

in my wp config but still same error

 

 

Had the same problem on a clients hosting.

 

Contact host, and ask for them to bump it up for you. Some hosts allow you to do it yourself by creating a php.ini file with the data and recursively saving it in every directory containing .php files by running this php script in a file (for example copyphpini.php):

 

<pre><?php system("find * -type d|xargs -i cp --verbose php.ini {}/."); ?></pre>COMPLETE!

Maybe you should just check your php.ini and increase a memory for PHP?

Had the same problem on a clients hosting.

 

Contact host, and ask for them to bump it up for you. Some hosts allow you to do it yourself by creating a php.ini file with the data and recursively saving it in every directory containing .php files by running this php script in a file (for example copyphpini.php):

 

<pre><?php system("find * -type d|xargs -i cp --verbose php.ini {}/."); ?></pre>COMPLETE!

 

 

 

but problem is i have installed wp mu on same domain although i havent posted anything there but there is no such issue there? my host is telling that there is problem in my script?

 

 

 

 

i got it solved i guess i deleted some unwanted plugins maybe i was installing too many plugins

 

 

For a blog you really shouldn't have to up that limit...

Hello,

 

If there is still issue try to contact your hosting provider ask them to increase the Rlimit value in apache.conf this will fix the memory problem.

Hello,

 

If there is still issue try to contact your hosting provider as them to increase the Rlimit value in apache.conf this will fix the memory problem.

 

Can't believe i'm hearing this from a supposed webhost...

Can't believe i'm hearing this from a supposed webhost...

 

 

Sorry I did not get your point?

supposed webhost

??

Sorry I did not get your point? ??

 

I was simply pointing out that you're a systems administrator for a webhosting company and have failed to answer the most basic of questions which could be answered simply from a Google search.

I was simply pointing out that you're a systems administrator for a webhosting company and have failed to answer the most basic of questions which could be answered simply from a Google search.

 

 

Thats the reason I updated it can be Rlimit as well.. when php.ini does not solves the memory issue of customer, mostly the problem lies on apache Rlimit setting.

 

If you are not aware of it ..Please do surf around.

 

Memory limit is not just restricted to basic php.ini setting. Many customer still face issue when you increase php.ini memory setting.

 

So please don't point fingers on others if you are unaware of live server issues.

 

 

I think you are completely unaware of Rlimit setting in apache.conf

Thats the reason I updated it can be Rlimit as well.. when php.ini does not solves the memory issue of customer, mostly the problem lies on apache Rlimit setting.

 

If you are not aware of it ..Please do surf around.

 

Memory limit is not just restricted to basic php.ini setting. Many customer still face issue when you increase php.ini memory setting.

 

So please don't point fingers on others if you are unaware of live server issues.

 

 

I think you are completely unaware of Rlimit setting in apache.conf

I am totally aware of the RLimit value in Apache as I'm actually a contributor. You're referencing a value which by default is set to use the OS default, if the OP is able to set the memory limit via local PHP scripts then it's not likely to be the Rlimit value.