In the previous and after the speech submission was successfully submitted, they jumped to a page called post_end.php. This page mainly prompts that the speech submission was successfully submitted and gave a link to it. The program is very simple, so I wrote it together:
<html>
Your statement has been submitted<br>
<a href="">Return to the homepage of difficult problems</a>
</html>
In this section, we will focus on the eight functions that are missing in this forum that we listed at the beginning:
1. In my forum, you can only speak after the user logs in. The user's ID exists in a cookie variable called "cookie_user".
I think this should not be the main content of the forum program. There are many very complete programs for reference regarding user login. If you want your forum program to be more complete, you can consider adding a user login module to it. You can also consider automatically helping the user register when the user logs in for the first time.
2. My forum has no sub-forum.
In fact, this must add a field id_style in the data table guestbook to indicate the id of the subforum to which it belongs. In addition, you'd better design a data table called bm_style, which contains two fields: style_code (subforum encoding), style_name (subforum name), and the field id_style in the guestbook should store the subforum encoding.
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, and accumulate it in it.
4. I have not designed the icons in front of each topic in the OSO forum that indicate whether there are new posts.
Record the last time the user reads a post in the user's cookie, and then use this time to compare it with time_close. If time_close is greater than this value, the topic is identified as having a new post.
5. I didn’t consider the optional theme arrangement and display time period provided by the OSO forum.
Give the user a drop-down list box for selection, and change the content of the select statement order clause according to the arrangement method selected by the user, and add the where clause according to the display time period selected by the user.
6. No statistics on the points posted by members.
Add the point field to the my_user table, set an initial value when registering, and add the corresponding points in the as well.
7. There is no function of moderator management forum.
Add a type field to the my_user table and indicate the user type. For users with type moderators, you can enter a management interface and perform delete operations on the guestbook data table.
8. There is no function of post editing.
For the user's own post (that is, the name in the guestbook and the name in the cookie are the same), the user can be allowed to perform the corresponding update operation on it.
At this point, all this essay has ended. If there are any shortcomings, please criticize and correct me. The ones involved in the suspected plagiarism of OSO (interface part). I would like to thank all OSO comrades.
[The copyright of this article is jointly owned by the author and Aoso.com. If you need to reprint it, please indicate the author and source]
<html>
Your statement has been submitted<br>
<a href="">Return to the homepage of difficult problems</a>
</html>
In this section, we will focus on the eight functions that are missing in this forum that we listed at the beginning:
1. In my forum, you can only speak after the user logs in. The user's ID exists in a cookie variable called "cookie_user".
I think this should not be the main content of the forum program. There are many very complete programs for reference regarding user login. If you want your forum program to be more complete, you can consider adding a user login module to it. You can also consider automatically helping the user register when the user logs in for the first time.
2. My forum has no sub-forum.
In fact, this must add a field id_style in the data table guestbook to indicate the id of the subforum to which it belongs. In addition, you'd better design a data table called bm_style, which contains two fields: style_code (subforum encoding), style_name (subforum name), and the field id_style in the guestbook should store the subforum encoding.
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, and accumulate it in it.
4. I have not designed the icons in front of each topic in the OSO forum that indicate whether there are new posts.
Record the last time the user reads a post in the user's cookie, and then use this time to compare it with time_close. If time_close is greater than this value, the topic is identified as having a new post.
5. I didn’t consider the optional theme arrangement and display time period provided by the OSO forum.
Give the user a drop-down list box for selection, and change the content of the select statement order clause according to the arrangement method selected by the user, and add the where clause according to the display time period selected by the user.
6. No statistics on the points posted by members.
Add the point field to the my_user table, set an initial value when registering, and add the corresponding points in the as well.
7. There is no function of moderator management forum.
Add a type field to the my_user table and indicate the user type. For users with type moderators, you can enter a management interface and perform delete operations on the guestbook data table.
8. There is no function of post editing.
For the user's own post (that is, the name in the guestbook and the name in the cookie are the same), the user can be allowed to perform the corresponding update operation on it.
At this point, all this essay has ended. If there are any shortcomings, please criticize and correct me. The ones involved in the suspected plagiarism of OSO (interface part). I would like to thank all OSO comrades.
[The copyright of this article is jointly owned by the author and Aoso.com. If you need to reprint it, please indicate the author and source]