no addresses

[t]

http://audiomastersforum.net/amforum/viewtopic.php?t=5594&highlight=
http://audiomastersforum.net/amforum/viewtopic.php?p=56082

t = topic, p = post.  Each topic is given an individual number in the database, same goes for posts.  But posts are also assigned to a topic.  So I would guess that by calling up a specific post number, it would also bring up the entire topic that that post belongs to.  At least, that seems like a logical explanation for how two different adresses can take you to the same page.  

Now why you are given different adresses is a whole other subject.  Could be based upon how you actually reach the topic.  The highlight parameter is used in searches, but usually it has a value!    LOL.

Ok, the answer to the frames problem lies in our usage of an add-on domain.  Support tells me that by using that feature, the hompage is thrown into a frame.  I'm not sure why this doesn't happen in FireFox.  But, if we want the problem eliminated it will mean finding an alternate route to use "audiomastersforum.info".  I can remove the setting that is causing the problem, if that is what everybody wants.  

EDIT:  I spoke too soon.  We should still be able to use the ".info" domain as it is set up.  I happened to stumble upon another setting the was utilising the frame forwarding, and I believe that that was the cause of the problem.  It's working fine here now.  Let me know what you all are experiencing.

Just to confirm, the behaviour I described above (i.e. the lack of detailed addresses) is new at my end...I've been able to point people in the Adobe forums to specific threads in the past.  Obviously the suspicion is that the change happened during the outage and this is the first time I've noticed it...but I can't say that for sure.

Bob

[EDIT:]

Ok, the answer to the frames problem lies in our usage of an add-on domain.  Support tells me that by using that feature, the hompage is thrown into a frame.  I'm not sure why this doesn't happen in FireFox.  

Hmm... It should only be a page on a different site/domain that is referenced from the original frame that would do this - it shouldn't happen within the single domain in which we are operating the forum, unless...

EDIT:  I spoke too soon.  We should still be able to use the ".info" domain as it is set up.  I happened to stumble upon another setting the was utilising the frame forwarding, and I believe that that was the cause of the problem.  It's working fine here now.  Let me know what you all are experiencing.

This makes a lot more sense as an explanation. Obviously you can choose to refer sub-pages as being within a frame if you want, but there shouldn't be any absolute requirement to do so. So if we turn off the frame forwarding, does everybody get an acceptable result?

Problem now fixed at my end...I see the proper full address now.

(and it DID happen in Firefox 1.5.0.6 for me.)

Thanks!

Bob