Skip to main content
NextStepTV
Inspiring
July 4, 2011
Question

Inserting a Recordset Kills PHP Processing

  • July 4, 2011
  • 2 replies
  • 870 views

In Dreamweaver 11.0 (CS5) on both MAMP and a live server, I am experiencing a puzzling issue.

Inserting any Recordset kills PHP processing.  For example, this document works perfectly:

 
<!DOCTYPE HTML>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Untitled Document</title>
</head>
<body><?php echo “Hello, world.” ?><?php phpinfo() ?></body>
</html>

 
As soon as I add any Recordset to the page, those two php statements simply stop working. In fact, the Recordsets return no data on the page. After I delete the Recordset code that Dreamweaver had inserted, and restore the page, php statements magically begin working again!

(During the creation of the Recordset, the Test button confirms all columns are present, and the two rows are fine.)
Any clue to what’s going on?

This topic has been closed for replies.

2 replies

Lon_Winters
Inspiring
July 4, 2011

Are you binding date to the page, or just creating a recordset? have you tried without the PHP statements?

I tried it using your code and added a recordset, but didn't bind any data to the page and it works fine.

NextStepTV
Inspiring
July 4, 2011

I've solved part of this issue. It turns out that Dreamweaver copies to the testing server all new files and changes to files EXCEPT... the Connections folder it creates and that folder's contents. The user needs to do that manually.

However, after I copied the Connections folder, Dreamweaver refuses to Insert any Data Object.

For example, it won't insert a Repeat Region or a Dynamic Table. When I select

Insert->Data Objects->Dynamic Data->Dynamic Table

Dreamweaver returns this error:

While executing insertObject in DynamicTable.htm, a JavaScript error occurred.

Ditto the Repeat Region.

David_Powers
Inspiring
July 4, 2011

NextStepTV wrote:

While executing insertObject in DynamicTable.htm, a JavaScript error occurred.

That's usually a sign of a corrupt cache file. See Deleting a corrupt cache file in the Dreamweaver FAQ.