abcb <> abcab

[George Hester]

So what's this? a is a ASP page. Clicking on a link there goes to the b ASP page. Clicking a link on that goes to the c ASP page. The idea here is to keep the visited attribute throughout the process. So if I go a->b-.c>->b using links dynamically generated the visited attribute holds up on the b page. Even later a->b. But if I go a->b->c->a->b the visted attribute does NOT hold up on the b page. Is there something I can do with session so that if the session is made in the c page then I can make sure the visited link in the b page holds the visited atribute? In other words abcb = abcab. Thanks.

 

[Aaron [SQL Server MVP]]

George, I have absolutely no idea what you're talking about. Are you
speaking of the VLINK attribute of the body tag? What does it have to do
with ASP?

--
http://www.aspfaq.com/
(Reverse address to reply.)





So what's this? a is a ASP page. Clicking on a link there goes to the b ASP
page. Clicking a link on that goes to the c ASP page. The idea here is to
keep the visited attribute throughout the process. So if I go a->b-.c>->b
using links dynamically generated the visited attribute holds up on the b
page. Even later a->b. But if I go a->b->c->a->b the visted attribute does
NOT hold up on the b page. Is there something I can do with session so that
if the session is made in the c page then I can make sure the visited link
in the b page holds the visited atribute? In other words abcb = abcab.
Thanks.

 

[Bob Lehmann]

It's probably in a *.asp page.

Which reminds me, I have an ASP site about fused glass. Where can my client
get the best prices on Bullseye glass? I need to do a site on auto mechanics
pretty soon too. My truck hasn't been running well lately.

Bob Lehmann

 

[Zeke]

George,
Your code needs to be flexible, so that the code in c checks for
current values before initializing your session variables. I beleive
that session variables won't error out if you check them for
existence.

As In:
If ISNULL(Session("visitedB")) Then
Session("visitedB")=False
End If

There are a variety of other ways to get this done as well.


If you are just talking about vlink='#color' tags not working, it
could because your site or your machine is caching the page. I use the
full cache blocking code in most ASP pages myself:

<%@ Language=VBScript %>
<%
Option explicit
Response.Buffer=true
Response.CacheControl = "Private"
Response.Expires=-1
%>

Place it at the start of the main ASP document for full effect. To
help guard against caching. It helps, but it won't handle all cases.

 

[George Hester]

Alright now I figured out what was happening. It turns out that:

http://www.myserver.com/page.asp is different then

http://www.myserver.com/page.asp?hi=hello

Since navigating around my site uses many of these parameters, I didn't
realize that visited depends on the parameters used. Not their values but
that they exist in the addressing.

So all I did was make sure that returned to pages included the parameters
that they were originally accessed with. Again not their values. For
example if I returned to page.asp above I could do it like this:

http://www.myserver.com/page.asp?hi=

and the visited would show correctly. I used the FSO to make sure that
pages accessed from out of the site would get their correct parameters.
Thanks to all who responded.

--
George Hester
__________________________________
So what's this? a is a ASP page. Clicking on a link there goes to the b ASP
page. Clicking a link on that goes to the c ASP page. The idea here is to
keep the visited attribute throughout the process. So if I go a->b-.c>->b
using links dynamically generated the visited attribute holds up on the b
page. Even later a->b. But if I go a->b->c->a->b the visted attribute does
NOT hold up on the b page. Is there something I can do with session so that
if the session is made in the c page then I can make sure the visited link
in the b page holds the visited atribute? In other words abcb = abcab.
Thanks.