i do not know php but had installed wordpress, i visit my site and see the following error
Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 98304 bytes) in E:\Domains\mysite.com\wwwroot\wp-content\plugins\wordfence\lib\wfLog.php on line 431
PHP Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 98304 bytes) in E:\Domains\mysite.com\wwwroot\wp-content\plugins\wordfence\lib\wfLog.php on line 431
how do i fix hat above, please guide
You have a plugin called Wordfence which is causing the problem. It appears to be overloading your memory. I wouldn't mess with your server config, the problem is with the plugin. Try deleting those logs, that should work, but it may only be a temporary solution. Removing the plugin would certainly solve the problem. No idea what Wordfence is though. If that doesn't work, change the title of your question to include "Wordfence plugin".
In my opinion i have got a better solution for you. All you need to do is just to increase memory size.
By default, when you installed and configure Wordpress it comes by 16MB memory . In your case, you can keep the plugin you already installed and add the following one line code to your wp-config.php file.
You can access this file via FTP(File Transfer Protocol) client FileZilla or from your hosting cPanel.
/* Increase memory */
code : define( 'WP_MEMORY_LIMIT', '96M' );
Related
I have recently installed this page builder plugin and started using it but it returned an error:
Fatal error: Allowed memory size of ---- bytes exhausted (tried to allocate ---- bytes) in --
Is there any thing I can do about this? I have search here and could not find suitable answer related to wordpress page builder.
This error is due to the PHP memory limit. Your WordPress needs more memory in order to complete the task. You will need to edit your wp-config.php file in your public_html (or root of your WordPress) and just after this line in your wp-config.php
/* That’s all, stop editing! Happy blogging. */
Add this and save the file.
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
Now try again.
Source: https://www.webxen.com/kb/wordpress-fatal-error-allowed-memory-size-of-67108864-bytes-exhausted/
I am a WordPress beginner and I have only rudimentary knowledge about CSS and HTML. I have built a WordPress blog in the last days, and it was working well. But since two days I couldn't login and couldn't open the page (but I haven't touch the page since about one week, I don't know what happened). This is what was shown:
Fatal error: Allowed memory size of 50331648 bytes exhausted (tried to allocate 30720 bytes) in /home/u0087038969/public_html/wp-admin/includes/deprecated.php on line 533
I suggested that one of the installed plugins caused this trouble. That's why I changed the name of the plugin file via FileZilla, so that I get access to WordPress again. Then I tried to reactivate the plugins gradually to find the trouble-maker. Still it's not really working. What can I do to go about solving the problem?
p.s. I used the following wp plugins: mail poet, all in one seo and contact form 7.
The problem is your installation is requiring more memory than you have available for your site. If you are using a shared hosting environment, you might be at a loss in increasing your memory allotment.
Try updating your wp-config file:
define('WP_MEMORY_LIMIT', '256MB');
If you can change your PHP.ini file you can adjust this:
php_value memory_limit 256MB
Your host seems to have this set incredibly low if it's giving you a memory error at 50MB.
I ran into this rather annoying issue the other day; when a page tries to load it will just 'stop' half way through returning half a page to the end user. The exact error is shown below.
[03-Jul-2015 03:15:04 Europe/London] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 18996 bytes) in [path]/concrete/vendor/imagine/imagine/lib/Imagine/Gd/Image.php on line 602
I spoke to my host and they bumped up PHP's memory to 512M (which is a bit overkill) yet it still throws this error. I'm not sure if it's a memory leak in Concrete5 somewhere or if it is just the server that the site is hosted on.
Any suggestions are much appreciated.
Edit: Forgot to mention I'm running 1.7.4.2
Edit 2: For reference the exact function is imagecreatetruecolor()
Either:
ini_set('memory_limit','256M');
Inside PHP or getting your host to bump up the memory limit will do the trick.
I'm currently running Joomla 1.5.8 on a live server. I can only make certain changes to the website such as text content updates in articles. However any modification to a module returns this titles error with error reporting on.
Without it returns a generic Server Error 500.
I've tried changing the permissions of alot of different folders and have tried to manipulate the htaccess file as well but I still have had no luck. I did not setup the site originally and have been brought into this project with functioning features already existing, I just cannot make any changes to them or new ones.
Full error is: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 1048576 bytes) in /var/www/vhosts/mydomain/httpdocs/libraries/joomla/filesystem/file.php on line 147
Try setting
ini_set('memory_limit', '-1');
I'm working on a wordpress website and I'm attempting to set up a local test-environment for development purposes. I'm running the MAMP (Mac Apache MySQL PHP) stack.
I'm running into the following error:
Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 4864 bytes) in /Users/casey/Documents/workspaces/yofreesamples.com/wp-includes/functions.php on line 1174
I've attempted to increase the memory limit by modifying line 28 in wp-config.php:
define('WP_MEMORY_LIMIT', '2024MB');
and by including the following value in index.php
ini_set('memory_limit','64M');
without any luck for any memory values I've tried. I'm relatively new to wordpress, anyone have any idea what's going on?
Perhaps the MAMP configuration doesn't allow you to override the memory limit programmatically. Set it in php.ini as described here.