Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
I have made a homepage that uses membership logins for certian pages. On all pages I have a login status that shows wether or not you are logged in.
I had some problems getting this to work and posted a thread about it here . I figured out, that authentification will not work if I am using SEO friendly urls - or rather, if the viewed page do not end with .aspx. So I changed back to using normal urls, and everything works fine.
The front page of the homepage is not using the .aspx - it's just www.friskfisk.dk/. So I am back to my starting point.
The "funny" thing is, that if i write the page name - ie. www.firmafisk.dk/frontpage.aspx it works. If i trace the two "different" pages, i can se that AUTH_TYPE, AUTH_USER, LOGON_USER and REMOTE_USER is null on the version without the .aspx extension, but have correct values on the front.aspx page.
This might be some web.config thing, but I have really run out of things to try.
Information on the umbraco version, urls to test etc. can be found on the older post mentionen above.
I would really appreciate a littl help here.
You can use SEO friends URLS but ASP.Net is not configured to run against all pages by default and that might be what you're running into. Try this under win2003:
That should then force all your pages to fall under ASP.Net execution and should cause your membership code work properly on all pages.
What version of IIS are you using?
I have used the membership logins and friendly URL's on IIS7 and integrated pipelines.
Here is my post on how I set up the project:
setting up a new umbraco project
Points #4 & #5 will be most relevent to you if you are using IIS7.
runAllManagedModulesForAllRequests="True"> from Poul's link did the trick.
If you ever get to Roskilde, I'll buy you a beer, Poul.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted