I haven't been using the wizard. If Dreamweaver is likely to screw up any WebAssist code because of weights then I don't really see the point because we'll end up having to hand code it anyway.
So, to test my theory, I've added a SecurityAssist Authenticate User behaviour on the following page and, lo and behold, it doesn't work:
http://www.portpatrick.me.uk/admin/index.php
Worst still, it's appending all of the security credentials into a querystring in the address bar!
Also, when I re-enter the dialog for the SecurityAssist Authenticate User behaviour and then exit it, it adds another:
<?php
@session_start();
?>
...to the top of the page so we're left with:
<?php
@session_start();
?>
<?php
@session_start();
?>
:(
No idea what's going on. Our database is connected. We have the right database fields binded to the sign in form. We are using the correct username and password credentials to sign in.
Hope you can help.
Thank you.
NJ
EDIT: This appears to be working now - I have no idea what I've done - but now that I'm logged in I can see no way to secure the private pages?
Would appreciate some help because I am finding SecurityAssist to be a real headache compared to the DW "Restrict Access to Page" behaviour but I want to maintain the WebAssist extension for the additional features that I believe it has.
