Recordset Not Seen Again

I can easily add these back again but though you might want to see this page. In was it's something you need to fix in the ext. Check out the page below. On this page select a Media Type (any media type) and then a Media and click continue. Brings you to a new page where you select the Client and then a Contact and Continue that bring you to the page in question. Here there are two recordsets that are not being seen in the behaviors panel.

These are hand-edited recordsets. This isn't something that will be fixed since we can't account for every way someone might edit a recordset. It will have to be found by Dreamweaver before we can update it. The same thing goes for the insert record server behavior that is on that page.

The best thing to do in those cases is to manually delete and re-apply the server behaviors. It looks like you edited the recordsets and manually added the sql parameters so they don't follow the typical syntax, and the insert has code added to save the insert id into the session. That is the reason why they don't show, but there really isn't anything I could do to fix that in a future build.

I have gone ahead and fixed the issues so you can see the server behaviors if you download the version I just uploaded.

They are there but doesn't let me edit them as it throws an error about javascript and the recordset. I will simply delete and add them back.

Unfortunately I can't even add recordsets with getting the following error now.

This post has been deleted.

This is because you have a form element on your page named "length". That is a reserved word in html because it is the name of a built in javascript object, and it breaks things if you have a form element with that name.

For a full list of form element names to avoid, see:
https://www.w3schools.com/js/js_reserved.asp

OK fixed that, updated and now 500 error. Im thinking this has to do with lines 32 to 38, check boxes don't seem to update so well, if you open the Insert Record behavior it has

<?php echo GetSQLValueString(isset($_POST['C1']) ? "true" : "", "defined","1","0"); ?>

as it's value, whereas everything else has

.($_POST['end_date']) .

I'm sure I could just use the lighting bolt to add it and it would fix it, but wanted you to see it for the EXT fix.

Yes, that does appear to be an issue with the update from the Adobe version of the insert when using checkboxes. You should fix yours by choosing the binding from the interface and I'll log the bug to get it fixed in the next update.