Question about changing the order that macro's are loaded.
I have LoginStatus XSLT and a .Net control that is part of the masterpage. I also have a login.aspx with a login control. The page also handles the logout functionality by going to login.aspx?mode=logout. Both of these items work, except for when they are on the same page.
My problem is that when I load up the logout page, the loginstatus doesn't update (to logout) since it seems to be running before the login macro can log the user out of the system.
Is there a way to change this so that the Login macro runs first, and then the loginstatus macro?
It may not be what you'd want, but can't you use the LoginStatus asp.net control instead of the xslt? It's designed to work with asp.net login controls so that should work flawlessly.
You are definitely correct, but we're trying to get nice and pretty HTML and the .net controls tend to create non-semantic and very ugly html.
I think I'm going to have to just add a bit of coding into the loginstatus control that I made that checks to see if the querystring mode=logout exists and if so, shows the login functionality. Not ideal, but it works.
Question about changing the order that macro's are loaded.
I have LoginStatus XSLT and a .Net control that is part of the masterpage. I also have a login.aspx with a login control. The page also handles the logout functionality by going to login.aspx?mode=logout. Both of these items work, except for when they are on the same page.
My problem is that when I load up the logout page, the loginstatus doesn't update (to logout) since it seems to be running before the login macro can log the user out of the system.
Is there a way to change this so that the Login macro runs first, and then the loginstatus macro?
Thanks,
C
Chad,
It may not be what you'd want, but can't you use the LoginStatus asp.net control instead of the xslt? It's designed to work with asp.net login controls so that should work flawlessly.
Hope this helps.
Regards,
/Dirk
You are definitely correct, but we're trying to get nice and pretty HTML and the .net controls tend to create non-semantic and very ugly html.
I think I'm going to have to just add a bit of coding into the loginstatus control that I made that checks to see if the querystring mode=logout exists and if so, shows the login functionality. Not ideal, but it works.
-C
is working on a reply...