Feature Request
I would like the ability to update the user record after login and still get the redirect behavior. It would be nice to easily update a last use filed with the current date upon login.
I would like the ability to update the user record after login and still get the redirect behavior. It would be nice to easily update a last use filed with the current date upon login.
Thank you for the suggestion.
The way to do this currently is to have an update server behavior from dataassist on the page below the login. Then don't set the success redirect in the login and use the redirect in the update.
We could definitely combine this into a single wizard in the future. Thank you for the suggestion.
Please correct me if I am wrong, but I didn't do it that way because I believe it does not quite work.
If I want to forward to previous page if it exists through the security extension, I believe it redirects to the login page with the previous url encoded in the "accesscheck" variable.
I don't think the update transaction will recognize this value and redirect to it will it? Isn't that security extension specific?
True, but then you could just set the redirect in the update server behavior to:
<?php echo(((isset($_GET["accesscheck"]))?$_GET["accesscheck"]:"defaultpage.php")); ?>
Which would use the accesscheck variable if it existed or redirect to the default page if not.
Just FYI,
There was an error in the code you offered.
<?php echo(isset($_GET["accesscheck"])?$_GET["accesscheck"]:"defaultpage.php"); ?>
when I tried to update the behavior. It kept coming back blank. I had to add the get value "accesscheck" to the bindings tab, use that, and manually edit it. Then I realized there is a parenthesis error. Should be:
<?php echo (($_GET['accesscheck'])?$_GET['accesscheck']:"defaultpage.php"); ?>
or
<?php echo ((isset($_GET['accesscheck']))?$_GET['accesscheck']:"defaultpage.php"); ?>
BUT it would not accept the second version.
It would be nice, under this methodology, if WA used something more generic than accesscheck like redirect. I want to use the behavior for more purposes than just an inappropriate page access such as when someone clicks on the login link from any page on the site, OR they try to access a page that requires login. The easiest way for me to do this is to make those links include the url value of accesscheck, but that does not really describe what I am using it for.
Your friends over here at WebAssist! These Dreamweaver extensions will assist you in building unlimited, custom websites.
These out-of-the-box solutions provide you proven, tested applications that can be up and running now. Build a store, a gallery, or a web-based email solution.