Forum 5 that imitates OSO_PHP tutorial

In the previous post.php and reply.php, after the speech is submitted successfully, it jumps to a page called post_end.php. This page mainly prompts that the speech is submitted successfully and gives a link to faq.php. The procedure is very simple, I will write it down below:

Your statement has been submitted
Return to the troubleshooting home page

In this section, we We will focus on how to implement the eight functions we listed at the beginning that this forum lacks:
1. In my forum, users can only speak after they log in. The user's ID is called "cookie_user" in the cookie variable.
I think this should not be the main content of the forum program. Regarding user login, there are many perfect programs for reference. If you want to make your forum program more complete, you can consider post.php and reply. Add a user login module in php. You can also consider automatically registering users when they log in for the first time.
2. My forum has no sub-forums.
In fact, you must add a field id_style to the data table guestbook to indicate the id of the sub-forum to which it belongs. In addition, you'd better design a data table named bm_style, which contains two fields: style_code (sub-forum) Forum code), style_name (sub-forum name), and the field id_style in guestbook should store the sub-forum code.
3. I did not count the number of clicks on a topic.
Add a field count_read in the data table guestbook, set its initial value to 1 in post.php, and accumulate it in read.php.
4. I did not design the icon in front of each topic in the OSO forum to indicate whether there are new posts.
Record the time when the user last read a post in the user's cookie, and then compare this time with time_close. If time_close is greater than this value, mark the topic as having a new post.
5. I did not consider the optional topic arrangement and display time period provided by the OSO forum.
Give the user a drop-down list box to choose from, change the content of the order clause of the select statement in read.php according to the arrangement selected by the user, and add a where clause according to the display time period selected by the user.

6. There is no statistics on points posted by members.
Add the point field to the my_user table, set an initial value when registering, and add corresponding points to post.php and reply.php.
7. There is no function for moderators to manage the forum.
Add the type field to the my_user table and indicate the user type. Users whose type is moderator can enter a management interface and perform delete operations on the guestbook data table.
8. There is no post editing function.
For the user's own posts (that is, the name in the guestbook is the same as the name in the cookie), the user can perform corresponding update operations on it.
This is the end of this exercise. If there are any shortcomings, I would like to ask all experts to criticize and correct them, including those that are suspected of plagiarism from OSO (interface part). I would like to express my gratitude to all OSO comrades.
[The copyright of this article is jointly owned by the author and Oso.com. If you need to reprint, please indicate the author and source]