Since this version, security related functions have been strengthened. Login related This version no longer uses password cookies, and user passwords are no longer directly exposed. Add token cookies and force them to be in httpOnly mode. Therefore: 1. The front end is no longer allowed to set cookies for login, nor is it allowed to read password related information on the front end. 2. The front end template logout link needs to be updated. Use setcookies to simulate login

Zblog PHP system divides users into 6 levels: 1 ->administrator, 2 ->website editor, 3 ->author, 4 ->associate author, 5 ->reviewer, 6 ->visitor. Each user has different permissions. Is there any way to change the default settings of the system? It is common to modify the user's upload permission. By default, the system only has the permission to upload attachments at or above the author level. If you need to open the permission to associate authors and reviewers

Some people often complain that ZBlog's verification code is too complex, and it is always wrong to fill in it without refreshing it several times. The ZBlog system verification code is composed of letters and numbers by default. Sometimes random codes and characters are distorted together, which is really difficult to distinguish. We know that too simple verification codes are easy to be automatically recognized by machines, and too complex to be manually recognized and filled in is very bad. Is there any way to neutralize it? In fact, in addition to using plug-ins to replace, there is also a way to simplify yourself. First, you need to

First, answer: Yes! Prerequisites: 1. The application itself does not have a domain name binding and authorization mechanism, which depends on the sales strategy of the developer, and will be explained in the general introduction; 2. The purchase account is normal and not blocked due to intentional sharing with others; The Z-Blog official application center does not limit the number of websites that applications can use, so when a paid application is not allowed to be enabled, there are basically two possibilities: you do not use the corresponding purchase account to log in to the application center, or the application developer has

ZBlogPHP is unable to upload the attached image, and the main reason why the inserted image of the article is not displayed. Here, the Yiwuku directly comes to the conclusion that the directory permission is insufficient. The probability of being affected by plug-ins or having problems with the image format itself is relatively small, and these situations need specific analysis. We will not expand them here. Today we mainly talk about the problem of insufficient directory permissions. In fact, it is mentioned in the article "ZBlog Usage Tutorial: ZBlogPHP Installation Method" on this website that ZB

As all friends who have used Erjin's works know, there are few special tutorials written for both themes and plug-ins. The reason is simple, because almost every setting item of all works will be directly annotated with the corresponding text description, some will also be annotated with the title description (displayed when the mouse passes), and more complex will be explained at the bottom of the theme configuration page. Another point is not the reason. In fact, many novice users do not know how to use themes and plug-ins, but because they are new to Z -

As of the official version of 1.6.0 Valyria, the Zblog PHP program still has eight data tables by default, namely zbp_ Category classification table, zbp_ Comment comment form, zbp_ Config system and application configuration table, zbp_ Member user table, zbp_ Module module table, zbp_ Post article table (including page), zbp_ Tag tag table, zbp_

After several versions of zblog have been updated, the possibility of comments being maliciously watered in large quantities is very small, but it is an open source program after all, so the operating mechanism and principle of the code are still easy to find out the weakness, which is almost an inevitable problem for all open source programs. In addition, some webmasters neglect the management of the website, and even do not open the comment verification code. It is not uncommon to see the website once every ten days and a half months. It is inevitable that website comments will be watered down. Dozens of garbage comments even