We use PHP’s ini_get() function to retrieve this value. It should match.
Maybe you’ve updated the wrong php.ini?
Thread Starter
haemse
(@haemse)
http://php.net/manual/de/ini.core.php#ini.memory-limit
As said, i’ve set mine to “512M” in /etc/php5/apache2/php.ini
Have you restarted Apache since you made the change?
Thread Starter
haemse
(@haemse)
Yes, several times.
See for your self: https://www.enad.eu/infophp.php
Thread Starter
haemse
(@haemse)
You may need to talk to your hosting provider, we just report back what PHP’s ini_get() returns so since it’s wrong it will be beyond our ability to correct.
Thread Starter
haemse
(@haemse)
vServer KVM Debian Apache
That’s really strange!
Thread Starter
haemse
(@haemse)
Do you know where the script section is, so i can have a look at it?
The WP Statistics code is in wordpress/wp-content/plugins/wp-statistics/includes/optimization/tabs/wps-optimization-resources.php
Thread Starter
haemse
(@haemse)
Now this is interesting. If I put
<strong><?php echo ini_get('memory_limit'); ?></strong>
into a .php file the value will adjust according to the main php.ini file after apache restart.
But the value in the wp statistics resources table will absolutely not change – no chance.
I changed the value in all my php.ini files on the system (3) and also the suhosin.memory_limit value – but still no chance.
Also cleared browser cache each time. Isn’t that strange?
Very strange. Something must be cached somewhere.
Your not using a caching plug are you?
Or eAccelorator?
Thread Starter
haemse
(@haemse)
No, none of them … 😐
Thanks for your interest in that issue!
BTW: wouldn’t it be kind of nice to load the statistics content dynamicly? Quicker, easier, cleaner …
That’s very strange. I wonder if another plugin is messing with the value for some reason. Two things you might want to try:
1. Temporarily disable your other plugins
2. Grab http://thisismyurl.com/downloads/wordpress-phpinfo/ and see what php_info() reports from within WordPress.
Dynamic loading is none of those things 😉 It’s slower (multiple connections back to the servers), harder (lots of javascript and server side code to support it) and messier (a whole new layer of code to go wrong).
Same here. From phpinfo():
memory_limit 128M 128M
Reported by WP-Stats:
PHP Memory Limit: 256M
The server is mine, fresh WP install, no cache-ing, no interference with other plugins.
We pull the value through PHP, so if it’s being reported incorrectly we have no control over it.
