-
The problem with the 500 error in this WordPress version and plugin upgrade is due to a problem with the plugin caching of the program.
I've also encountered plugin upgrade failures and WordPress version upgrade reporting 500 errors these days.
My problem is that I have WordPress super cache turned on.
If your backend has the WordPress Super Ceche plugin turned on. You can turn off the plugin and upgrade the plugin and program.
After I turned off this caching plugin, I was able to successfully upgrade the plugin and WordPress itself.
The way to close the plugin before the upgrade is to deactivate the plugin in the background.
If you've upgraded and a 500 error is broken, go to the file and put define('wp cache', true); added by wp-cache manager commented out.
It's accessible. Then the database upgrade is carried out, and after the comments are removed, the recovery starts, and it is done.
That's how the whole process is solved.
-
One-sided blockage of trees and more postures.
-
If not, then it's your theme's problem. If you have the same problem, then it is your host problem, consult your host customer service.
-
The reason for the problem is that after the WordPress program is successfully installed, it will connect to the WordPress official website, and if it can't be connected, there will be no 500 error.
So if you are a foreign host, this problem will generally not occur, and the general domestic host is prone to this kind of problem.
Then replace this sentence with **.
If you install it again, you won't have such a problem.
-
Foreword: First of all, some customers will have the problem of "http 500 internal server error" when changing the theme in the WordPress background, resulting in**500 error and unable to open in the front and back ends**, this situation mainly occurs in some hosts with low configuration, and the solution is not complicated, as follows.
The steps to workaround are as follows:
1. Tool requirements.
1)wordpress
2. In the first step, after we change the WordPress theme, there is a "http 500 internal server error" in the front and back end;
1) Then we log in to the ftp of **, find the folder of the theme we just enabled under the wp-content themes folder, and change the theme folder name to other (you can access the wordpress backend after changing the name), or directly modify the themes folder name to other.
3. The second step, we enter the [Appearance Theme] in the background, enable other themes, if there is still a problem with enabling the theme that just caused the 500 error, you can delete the theme, and re-upload it again in the "Add" of [Appearance-Theme] in the background to enable it.
1) Then if the above method of modifying the theme directory cannot solve the problem of "HTTP 500 internal server error", you can log in to the ftp of **, find the wp-content plugins folder, modify the name of the plugins folder to Other, and then visit the login **background.
4. Finally, if we can't solve the problem by modifying the wp-content themes or wp-content plugins folder, then it should be caused by the low PHP version of the server where you are **, contact your space service provider, and upgrade the PHP version to the above.
Only the article summary is displayed on the WordPress homepage. >>>More
Decisively change to centos.,CentOS is a recompiled version of rhel5.,After installation, get a NetEase's yum source rpmfusion source.,yum update can be upgraded.,It's completely free.,There's a lot of software.。
First delete the system. Command erase flash in mode (this will delete all the configurations.) del+ios file name only deletes the file. >>>More
1. First of all, you need to check the IE version of the computer and the relevant information of the computer system.
Dark-Alex has released the latest OE-A in response to a series of problems with OE-A'(a2) Upgrade the patch. Please upgrade on the OE-A system, other systems cannot use this patch. (For other versions, please install OE-A before using this patch) Update: >>>More