Moving Back Problems n Scrolling
Hi All.
In a web page, which is for entering and saving data.
After saving user redirects to a new page. but User can move Back(using Back button of BROWSER) to that page and can edit and Re save it. So what is the method to prevent user to see old pages or how can we prevent user to save it again.
Second problem is that when page is too long then I don't want my Menu and Header to scroll above the page while using scroll bars.
How is possible to to make it visible while scrolling.
ANy IDEA
Thanks
Re: Moving Back Problems n Scrolling
Response.Cache.SetCacheability(HttpCacheability.NoCache)
Re: Moving Back Problems n Scrolling
For your second problem, you could use a floating DIV that contains your menu and header.
Re: Moving Back Problems n Scrolling
Thanks Mendhak for reply.
Response.Cache.SetCacheability(HttpCacheability.NoCache)
where should i put this line? means on page load event or any where else?
And for other problem
<div align="center" style="float:inherit;" >
Float don't have Top , it contains Left,right,none and inherit only.
while I want I want to show the menu bar and header evenif user scroll down.
thanks
Re: Moving Back Problems n Scrolling
That makes things slightly more complicated. You'd end up making your page to fit the screen, and putting any scrollable content inside a scrolling <div> tag... I've seen it done, but I've never actually done it. I just manipulate the visible states of <div> tags based on inputs...
Re: Moving Back Problems n Scrolling
First answer: Place it in the page load event of every page that you do not want the user to be able to access after he has logged out.
Second answer: Goooooooooooooooooooooooooooogle
Re: Moving Back Problems n Scrolling
Thanks Mendhak for reply.
Actually I do not want the user to be able to access previous page even user is still logged in .
Any Idea??
Thanks .
Re: Moving Back Problems n Scrolling
Now you're being weird. If you don't want them to access it when they click 'back', why give them access at all? Don't even create the page. That goes against the concept of navigation.
You will need to explain what the pages are for and why you want to do this before we can offer a solution. The solution will have to fit your current uhm... "architecture" in double quotes.