A place for discussion about skinning and design. Before posting questions here you should review the documentation about creating skins.
I followed the directions in one of the threads in this forum to remove the line of links at the top of every page by removing the topnav div in layout.master. I then created new pages/menu items to go login and logout, redirecting to ~/secure/login.aspx and ~/logoff.aspx, respectively. After creating the pages, I must've edited it one or two times changing the title of the page, not paying close attention realizing the url changed accordingly. When I tested it by clicking on my new logout menu, it redirected to ~/logout.aspx which was created as my new page when I changed the title from logoff to logout. Realizing what had happened, I edited the page again, changing the url back to ~/logoff.aspx. After saving my change, I tested the menu but it still goes to logout.aspx. This time, however, it says the page doesn't exist and brings me to a search page. I flushed by browser cache and the cache on the server (I know it only controls CSS but I tried everything). I restarted my browser, tried a different browser and different computer with all the same results. My menu pointing to logoff.aspx still redirects to logout.aspx which doesn't exist. Anyone know where this could be stored? As a test, I tested this on a different site and it worked fine (once I confirmed the urls were correct). By the way, when I enter the urls, I get a warning that the pages physically exist. I also checked the files in the app directory and nothing looks suspicious with the current date/time other than a log file showing the redirection to logout.aspx and that it doesn't exist. Thanks in advance for the help!
Oh, one more thing. I enabled the navbar again and the sign out liink also redirects to logout.aspx. When I manually type in the url http://mydomain.com/logoff.aspx, it also redirects to logout.aspx.
when you change the url for a cms page a 301 redirect is automatically created, you need to remove it from Administration > Advanced Tools > 301 Redirect Manager
then you may need to clear the browser cache again because 301s are cached