After the website is opened, the theme/plug-in displays the solution to the error, which is applicable to various BUGs.

Li Yang's Blog 2019-09-25 2.06 W Reading 0 Comments

Last article updated: June 15, 2022 Has exceeded six hundred and seventy-four No updates for days.

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:

 After the website is opened, the theme/plug-in displays the solution to the error, which is applicable to various BUGs. Page 1

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): After the website is opened, the theme/plug-in displays the solution to the error, which is applicable to various BUGs. Page 2

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 the website is opened, the theme/plug-in displays the solution to the error, which is applicable to various BUGs. Page 3

After opening, refresh the homepage of the website, as shown in the figure:

 After the website is opened, the theme/plug-in displays the solution to the error, which is applicable to various BUGs. Page 4

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:

 After the website is opened, the theme/plug-in displays the solution to the error, which is applicable to various BUGs. Page 5

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.

Article copyright notice: unless otherwise noted Lao Li's Notes For original articles, reprints or copies, please use hyperlinks and indicate the source.

Comment

Quick reply: expression:
 Addoil Applause Badlaugh Bomb Coffee Fabulous Facepalm Feces Frown Heyha Insidious KeepFighting NoProb PigHead Shocked Sinistersmile Slap Social Sweat Tolaugh Watermelon Witty Wow Yeah Yellowdog
Comment List (No comment yet, twenty thousand six hundred and eleven People around)

No comment yet, let me say something

 cancel
 WeChat QR code
 WeChat QR code
 Alipay QR code