|
Young
|
July 26, 2013 at 3:44 pm
Recently upgraded to 3.1.33.3.P
Did not change any settings from previous version.
Using latest version of WordPress.
Here is link to one of our events:
https://maibergerinstitute.com/events/?ee=51
Installed the “Event Espresso – Requirements Check” plugin. No error messages popped up.
===============================
In the “System Status” plugin, under Server Environment > WP Memory Limit, we have the following error:
======
WP Memory Limit 40MB – We recommend setting memory to at least 64MB
======
I reset the WP memory setting to 64 MB as instructed. PHP memory was already set to 128 MB
Yet this error is still there.
What does this error mean?
Why didn’t it change when I updated the memory?
What affect will this have on EE?
Is this something I need to worry about at all?
|
|
Josh
|
July 26, 2013 at 3:57 pm
It’s not an error. It’s a recommendation based on what we’ve seen while working on many sites. If changing the memory limit via WP doesn’t yield more memory being allocated to WP, you can check with your host, they may be setting a limit that supersedes what WP can set.
|
|
Young
|
July 26, 2013 at 4:10 pm
As I said, the host server has allocated 128 mb.
If it’s a “recommendation”, why the error message at all?
The WP memory is set at 64 mb. The host/server memory has allocated 128 mb. So this error shouldn’t be there at all, right?
Is the plugin not reading my server correctly?
|
|
Josh
|
July 26, 2013 at 4:24 pm
It doesn’t read the server. There is a constant that is defined in the wp-config.php file and the system status page checks it, and if it’s below 67108864 it displays a message that says “We recommend setting memory to at least 64MB”.
|
|
Young
|
July 26, 2013 at 4:49 pm
sooooo does that mean I should ignore it?
|
|
Josh
|
July 26, 2013 at 4:53 pm
It’s your choice, although it might be fun to see what happens if you increase the WPmemory constant value in the wp-config.php file.
|
|
Young
|
July 26, 2013 at 6:05 pm
Maybe for you.
Okay, another System Status questions. Why does it say that it can’t write a PHP session? Is this another error I need to ignore? New ticket?
|
|
Josh
|
July 26, 2013 at 6:54 pm
If it’s saying it can’t write to a PHP session there may be something misconfigured on the server’s end of things. Usually it will be either a file permissions issue -or- the session_save_path isn’t correct. This is something you can ask your host about.
|
