PHP Code for Delete Reply in Database
Content Management System: Blogs
- regular blog: home page
- small blog: home page
- tiny blog: home page
- blog: search
- blog: login
- blog: topic and replies viewing page
- blog: add topic to database
- blog: add reply to database
- blog: edit topic in database
- blog: create topic in database
- blog: delete topic in database
- blog: delete reply in database
- blog: create categories in database
- blog: edit categories in database
- blog: open or close topic
- blog: delete user account in members table
The blog's reply deleting page whose code is on this web page is very simple. If your username matches the administrator's username, the replies table is consulted, and the topic which has the reply to delete has its id learned from a PHP GET statement and the reply id is also learned from a PHP GET statement, and the reply that has the a_id that belongs to this reply and the question_id that is this topic's id is dumped from the replies table of the MySQL db using the SQL DELETE FROM command.
On to the PHP code. As usual, we start with config.php, since without it, the MySQL-based blog would not be viable. You cannot relate to a db without knowing the magic words. Next, the security of the page is dealt with by ensuring the page visitor has the administrator's username. Note that the various pages on our blog app use both forms and URL query strings to transfer data between pages, so both POST and GET are checked for username, and if neither works, the visitor is sent to the login script. Not only is the username checked to ensure it is the administrator's username, the username is checked to make sure it has only 6 to 20 letters, numbers or underscore in it and no other characters—otherwise, it's off to the login script. If a hacker has put something nasty in the query string, he'll end up at the login script. All our blog app scripts have this same (almost) username checker at the top of the PHP section—except for the login script. We say "almost" because most pages (like this one) only allow the administrator access because most pages are about adding, deleting, or editing topics, replies, or categories. So, seeing if the username is the administrator's is in the user checker on most of these blog app pages.
The administrator's username is a bit silly, as you see. Feel free to change it (to AfDqC_1f3_DkI3j5k9N_ for example) when you register the administrator username and password, but you must use search and replace on ALL blog app pages searching for our silly name and replacing it with your not-as-silly name or you'll have more problems than a pregnant nun.
Next comes GETting the topic id and reply id gotten from the URL query string that brought us to this reply deleting page. Depending on which reply's Delete Reply link is clicked on the topic and replies viewing page, its corresponding reply id number and topic id number will be sent via query string (along with the username) to this blog reply deleting page and only this one reply will be vulnerable to deletion.
Finally, if your username matches the administrator's username, you'll be let into the script, and the reply, whose topic id is learned from a PHP GET statement and whose reply id is learned from a PHP GET statement, is dumped from the replies table, named blog_answer. The mysql_affected_rows() function finds out if deletions have occured and you get a message regarding the success or failure of this operation.
SAVE THIS PAGE AS: cms-delete-blog-answer.php
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
<TITLE>Delete Blog Reply—Content Management System (CMS)</TITLE>
<meta name="description" content="Delete Blog Reply—Content Management System (CMS)">
$sql="DELETE FROM $tbl_name WHERE question_id='$id' AND a_id='$aid'";
$result=mysql_query($sql) or die('Error ,deleting failed');
$rc = mysql_affected_rows();