S2_Mac
New member
Sorry for flogging this (apparently dead) horse, but this is really irritating. Yes, I've posted about this before, and Bob sez, "Works fine for me," but something is still wrong.
The situation: When I click on an orange page number link (in the "vbmenu_control1" section of the dark gray "topic_navigation" box) for a second or third page, the link is malformed and won't allow access to the second page.
The conditions: My "thread display options" are set to "Show Avatars," "Show Signatures," and "Show Images;" Thread Display mode is set to "Hybrid;" and "Number of Posts to Show Per Page" and "Default Thread Age Cut Off" are both set to "Forum Defaults."
My testing: I have duplicated the problem on several computers: Mac OSX 10.4, 10.5, and 10.6, using Safari 4 & 5 and FireFox 3 & 4; Win XP SP2 and 3, using a couple of different IEs and FFs; Win 7 (SP unknown) using using a couple of different IEs and FFs. I created a new account (PlaysInTraffic), gave it the same preferences, and duplicated the problem on a smaller set of Mac and Win platforms. I've used connections supplied by ATT and Comcast; no difference.
An example: Here's a recent thread that has grown to 2 pages (given my settings) -- iPad2 versus PS3 for portable media player. The address of the thread starter post is " "http://forums.ilounge.com/ipad/269232-ipad-2-versus-ps3-portable-media-player-post1404283.html". The Page 2 link I get is this: "http://forums.ilounge.com/ipad/269232-ipad-2-versus-ps3-portable-media-player-2.html#post1404283".
Notice that the fragment identifier in the Page 2 link is the same as the tail of the thread starter's link -- "1404283" This results in the following behavior, every time: 1) The actual "Page 2" listing is served up; great! 2) Then the fragment is processed, and the first page -- the true location of the indicated fragment -- loads. In this example, the page I'm ultimately served is http://forums.ilounge.com/ipad/269232-ipad-2-versus-ps3-portable-media-player-post1404283.html
So...well, maybe I'm actually going nuts, or I've developed some strange RDF of my own ;-) But could someone at least humor the crazy person by attempting to replicate this error? Temporarily set your options to match those I've listed above, and then try to access this link: iPad2 versus PS3 for portable media player, Page 2, and then tell me if your final destination was the actual second page, or if -- like me -- you get dumped back onto the first page.
It's not a huge deal to work around this -- right-click on the link to Copy Link; then paste into the browser's address bar, and peck at the Delete key to remove the fragment identifier (leaving the address http://forums.ilounge.com/ipad/269232-ipad-2-versus-ps3-portable-media-player-2.html); then press Return to send the request to iLounge servers. Not a huge deal, but certainly worthy of being a lowercase pita!
The situation: When I click on an orange page number link (in the "vbmenu_control1" section of the dark gray "topic_navigation" box) for a second or third page, the link is malformed and won't allow access to the second page.
The conditions: My "thread display options" are set to "Show Avatars," "Show Signatures," and "Show Images;" Thread Display mode is set to "Hybrid;" and "Number of Posts to Show Per Page" and "Default Thread Age Cut Off" are both set to "Forum Defaults."
My testing: I have duplicated the problem on several computers: Mac OSX 10.4, 10.5, and 10.6, using Safari 4 & 5 and FireFox 3 & 4; Win XP SP2 and 3, using a couple of different IEs and FFs; Win 7 (SP unknown) using using a couple of different IEs and FFs. I created a new account (PlaysInTraffic), gave it the same preferences, and duplicated the problem on a smaller set of Mac and Win platforms. I've used connections supplied by ATT and Comcast; no difference.
An example: Here's a recent thread that has grown to 2 pages (given my settings) -- iPad2 versus PS3 for portable media player. The address of the thread starter post is " "http://forums.ilounge.com/ipad/269232-ipad-2-versus-ps3-portable-media-player-post1404283.html". The Page 2 link I get is this: "http://forums.ilounge.com/ipad/269232-ipad-2-versus-ps3-portable-media-player-2.html#post1404283".
Notice that the fragment identifier in the Page 2 link is the same as the tail of the thread starter's link -- "1404283" This results in the following behavior, every time: 1) The actual "Page 2" listing is served up; great! 2) Then the fragment is processed, and the first page -- the true location of the indicated fragment -- loads. In this example, the page I'm ultimately served is http://forums.ilounge.com/ipad/269232-ipad-2-versus-ps3-portable-media-player-post1404283.html
So...well, maybe I'm actually going nuts, or I've developed some strange RDF of my own ;-) But could someone at least humor the crazy person by attempting to replicate this error? Temporarily set your options to match those I've listed above, and then try to access this link: iPad2 versus PS3 for portable media player, Page 2, and then tell me if your final destination was the actual second page, or if -- like me -- you get dumped back onto the first page.
It's not a huge deal to work around this -- right-click on the link to Copy Link; then paste into the browser's address bar, and peck at the Delete key to remove the fragment identifier (leaving the address http://forums.ilounge.com/ipad/269232-ipad-2-versus-ps3-portable-media-player-2.html); then press Return to send the request to iLounge servers. Not a huge deal, but certainly worthy of being a lowercase pita!