Scheduled Downtime

jimmysisson · Jan 5, 2006

Hi. Still having trouble with 1 through 4. Also, when I've finished reading a thread, Previous and Next are nonresponsive; I have to go back to the Main Index, then to the particular forum, then subject heading to get to the next thread. Good luck debugging, and thank you.
Jim

Ibrahim · Jan 5, 2006

But I've marked number 2 and 3 as being normal operation for TBN. At least on my computer (and Muhammad's and Hakim's as well as all our backup machines.)

What browser are you using?

-Ibrahim

jimmysisson · Jan 5, 2006

Yes, 2 and 3 work correctly now. I'm using SlimBrowser, an overlay to IE. WOrks the same in IE. Still don't get Previous or Next, and clicking on Index gets me to a screen that only shows a couple of ads, so I click Index or Discussions or General Discussions again to get back to the Main Index page, then click for the specific discussion group. Thanks, Jim

MadReferee · Jan 5, 2006

As Soundguy indicated in an earlier post, #3 still does not work correctly. I am using the latest IE6 with Xp SP2 and W98SE with latest IE6. Also just to make sure it's not me, I tried #3 on one of my client's box stock Dell's with XP SP2 and it exhibits the same incorrect behavior.

For example on this topic, which contains multiple pages, when new posts are there, clicking on the topic from the News/Feedback menu always takes you to the first post of the topic's first page not the first unread which may be on page 2 or 3. Also clicking on any individual page number or "all" always takes you to the first post of the first page and in the case of "all" you only get the first page displayed not all of the posts.

If the topic does not have multiple pages but new posts then you go directly to the first unread which should be the correct behavior.

DaNag · Jan 5, 2006

( But I've marked number 2 and 3 as being normal operation for TBN. At least on my computer (and Muhammad's and Hakim's as well as all our backup machines.))

Number 3 (the "last unread post" problem) is still broken for me on the following:

Windows XP - Firefox and IE. Tested on 2 different PC's, cleared all cache, cookies and offline files.

Linux - Konqueror, Firefox. Again - everything cleared.

The URL's are still malformed. Here are two examples of broken links I'm seeing for this topic, when viewing the main page for this forum - it's the same on all PC's and browsers for me:

The topic link (should take me to last unread post):

Shortened Long URL

The Page 3 link:

Shortened Long URL

Neither of the above links work as they should, on any of the above PC/browser combinations - they both take you to the first page of posts.

Both of these links have the same problem. If you look near the end of each URL, you'll see the following snipet:

o//

Without getting into the tech details, this is the crux of the problem. Basically, the "o" is either missing a required value (that would go between the slashes), or it shouldn't be there at all - can't tell without access to the code. In any event, the two consecutive forward slashes should not be there.

Verifying this is easy. If you encounter the problematic behaviour when clicking on a link, manually edit the URL displayed in your browser by deleting the following characters:

o//

Leave the rest of the URL, before and after these characters intact. Hit enter to reload the page, and you'll go to the proper location.

I can't see how a browser/OS problem could cause the above, particularly when the behaviour is identical across different browsers and OS's. IMHO, it's got to be on the server side.

Keep at it, Ibrahim...we've got faith in you. /forums/images/graemlins/cool.gif

MikePA: Please review your message before posting it. It's simple not to create a long link that widens the entire thread. Just insert a descriptive word or two between the {url=http://whatever}Enter words here{/url} instead of the entire URL. Replace parentheses {} with square brackets in previous example. Alternatively, if you use the Instant Markup language URL link, the first prompt is for the URL. The second prompt is for a description. Do not simply paste in the URL again. Type a short description of the link.

DaNag · Jan 9, 2006

(MikePA: Please review your message before posting it. It's simple not to create a long link that widens the entire thread. Just insert a descriptive word or two between the {url=http://whatever}Enter words here{/url} instead of the entire URL. Replace parentheses {} with square brackets in previous example. Alternatively, if you use the Instant Markup language URL link, the first prompt is for the URL. The second prompt is for a description. Do not simply paste in the URL again. Type a short description of the link. )

MikePA - I'm familiar with how to make descriptive URL's. Perhaps if you re-read the post a little more closely, you will see why the complete URL was posted - in this case, it was necessary.

The point of posting the complete URL was to show the actual error in the URL text, which is why I stated:

"If you look near the end of each URL..."

Which, is a little tougher to do now that you've edited the URLs into links.

You messed up my quote, too... /forums/images/graemlins/grin.gif

MikePA · Jan 9, 2006

Perhaps if you re-read the post a little more closely,
When I find a widened thread, I look for the offending URL and change them. I seldom read the message, particularly when they're lengthy.

The point of posting the complete URL was to show the actual error in the URL text, which is why I stated: "If you look near the end of each URL..." 
Perhaps simply quoting the end of the URL where the error was? /forums/images/graemlins/tongue.gif

 Which, is a little tougher to do now that you've edited the URLs into links. 
All somone has to do is put their mouse over the link and the URL appears at the bottom of their browser.

 ou messed up my quote, too... 
Happens when a post with a quote is edited. /forums/images/graemlins/frown.gif

ronjhall · Jan 9, 2006

All someone has to do is put their mouse over the link and the URL appears at the bottom of their browser. 
Right clicking on the link, then clicking properties will brings up the url that can be copied and pasted.

DaNag · Jan 9, 2006

( Perhaps simply quoting the end of the URL where the error was? /forums/images/graemlins/tongue.gif)

Which would have removed the ability to click on the links, which illustrated how they were failing.

Not a big deal, Mike...just pointing out there was a method to my madness, and clearing up to anyone reading my post details why it doesn't make sense anymore. It references text which is no longer there.

I would have simply edited my original post to clear things up after your URL edits, but evidently, too much time had passed - the edit function was disabled.

Oh, and FYI on the "edit bug" (quotes disappear) - I've run into this before as well, but you can add the quote tag back in. A bit of hassle, but it does work.

DaNag · Jan 9, 2006

( Right clicking on the link, then clicking properties will brings up the url that can be copied and pasted. )

That works, but you can do it a little easier/quicker...

IE: Right-click link, select "Copy shortcut"

Firefox: Right-click link, select "Copy link location"