guest_post()函数工作机制咨询及PHP数据库操作输出显示问题

Hey there, let's break down your two issues step by step to get things sorted out.

一、关于guest_post()函数的工作原理与输出问题 #

First off, let's cover what a typical guest_post() function does—most often, it's a custom function built to handle visitor-submitted content (like comments, guest articles, or form entries). The standard workflow usually looks like this:

• Receives form data submitted by the user (e.g., title, content, author details)
• Validates the input (checks for empty fields, correct formatting, etc.)
• Saves the data to a database or processes it further
• Returns or renders a result (success/failure message, or the submitted content for display)

Since you mentioned an output display issue (and referenced an attached image), here are the most common culprits to check:

• Truncated output: This might happen if your database has a character limit on the relevant field, or if you're not handling line breaks/special characters correctly when rendering the content.
• No output at all: Double-check if the function's logic is actually triggering (e.g., is the form submission being detected correctly?) or if a database write failure is silently stopping the process without returning a message.
• Garbled text (encoding issues): Make sure the page's character encoding (usually UTF-8), your database's encoding, and the function's data handling all use the same standard. Mismatched encodings will cause weird text display.

二、排查sqltest.php中的DELETE操作问题 #

Let's start by looking at your incomplete code snippet first, then walk through the issues:

Your Current Code Snippet #

<?php 
//sqltest.php 
//Part 01 - The first part of the code will establish connection with DB using mysqli method 
require_once 'login.php'; 
$conn = new mysqli($hn,$un,$pw,$db); 
if ($conn->connect_error) die ($conn->connect_error); 

// Part - 02 - Here is the method to delete some data using query by taking input and later checking using isset 
if (isset($_POST['delete']) && isset ($_POST['isbn'])){ 
    $isbn = get_post($conn,'isbn'); 
    $query ="DELETE FROM classics WHERE isbn =...

Key Issues & Fixes #

1. Incomplete SQL Statement
   Your DELETE query cuts off mid-way. Even if you finish it by adding '$isbn'";, this approach is risky because it leaves you open to SQL injection attacks. Instead, use prepared statements (the safer, recommended method for MySQLi):

   if (isset($_POST['delete']) && isset($_POST['isbn'])){ 
       $isbn = $_POST['isbn'];
       // Use prepared statement to avoid injection
       $stmt = $conn->prepare("DELETE FROM classics WHERE isbn = ?");
       $stmt->bind_param("s", $isbn); // "s" = string type; use "i" if ISBN is an integer
       $stmt->execute();
   }
   

2. Undefined get_post() Function
   Your code calls get_post($conn,'isbn'), but if this function isn't defined elsewhere in your codebase, it'll throw a fatal error and stop the DELETE logic. If you intended to use it to sanitize input, here's what a basic version would look like (though prepared statements make this less necessary):

   function get_post($conn, $var) {
       return $conn->real_escape_string($_POST[$var]);
   }
   

3. No Execution Result Handling
   You're not checking if the DELETE actually worked. Add a check to confirm success or debug failures:

   if ($stmt->affected_rows > 0) {
       echo "Successfully deleted {$stmt->affected_rows} record(s)";
   } else {
       echo "No matching records found, or deletion failed: " . $stmt->error;
   }
   // Clean up resources
   $stmt->close();
   $conn->close();
   

4. Missing Resource Cleanup
   While PHP automatically closes connections at the end of the script, it's good practice to explicitly close your statement and database connection once you're done with them to free up server resources.

Final Quick Tips #

• For guest_post(): Add var_dump() statements inside the function to check if input data is being passed correctly, and verify that any output logic (echo, return) is actually being triggered.
• For the DELETE script: Always use prepared statements to protect against SQL injection—this is non-negotiable for secure code.

内容的提问来源于stack exchange，提问作者Mehedi Hossain