Bungie.net Community
This topic has moved here: Subject: Posting Errors...Need Help or Advice...
  • Subject: Posting Errors...Need Help or Advice...
Subject: Posting Errors...Need Help or Advice...

"I pledge to punch all switches, to never shoot where I could use grenades, to admit the existence of no level except Total Carnage, to never use caps lock as my "run" key, and to never, ever, leave a single BoB alive."

2B || !2B - Why don't you look Inside the Machine?

I have been experiencing some very strange things the past week or so here on B.net...the major one is the fact that I will go to read a thread and there will be no post by the person the tracking thing says made the last post. If you didn't catch that...let me explain:

When ever you are viewing the main forum, like the Flood...under the Last Post column, it says who posted last. Well when I see who posted last, I enter the thread and expect to see there reply, and I see nothing except the person before them. There post is not even there!

I don't know whether this has been brought up or explained, if so I am sorry for being redundant, because I have not read anything about it.

*Other Issue*

I think this has been noticed, but everytime mostly when I go to post a new topic, sometimes at the top of the forum it will have the "New users can't post within 24 hours..." warning at the top...and I am logged in and I have been here since May 11th 2005...so that is not the issue.

Thanks in advance for help/advice/other constructive and/or positive notation :)

[Edited on 2/25/2006]

  • 02.25.2006 5:11 PM PDT
  •  | 
  • Exalted Mythic Member
  • gamertag: Mabian
  • user homepage:

"Whatever exists, whatever in creation exists without my knowledge exists without my consent. These anonymous creatures may seem little or nothing in the world. Yet the smallest crumb can devour us. Any smallest thing beneath yon rock out of men's knowing. Only nature can enslave man and only when the existence of each last entity is routed out and made to stand naked before him will he be properly suzerain of the earth."

They are both glitches, and they are both temporary. In short, just refresh a couple of times, and if the problem continues, then wait about 30 seconds, then refresh again. I keep forgetting the reason as to why it happens, but we all know that they are easily fixed.

  • 02.25.2006 6:33 PM PDT

"I pledge to punch all switches, to never shoot where I could use grenades, to admit the existence of no level except Total Carnage, to never use caps lock as my "run" key, and to never, ever, leave a single BoB alive."

2B || !2B - Why don't you look Inside the Machine?

Thanks for the info.

:)

  • 02.25.2006 6:35 PM PDT
  • gamertag: [none]
  • user homepage:

Only the paranoid will survive!

With the first error, try Ctrl+r. It refreshes, but not from the cache. I find that using Ctrl+r (with Firefox, that is. Not sure what happens with IE) tends to clear up the invisible post problem. With the second problem, you can still post threads and such I believe, so it doesn't really cause any problems.

  • 02.26.2006 12:12 PM PDT

Phrog pilots, reckless and free. We would strap into our birds, set the engines on fire, and leave these earthly bonds with a chorus of WHOP WHOP WHOP. Akin to beating your chest and howling in defiance at the rest of the world.
Phrogs eye view
sockbaby

Posted by: Pimp at Sea
With the first error, try Ctrl+r. It refreshes, but not from the cache. I find that using Ctrl+r (with Firefox, that is. Not sure what happens with IE) tends to clear up the invisible post problem.
Yep, it also works for us IE types as well. :)

  • 02.26.2006 1:36 PM PDT

They're both bungie.net caching glitches. They usually sort themselves out pretty quickly.

  • 02.26.2006 6:53 PM PDT

"I pledge to punch all switches, to never shoot where I could use grenades, to admit the existence of no level except Total Carnage, to never use caps lock as my "run" key, and to never, ever, leave a single BoB alive."

2B || !2B - Why don't you look Inside the Machine?

Posted by: goweb
They're both bungie.net caching glitches. They usually sort themselves out pretty quickly.


Thanks...hopefully there will be a solution!

:)

  • 02.27.2006 2:20 PM PDT