The title party blamed me??? The main purpose of this article is not really to solve all problems, but to make them specific, as follows course Operation, feedback the error code of the website to the subject/ plug-in unit And wait for the solution.
First, check the error displayed after the website is opened under normal conditions, as follows:
Yes, it's such a simple picture. Without specific code, Xiaobai may be confused. What's the reason? What's going on? In fact, we can simply set the website to display errors in a more specific way, and then throw it to the developer.
On the home page, open the website settings, global settings, and then find the development mode as shown in the figure, and open it (on is open):
PS: zblog When PHP is upgraded to 1.7+, the developer mode is no longer displayed, but the "debug mode" is changed. Of course, the warning level error is allowed, as shown in the figure below:
After opening, refresh the homepage of the website, as shown in the figure:
See, the specific error code and the location of the file error are all displayed. Next, just throw the screenshot to the theme or plug-in developer.
Now that we've talked about this, let's say by the way that we can distinguish between themes and plug-ins, as shown in the figure,/zb_user/cache/compiled/briefflee/, where brielflee is the ID name of the theme. How can we distinguish plug-ins? See the picture:
The location in the figure is/zb_users/plugin/CommentUA/, where/plugin/is the directory of the plug-in, and/CommentUA/is the ID of the plug-in. In fact, it is very simple. Just check whether/zb_user/is followed by/plugin/. If yes, it is a plug-in problem, and if not, it is basically an error caused by the theme.