65k Unread PMs

Discussion in 'ARRSE: Site Issues' started by armchair_jihad, Jul 29, 2007.

Welcome to the Army Rumour Service, ARRSE

The UK's largest and busiest UNofficial military website.

The heart of the site is the forum area, including:

  1. I have never been that popular, whats going on?
  2. Good CO

    Good CO LE Admin

    Is this an attempt to wind me up?
  3. I've got 65000!!
  4. In that case can I have some? I have bugger all :(
  5. I believe what GCO is getting at is that this is a known bug with the site software and if you had looked 13 threads before your own, you would have found someone else asking exactly the same question.
  6. i have 70000!!!

    beat that ha ha.
  7. So just because Dozy has asked the same question on the 2nd of April to which GCO replied

    negates my right to repeat the question?
  8. Sixty

    Sixty LE Moderator Book Reviewer
    1. ARRSE Cyclists and Triathletes

    No, I think this

    pretty much negates the need to ask the question.
  9. It is well known that the READ BEFORE POSTING TENDENCY on ARRSE is very much in the minority, increasingly so as the site gets bigger.

    However I acknowledge my wrongdoing.



    If you like I could start a new boot question thread
  10. Good CO

    Good CO LE Admin

    Sorry about the delay. Should now be sorted. I should add this one to the FAQ I suppose so shouldn't complain.
  11. Sorry Good CO, it's back!!
  12. Good CO

    Good CO LE Admin

    I've 'bumped' the software support forum thread in the hope of some help, meanwhile I'll just clear these from time to time. Not today though, sorry. Servers to worry about!
  13. Good CO

    Good CO LE Admin

    Did you do anything that might be the trigger for this? Deleted all your messages for example or some other definite action?
  14. Dads, can you fix my inbox again please?

    I haven't got 65543 messages.

    Just smutty ones from Flashy and Halo.

    Thanking you tar, in anticipation,

    Sluggy xxx
  15. Good CO

    Good CO LE Admin

    Done - I think the software producers have found the cause of this (thank you Nanocairdo of the dragonfly cms team) and a fix will hopefully be part of the next upgrade.