求助：使用A-Frame点击按钮触发PHP发送邮件功能异常排查

Let's break down the possible issues step by step to get your email functionality working smoothly:

1. Confirm A-Frame Button Click Events Are Firing #

First up, make sure your clickable plane is actually registering user interactions. Your current A-Frame markup has the clickable class, but you need to add an event listener to trigger the email request when the button is clicked. Without this, clicking the plane won't do anything at all.

Add this script block to your HTML to handle the click action:

<script>
  document.addEventListener('DOMContentLoaded', () => {
    const infoButton = document.getElementById('information-button');
    infoButton.addEventListener('click', async () => {
      try {
        // Log to confirm the click is detected
        console.log('Button clicked, initiating email request...');
        // Send request to your PHP script
        const response = await fetch('email.php', {
          method: 'POST',
          // If you need to pass user-specific data (like user ID to fetch their email), add it here
          body: JSON.stringify({ /* add required data, e.g., userId: 123 */ }),
          headers: {
            'Content-Type': 'application/json'
          }
        });
        const result = await response.json();
        console.log('Email request response:', result);
        // Add success/error feedback for the user here if needed
      } catch (error) {
        console.error('Error sending email request:', error);
      }
    });
  });
</script>

• Open your browser's developer console (F12) and check if the "Button clicked..." log appears when you interact with the plane. If not, you might be missing a cursor component in your A-Frame scene—add a <a-cursor raycaster="objects: .clickable"></a-cursor> to enable click interactions.

2. Fix Frontend-Backend Communication Issues #

• CORS Errors: If your A-Frame app runs on a different origin than your PHP server (e.g., local dev server vs. remote hosting), you'll hit CORS blocks. Add these headers at the very top of your email.php to allow cross-origin requests (restrict the origin to your app's domain in production):

  <?php
  header("Access-Control-Allow-Origin: *"); // Replace * with your app's URL for production
  header("Access-Control-Allow-Methods: POST");
  header("Access-Control-Allow-Headers: Content-Type");
  

• Request Payload: If you need to fetch a specific user's email from the database, make sure you're passing the necessary identifier (like a user ID) from the frontend to the PHP script. The example above uses JSON, but you can also use form data if that's more familiar.

3. Debug Your Email PHP Script #

Since you haven't shared the full PHP code, here are critical checks for email.php:

• Database Fetch: Ensure your database connection is working and you're correctly pulling the user's email. Add debug logs to verify:

  // Example database fetch (adjust to your setup)
  $userId = json_decode(file_get_contents('php://input'))->userId;
  $userEmail = /* Your SQL query to get the email for $userId */;
  error_log("Fetched user email: " . $userEmail); // Check your server's error logs for this entry
  

• Email Sending Logic:
  • If using PHP's built-in mail() function: Many shared hosts require specific SMTP settings, and mail() can fail silently. Add error checking to catch issues:

    $to = $userEmail;
    $subject = "More Information Request";
    $message = "Here's the info you requested...";
    $headers = "From: your-valid-email@example.com\r\n";
    
    if(mail($to, $subject, $message, $headers)) {
      echo json_encode(["status" => "success", "message" => "Email sent successfully"]);
    } else {
      error_log("PHP mail() function failed to send email");
      echo json_encode(["status" => "error", "message" => "Failed to send email"]);
    }
    

  • For better reliability, use a library like PHPMailer instead of mail()—it handles SMTP authentication and provides detailed error messages if something goes wrong.
• Server Mail Setup: Confirm your web server has a working mail transfer agent (MTA) installed (like Postfix on Linux). If you're on shared hosting, check if they restrict outgoing emails or require you to use their official SMTP servers.

4. Test the PHP Script Independently #

To rule out frontend issues entirely, test your email.php directly by sending a POST request via tools like Postman or even a simple HTML form. This will tell you if the script works on its own, separate from A-Frame.

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