Normally, if I want to link directly to a particular post in a thread, I’d click on “quote” to pick up the post ID data. But this isn’t possible with a closed thread. Is there an alternate method of determining the post ID number?
Hovering over the quote button doesn’t do much good, either, at least in my IE6; the URL line is so long it gets cut off from the URL slot at the window bottom, and the desired data doesn’t show.
And while we’re on the subject, what’s with the PHP data imbedded in all SDMB links in the browser’s address line? It looks like random characters, like “79fe54a649d2b1edb428a44516cecb” following “.php?s=”. I have found that deleting this from the URL doesn’t alter the action, so I usually do this when posting links. Is this a session or user-specific randomly-generated ID? And if it isn’t needed, why is it there?
If you mean the part that starts with “s=” and has all sorts of incomprehensible stuff in it, it’s the session identifier, which means that you are not using cookies.
If you have the bottom Status Line turned on in your browser, just hovering over the buttons show the number.
Note that some buttons yield threadid and some postid, but the status line will say which it is.
If you go into “properties” as Q.E.D. suggested, you could highlight the post id there, right-click and select copy to copy it rather than transcribing it manually.
IMHO an easier way - hover over the quote button, right-click, then select “copy shortcut”. Then paste it someplace and proceed.
Rowrrbazzle’s idea of right-click, “copy shortcut” works fine, maybe a little easier than the “properties” idea.
Yes, that’s the part I mean. But I don’t think it indicates I am not using cookies, as I never have to log in and I have cookies turned on both in the vB control Panel and the browser. Must be something else.
Thanks, Molson, but as UncleBeer pointed out, the data I want to reveal in the bottom status line is normally too long to show completely and there is no way that I know of to scroll horizontally in that slot.
So the random character string is called a “session hash”?
That’s something we can test, Ringo. Looking at the URL above, the string is still there. Checking my settings in CP, and it says “no” for “browse board in invisible mode.” Changing that to “yes”, saving settings, cruising back to this thread and redisplaying, the string is still there.
Automatically login when you return to the site? (uses cookies) yes
Browse board with cookies? yes
Allow Bulletin Board Administrators and Moderators To Send You Email Notices? yes
Hide Email Address? no
Use ‘Email Notification’ by default? no
Enable Private Messaging? no
Send you an email when you receive a Private Message? no
Pop up a box when you receive a Private Message? no
Show user’s signatures in their posts? no
Show user’s avatar in their posts? no
Show image attachments and [img] code in Posts? no
Default Thread View: Use forum default
Default Posts per Thread: Use forum default
Start of the week Sunday
Time offset: (GMT -6:00 hours) Central Time (US & Canada), Mexico City
Use vBCode quick links on your message input screens? yes
Style Set: BrightLinks
If I have Invisible Mode engaged, I see session hash. If I turn it off, the session has disappears. YM(apparently)MV.
I suppose your OS/browser combination might affect the situation as well.
Ringo, you made me think about other CP settings, so I went back to check the options. Here is the way the first three are set for me:
[ul][li]Invisible Mode? no[]Automatically login when you return to the site? (uses cookies) yes[]Browse board with cookies? no[/ul]If I change the last item to YES, the mystery string goes away. So apparently it is a cookie-substitute, and whatever data is otherwise stored as a cookie is imbedded in each URL request.[/li]
The advice along with the option says
My interpretation is “no” is the preferred choice unless you are using a proxy arrangement. I am not, but unless someone tells me the hamsters prefer it the other way, I’ll say “yes” and avoid the string junk.
Thanks, Ringo. You didn’t tell me the answer, but you led me there!
And Una Persson, perhaps this is the setting you were referring to (#3) – I thought you were referring to #2 (login cookies), which seemed to have no effect. Thanks to you, too.
