MySQLi - getting started

I've purchased, downloaded and activated your MySQLi extension. I have a preexisting web site that used Dreamweaver's Server Behaviors, Bindings, etc. My question is, as I update my existing pages with your extension, it is best practices to delete my old server behaviors, recordsets, etc. so that there's not a lot of excess code in my pages? Thanks,

Gail

Yes, remove the existing server behaviors, then replace them with the ones from the mySQLi extension.

In my older DW pages that have a membership profile recordset, I've duplicated the old rs with the new "_i" rs. In my old rs, it was filtered on "email = Session Variable MM_username". When I do a Test, however, regardless of whether I use a test default value of "-1" (which was what my old rs was set at) or "1", I get a result of No Data. What should be the default test value?

"What should be the default test value?"

a value that exists in the database for that column.

where it is the MM_Username session, i would suspect an email address.

Duh! Of course! Now I feel stupid. Plugging in an email address calls up the correct record. Thanks for your help!

No Worries.

I have many PHP pages with restricted access (members only or admins only). The previous DW behavior was fairly simple to set up: Restrict based on username and password, and if access denied, send them back to login.php. Your server behavior is more complicated to set up and even after reviewing the help file for this, I can't say I understand what to choose for Trigger and Authentication.Would the trigger be 'before page load'? and Authentication be what ... username? email?

In most cases the trigger to use would be one of the form post options when working with a login.

Any Form Post
Curent page submit
or Button: Submit pressed.

On the find record tab, you would bind the email and password columns to the email and password form elements.

In the MySQLi server behaviors, you will need to set up a different login for each user level, and on the Find record Tab, enter the user level value

on the members page, apply the members restrict access, and on the admin pages, apply the admin restrict access.

I probably wasn't clear in my original description. This is not my login page, but the page they land on after a successful login. So there are no forms or fields on this page, it just links people to members-only pages. Does your reply above still apply?

First you need to create the login, when you create the login using the MySQLi authenticate user behavior, you will give it a name.

in the restrict access behavior, use the before page load trigger, and select the login you created from the authentication menu.