Fatal Error call to undefined function WP raise memory_limit() in WordPress
Fatal Error in WordPress

In WordPress sometimes you may face a common issue called “Fatal Error call to undefined function wp raise memory_limit()”. It comes generally when we transfer/upload files to hosting.

Below are the steps to resolve the issue:-

    • First of all, you have to download the latest WordPress zip file.

Fatal Error call to undefined function wp raise memory_limit() in WordPress

  • Unzip the downloaded file.
  • Next, keep a backup file of your WordPress.
  • Now, rename the wp-admin and wp-includes folders to wp-admin.temp and wp-includes.temp through cpanel or FTP.
  • Upload new wp-admin and wp-includes folders to your WordPress root directory.
  • Now, upload the latest version of the rest of the files to your root directory except wp-config.php and wp-content folder.
  • Delete the .maintenance file from your WordPress root directory through FTP.
  • Now, open your WordPress site. The database update request is available now.
  • Click on the database update.

Now, your WordPress will work properly without the fatal error: wp raise memory_limit().

We hope this article put an endpoint for your WordPress Error. Now, you have known how to fix Fatal Error: function wp raise memory_limit() in WordPress and how to update WordPress version easily. Here we provide easy and simple ways for solving WordPress Theme Errors.

For any query, contact us or email us to [email protected].

Error 406 in Wordpress Site
How to Fix Error 406 in WordPress Site
Resolution for Error 406 in WordPress Site/Not Acceptable

Sometimes we get Error 406 in our WordPress site and below solution helps most of the time.

We see “406 not acceptable error” largely due to restrictions on the web server.

Most web hosts install a program called “ModSecurity” to protect the web server from malicious actors like spammers, hackers etc.

ModSecurity generally block malicious requests to the web server with a “406 not acceptable error”. But often it blocks legitimate requests as well.

Recently in one of the VPS server that we manage, we saw ModSecurity blocking a genuine request. On trying to Publish a WordPress post, website owner was presented with the error.

To fix the error, our Support Engineers analyze the ModSecurity logs and that helps to identify the exact rule that caused the block.

If the request from browser is genuine and ModSecurity wrongly blocked it, we disable this particular rule for the domain.

When selective disabling of rules do not work, the only option left is to Turn OFF ModSecurity completely for the domain.

In cPanel servers, there is an option to do this from the cPanel of the domain.

First of all take backup of your .htaccess file (If you are in linux hosting make sure you have checked “show hidden files” by going to site settings ( in cpanel). If there is no .htaccess file then create one and paste below code and save it.

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress

Hope this will help.Happy coding.


About Us

We create experiences that change the way people interact with brands – and with each other