so completely new at this. long story short, recently started a new business, have several websites up and running so far, no problems. most of the sites are variations of one site i had built. did the changes myself in Dreamweaver cs4, everything worked fine. tried to do another yesterday and im having a problem with the php form. spoke with godaddy customer service after much deliberation they said it was definitely a php scripting error. as i am not well versed with this type of problem i figured i would ask someone who does.

thanks in advance for any help i receive.

Dani AI

Generated

OP reported a PHP form failure after edits in Dreamweaver CS4; correctly asked for the code and ’s "check the engine" quip is on point. The following concise checklist and two tiny test scripts isolate whether the issue is server configuration, file placement, or a bug in the form handler.

Quick PHP engine check (save as test.php in the same folder as the form):

<?php
ini_set('display_errors', 1);
error_reporting(E_ALL);
echo 'PHP OK. Version: ' . phpversion();
?>

If that prints the PHP version, the server parses PHP. If the browser shows PHP source or nothing, PHP is not being parsed (common causes: file not named .php, uploaded outside the web root, or using a hosting plan that does not run PHP).

Minimal form + handler to verify POST handling (place both files in the web root):

<!-- form.html -->
<form action="handler.php" method="post">
  <input name="name" />
  <input name="email" />
  <input type="submit" value="Send" />
</form>
<?php
ini_set('display_errors', 1);
error_reporting(E_ALL);
$name = trim($_POST['name'] ?? '');
$email = trim($_POST['email'] ?? '');
if ($name === '' || $email === '') { echo 'Missing fields'; exit; }
echo 'Received: ' . htmlspecialchars($name) . ' / ' . htmlspecialchars($email);
?>

Common pitfalls to check: use full <?php ?> tags (short tags may be disabled), ensure files are saved as UTF-8 without BOM (Dreamweaver can add a BOM that triggers "headers already sent"), confirm correct file permissions (typical 644), and review the host error log (GoDaddy control panel) rather than relying only on generic support statements. Enable display_errors only while debugging; turn it off afterward. Useful debug data for follow-ups: exact PHP error text, the full HTML form and handler code, and the hosting PHP version.

Recommended Answers

All 2 Replies

You literally just posted the equivalent of a check-engine light. You have to actually explain your problem preferably with code samples

You literally just posted the equivalent of a check-engine light.

Well, in all fairness, he did say that the check engine light was on, so I think he should check the engine first and then focus on other areas, like his missing code. Agreed?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.