I'm basically trying to make a computer based training module. We had to choose a topic and basically make a module that is to educate someone on the topic. At the end of the section there will be a quiz top test you on what you learn. We need to have an index or beginning page that lists all of the sections out so that the user can start wherever they want. I have all of my data done, but now I need to start the javascript. I wants it so that when you enter a section the page the user is on should be tracked. If for some reason the user closes the browser, he or she should be able to start on the page of the section they were on when the browser closed. For example if they were on the third page of the section when the browser was closed they would go back to the module later choose the section they were reading and it would remember and load the third page.

I created this set and retrieve function on each page of the module:



and this in the bodytag of each page



I've only used this one of of the module links so far:



I didn't think about what will happen if they close the browser come back start a whole different section. the cookie from before will interfere and it'll send them to the wrong place. Is there anyway I can adjust this so that if you want to start a new section the cookie from before won't interfere?

when you refresh or close and open a browser, temporary cookies can be destroyed (like the ones yours may be)

I believe most of your problem is because when your form loads it is writting a the cookie.. thus destroying all the previous data you had already saved.
(body on load)

The first step should be to check if the cookie already exists, if not, then create it

you should create different variables to keep track of page count for each section

This post has been edited by William_Wilson: 21 Apr, 2006 - 09:41 PM

so I should take the setCookies function off of the index page of my module? If I take the onload off of each page what do you suggest I do instead.

btw the onload is only on the pages of each section. The onload isn't on the index page that has the links to each part of the module.

This post has been edited by pricecd: 22 Apr, 2006 - 11:56 AM

It's not that you have to take it off the page...you should simply check and see if a cookie already exists before writing to it...if it is already there, do not write a new one. If additional information is required in the cookie, you can append to it.