Your site is capped at 64MB. 67108864 = 64MB.
Thanks Kurt, what should i do about that?
Do you mean that the php.ini may not be working?
It appears php.ini isn’t working.
You can try editing wp-config.php to raise the memory limit:
http://codex.ww.wp.xz.cn/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
define( 'WP_MEMORY_LIMIT', '256M');
define( 'WP_MAX_MEMORY_LIMIT', '384M');
Thanks for the answers, I have now found the issue, which may be helpful for some people.
When changing the memory limit in php.ini I found that there also had to be a link to the php.ini in .htaccess:
Without this, or unless the path is correct, the php.ini raisid limit shows correctly in a phpinfo.php, but still does not allow the increased amount to WordPress
which i discovered with the plugin: WP-Memory-Usage
The .htaccess needed this:
suPHP_ConfigPath /data01/taming/public_html/php.ini
This plugin is only compatible up to 3.5, if you are using 3.9 (the latest version of WordPress) it is probably not a good idea to use this plugin as per the WordPress guidelines.
P3 (Plugin Performance Profiler)
Requires: 3.3 or higher
Compatible up to: 3.5.2
Last Updated: 2012-12-6
🙂
Hi greataussiepie,
P3 is definitely compatible with 3.6, 3.6.1, 3.7, 3.7.1, 3.7.2, 3.7.3, 3.8, 3.8.1, 3.8.2, 3.8.3, and 3.9. I have been avoiding releasing a new version just to update the readme file.
You can see user submitted plugin compatibility information on the P3 page on the lower right-hand side. 3.9 is currently marked as 3 “yes” and 0 “no”
That said, there’s an update pending you’re welcome to try here:
http://downloads.wp.xz.cn/plugin/p3-profiler.zip
It will be 1.5.0 and it’s pending some more thorough testing on different hosts, web servers, versions of php, etc.
You’re welcome to browse the changes since 1.4.1 here:
https://plugins.trac.ww.wp.xz.cn/changeset?sfp_email=&sfph_mail=&reponame=&new=905828%40p3-profiler&old=635099%40p3-profiler&sfp_email=&sfph_mail=
Please let me know if you have any questions or if you find any features that do not work.
Ok cool, thanks for letting us know Kurt, will submit feedback when i try this out 🙂
I’m glad to know it’s up to date and that you don’t keep doing updates just for the sake of it.
As mentioned, the issue was connected with the php.ini not working due to incorrectly configured .htaccess and not apparently due to this plugin, it just happened to be the one I reactivated that tipped the memory of 64MB.
It is now working fine on 3.8.3
