I still don't have the fix in the latest version of MySQLi Server Behaviors.
The issue is that for some reason some versions of php and/or MySQL won't work with views and prepared statements.
In general MySQLi server behaviors uses prepared statements because it is an extremely secure method of preventing SQL injection.
However, you can manually add code to prevent injection which should work just as effectively and actually has lower overhead. In the more recent rsobj.php file I've added a property to the WA_MySQLi_RS object that allows you to turn on and off "Prepared" statements. When it is turned off it falls back on traditional methods of preventing SQL injection.
I've uploaded that new file to your server. Please back it up in case you need to use it in the future.
You can either turn off Prepared statements in the recordset itself, like I have done on line 9 of your playlist_list.php file by adding:
$playlist->Prepared = false;
before the ->execute line, or you could turn it off entirely in the rsobj.php page on line 8.
The issue with doing it for each recordset is that adding that line will prevent Dreamweaver from recognizing the recordset for bindings and editing with the server behaviors window.