Updating website using ftp with wordpress
Open your root directory, and locate your Save the file, and re-upload it to your root directory, overwriting the original file. If you still see the error, you are not having PHP memory limit issues. Increasing your site’s PHP memory limit in the file is the equivalent of pouring bleach down your kitchen sink when it smells like rotten eggs.
Remove the above code from the file on your computer, save it, and re-upload it to your root directory. You’re fixing the problem well enough to get rid of the offensive odor, but you’re not fixing the bigger issue at hand, which is likely a clog somewhere in the pipes that lead to your sink.
The same is true with increasing your site’s PHP memory limit.
You may have increased it yourself in the file, but something is still exhausting your limit.
You can follow the steps in the next few sections to try and find out what that might be, but if worst comes to worst, you’ll likely need to convince your host to increase the limit on your server.
Open the root directory, and open the folder to anything you wish, such as “plugins.test”. Activate each plugin one by one, refreshing your site after each activation, to find out which plugin is causing the error.This essentially deletes your site’s .htaccess file, so we need to create a new one. It’s also worth mentioning that an improperly named .htaccess file will cause this error to run on your site.Make sure this file is not named anything other than “.htaccess”.But we’re going to try to help alleviate some of that stress by suggesting several solutions to this problem and walking you through each. These solutions require making a lot of changes in your site’s root directory.It’s highly recommended you backup your site prior to trying any of these solutions in case something goes wrong.
Search for updating website using ftp with wordpress:
The .htaccess file in your Word Press directory can become corrupted after you install a plugin or make another change to your Word Press site. You’ll begin to exceed the PHP memory limits set by your hosting provider once either of these things happen. We’re going to learn how to create a new .htaccess to get rid of the corrupted one as well as how to test whether or not you’re exceeding your PHP memory limits. If the 500 internal server error is gone, it was caused by a corrupted .htaccess file and your issue is now fixed.