If you follow the steps listed above you can comment out the line that makes this change, HOWEVER, it will then ALWAYS show the page title.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

The problem here is that we have two usage scenarios which are at odds.  In one case you have a page where the CONTROL is injected dynamically and another case where a MODULE is placed on a page.  The code should differentiate between these two usage patterns and behave appropriately.  I can't think of a single case where someone would manually place a login module on a page where that page was restricted from anonymous access (if you were already logged in then you wouldn't need the login module).  So I would not look at permissions to determine the behavior, but instead look at the usage pattern.  If you are on a page with ctl=login then you could use the current behavior, but if you are on a standard DNN page where the login module is being used then the page title should be preserved.

---

Joe Brinkman
DNN Corp.

Issue logged @ http://support.dotnetnuke.com/issue/ViewIssue.aspx?ID=5935 , i'll make the change for the next release.

Cathal

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US