This is an article for webmasters who use ZBlog but have no development experience. If you are an "old driver", you don't need to delay your time. Because they are often asked some basic (for developers) questions, and often cannot explain to each other in a few words, both parties are "anxious". So I want to explain some common problem troubleshooting skills as a ZBloger. I hope my friends will not waste time when they encounter problems in the future.

First of all, ZBlog will not tell you the wrong details by default, just like a girlfriend who is angry will only throw tantrums, but will not tell you why. We can Thump Open the debug mode to expose the error information thoroughly, so as to facilitate troubleshooting. Refer to the figure below for opening debugging mode

Can't understand the error message? The person without development experience may not be able to see the key points of the error at a glance, and it is not complicated to quickly understand. Generally speaking, the first line of text information (probably in English) is the cause of the error. We can use translation tools to roughly understand the problems that the program wants to tell, as shown below

Know the cause of the error, but can't solve the problem? Admittedly, friends without development experience even find it difficult to find problems, let alone solve problems. According to my past experience, most of the problems are caused by the acclimatization caused by the installation of other applications. Friends can find out from the front (top to bottom) information of the exposed errors whether there is any content prompted according to the following rules

Rule 1: zb_users/plugin/The characters here refer to the installed plug-in ID/any characters

If you find such content, you can view it on the server Zb_users/plugin/hit directory/plugin.xml File, from which you can know which plug-in threw the error, and then close the corresponding plug-in in the background to see whether the website returns to normal.

Rule 2: zb_users/theme/The characters here refer to the installed theme ID/any characters

If such content is found, you can switch to other themes in the background to test whether the website returns to normal (as shown in the figure below, the theme I used threw an error)

If the website is successfully recovered through the above troubleshooting, but cannot bypass the error itself, you can report to the corresponding author in a timely manner Submit work order Or contact feedback, you can also visit ZBlog Forum Send a post for help, and be sure to post error messages or screenshots. Of course, many problems have learned from the past. You can directly post error information to Baidu and Google for search. After all, ZBlog has been more than ten years, and common problems basically have sharing solutions, but you still need to patiently try.

Note: After solving the problem, please turn off the debugging mode in time to avoid the potential safety hazard of the website caused by the exposed information.

To sum up, if there is a website error, open the debugging mode at the first time to view the details of the error. You can view the reason by translating the error information. You can quickly detect whether the problem is caused by the plug-in or the theme by prompting the content rules. If you cannot solve it yourself, you can carry the error information to consult the author or the forum to post.