SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
SI - Site Forums : Silicon Investor - Legacy Interface Discussion (2004-2011) -- Ignore unavailable to you. Want to Upgrade?


To: kirby49 who wrote (274)4/8/2004 3:36:39 PM
From: SI Bob  Respond to of 6035
 
Most of what you're bringing up won't be done when Dev becomes the production site, but will be added later.

I'll double-check to make sure it's taking you to the appropriate message number when you click on the number of unread messages.

Also keep in mind that the Dev site doesn't currently keep track on its own of what posts you've read and haven't read. That's still calculated based on what's been most recently imported from the production site. So clicking the unread posts on Dev won't reset that thread to zero like it does here. Not yet anyway.

Edit: Part of what's used to calculate unread posts comes from the bookmarks table here, which isn't imported on a regular basis. It's imported during off-peak times when I remember to do it. It's part of a site-wide "dead record" problem I'm still working on. Folder_Links was just the first part of it I fixed.



To: kirby49 who wrote (274)4/8/2004 3:47:00 PM
From: SI Bob  Read Replies (1) | Respond to of 6035
 
Well, I clicked on the dev site and had 40 posts to read on this thread so my first post showing when I click on that is 202. That's a problem right away as it says 202 of 256 which is more that 41 posts.

That's a symptom of the "disconnect" between the number of messages in existence here and on Dev. It should be mitigated a bit now because instead of having a 500-message gap between the two, it's a 20-minute gap. I can't decrease that gap (easily) because it'd involve a lot of checking to see if a message that was previously imported has been edited since the import. Hence the 20-minute gap. To make sure it can't be edited anymore.

Incredibly, I'm still having trouble getting the import routine to auto-refresh itself. It was working for a while using exactly the same syntax, but currently isn't working. A real head-scratcher.

Now it's hard to read those batches in reverse order and it's hard to find your place unless the new post count resets. If the messages in your batch are not in reverse order,

I see the problem now. The current version of the site shows the messages in ascending order, but the Dev version shows them in descending order. I'll change it to ascending order on Dev. Then the "Jump to Bottom" won't be necessary anymore.



To: kirby49 who wrote (274)4/9/2004 8:49:43 AM
From: SI Bob  Read Replies (1) | Respond to of 6035
 
Just noticed, and fixed, a problem you may've been trying to tell me about.

When clicking the number of new messages for a board, it was taking you to the last one you'd read, rather than the first unread one.

Fixed.

There are some recent holes in boards there, which I'd better fix this morning when I get to the office. I'm sure it's a problem with the new version of importing I put into production yesterday, which is also running every 5 minutes, meaning I've probably got as many missing messages on Dev as there were 5-minute periods since I fired the import back up yesterday afternoon.