Reply to thread

Message

<blockquote data-quote="Quartermoon" data-source="post: 562877" data-attributes="member: 243">Re: New workaround!Hi!Mac OS 8.6, Netscape 6, home dial-up (no firewall, network, blah blah)I've had this problem ever since the switch to the new boards last year.&nbsp; (Just ask Piratecat!)&nbsp; The worst what when I would post a reply, and it would send me back to the end of the topic, but my post wouldn't show!&nbsp; <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f641.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":(" title="Frown&nbsp; &nbsp; :("&nbsp; data-smilie="3"data-shortname=":(" />)I had a rather thorough chat with a guy at vBulletin about it, and he was pretty clear that it's not them...but could never really address why it doesn't happen anywhere else that uses vB.&nbsp; I think the dialogue is on ther help forum somewhere...This is essentially how I solved the problem, but I left the &quot;check cache against server&quot; to &quot;Automatically.&quot;&nbsp; At least in my version, Netscape differentiates between memory cache, which it keeps in current memory during a single browsing session, and disc cache, which it stores on your hard drive.&nbsp; So just setting the disc cache to 0 prevents the cache from your last session from being kept.This means that, yes, the first time a page loads, it takes a while, but it's still in memory if you go back to it---yes, this is a problem here in these boards, but not anywhere else, so I find it a good compromise.&nbsp; I then go ahead and use the usual work-arounds to ensure I get the freshest page here when I have a problem (which isn't as often anymore...go figure).The only thing that really gets to me is that before the move, this never happened.&nbsp; So something changed somewhere, but who knows if we will ever find it.BTW, if you look really, really, really close, you can tell that Hacker Kulp is using a Mac.&nbsp; I blame him.<img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink&nbsp; &nbsp; ;)"&nbsp; data-smilie="2"data-shortname=";)" /></blockquote>

[QUOTE="Quartermoon, post: 562877, member: 243"] [b]Re: New workaround![/b] Hi! Mac OS 8.6, Netscape 6, home dial-up (no firewall, network, blah blah) I've had this problem ever since the switch to the new boards last year. (Just ask Piratecat!) The worst what when I would post a reply, and it would send me back to the end of the topic, but my post wouldn't show! :()I had a rather thorough chat with a guy at vBulletin about it, and he was pretty clear that it's not them...but could never really address why it doesn't happen anywhere else that uses vB. I think the dialogue is on ther help forum somewhere... This is essentially how I solved the problem, but I left the "check cache against server" to "Automatically." At least in my version, Netscape differentiates between [i]memory[/i] cache, which it keeps in current memory during a single browsing session, and [i]disc[/i] cache, which it stores on your hard drive. So just setting the disc cache to 0 prevents the cache from your last session from being kept. This means that, yes, the first time a page loads, it takes a while, but it's still in memory if you go back to it---yes, this is a problem here in these boards, but not anywhere else, so I find it a good compromise. I then go ahead and use the usual work-arounds to ensure I get the freshest page here when I have a problem (which isn't as often anymore...go figure). The only thing that really gets to me is that before the move, this never happened. So [i]something[/i] changed [i]somewhere,[/i] but who knows if we will ever find it. BTW, if you look really, really, really close, you can tell that Hacker Kulp is using a Mac. I blame him. ;) [/QUOTE]

Verification