|
Posted by dorayme on April 1, 2008, 6:12 am
Please log in for more thread options
> I've thought of putting all on the one page - trouble is that would
> involve a lot of scrolling ...
A lot of scrolling? You mean three pages worth? Who do you think your
audience is, wimps and wusses? Come on Geoff, grab this thing by the
horns and take the easy way out.
If you want to assist these delicate scrolling averse users, you can
stick in an id or two and link within the page. For example you might
want the sections that have to be filled in to be separated by some sort
of height chasm not to influence answers to the test in the earlier
sections by the eyeballing of the questions in the subsequent sections.
--
dorayme
|
|
Posted by George Maicovschi on April 1, 2008, 5:23 am
Please log in for more thread options
Use a server-side validation using sessions and throw the user on the
page he should be if he tries to access another one.
|
|
Posted by Jukka K. Korpela on April 1, 2008, 5:38 am
Please log in for more thread options Scripsit Geoff Cox:
> I am preparing a site where it is important that the user moves from
> page 1 to page 2 to page 3 etc as a series of tests are presented and
> the order is important.
What makes you think this is an HTML question, or a JavaScript question?
Followups set to the the group where this is less off-topic than in the
other. In future, please select _a_ group properly. (Hint: use
comp.infosystems.www.authoring.misc if you think it's about WWW
authoring but you cannot select a more specific group.)
> Is it possible to make sure that this happens?!
No.
> One thought I've had is that to stop a user arriving at say page 2 by
> using Google, I can put all these pages into a password protected
> folder (using htaccss/htpasswd). The users would be presented with the
> same user name and password on the public page. Is there any other
> way?
That does not prevent people from accessing page 2 first. They just need
the password from a pal. Or something like that.
But it would piss off users.
You can use <meta> tags to ask indexing robots not to index pages 2, 3,
etc. Most of them will honor the request. Does this leave you some
_real_ problems? Which? What will happen, really, if someone views page
2 before viewing page 1? The world, as we know it, will end? You will be
prosecuted? The user sees a spoiler?
If this is a _real_ problem, please re-raise it in a more appropriate
forum and explain what you are really doing and what your server-side
programming capabilities and skills are.
You would probably get reasonably close by arranging things so that page
2 has no direct address of its own and page 1 contains a form consisting
only of a submit button and some hidden field(s), and the form would
have method="POST". The action="..." attribute would refer to a
server-side script that checks its data for the presence of some
specific field(s) with specific value(s) (as specified in the hidden
field[s] of the form); if they are present, the script would return the
content of page 2, otherwise an error code and an error explanation
page.
Of course, the "protection" would be easy to break, but only by someone
who is really interested and studies the techniques used. For a safer
approach, you would make page 1 dynamically generated and would make the
hidden field be different for each occasion, and your server would
contain a file of generated hidden field values and would remove a value
as soon as it has been found in a request. That is, for each page 1
generated, page 2 could be accessed _once_. So page 2 would resemble the
scrolls in Rogue, the game (you know, "as you read the scroll, it
vanishes").
Now, there's the simple problem of a user who has so accessed page 2 and
saves a local copy of it and uploads it on a server. I hope your next
question won't be "How do I prevent people from saving my page?"
--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/
|
|
Posted by Andreas Prilop on April 1, 2008, 8:46 am
Please log in for more thread options On Tue, 1 Apr 2008, Geoff Cox wrote:
> I am preparing a site where it is important that the user moves from
> page 1 to page 2 to page 3 etc
"I am the publisher of a newspaper where it is important that the
reader moves from page 1 to page 2 to page 3 etc. How do I do this?"
--
In memoriam Alan J. Flavell
http://groups.google.com/groups/search?q=author:Alan.J.Flavell
|
|
Posted by Geoff Cox on April 1, 2008, 9:15 am
Please log in for more thread options wrote:
Thanks everyone for the useful comments - will work through them now.
Cheers
Geoff
|
| Similar Threads | Posted | | Force CSS on external site? | December 13, 2004, 6:00 pm |
| Forms: Where is the character encoding (eg. UTF) defined? | October 29, 2004, 3:32 pm |
| XHTML 1.0 Validator: No attributes, elements not defined... | August 11, 2004, 3:21 am |
| CSS: Problems with doubly defined colors (according to validator) | May 20, 2007, 5:26 pm |
| Order of buttons? | October 6, 2005, 9:37 am |
| css parsing order | May 20, 2006, 8:11 pm |
| Z order for frames | January 14, 2008, 8:55 pm |
| div presentation order | April 28, 2008, 7:28 pm |
| DIV Tag Not on Top Z-Index Order Problem? | March 25, 2005, 3:03 pm |
| WYSIWYG order forms? | November 24, 2007, 2:20 am |
|
XML Sitemap