1. Are you a current member with account or password issues?

    Please visit following page for more information

    Dismiss Notice

Imprper BANNED message. These are not real

Discussion in 'MEMBER RULES, GUIDELINES & ANNOUNCEMENTS' started by JonSidneyB, Feb 28, 2010.

  1. JonSidneyB
    • Administrator

    JonSidneyB Uber Prepared
    Staff Member

    Joined:
    Mar 28, 2006
    Messages:
    21,161
    Likes Received:
    12,085
    About a dozen people so far have told me they are getting the message that they have been banned.

    You are probably not banned. I am working on this problem now.
     
  2. JonSidneyB
    • Administrator

    JonSidneyB Uber Prepared
    Staff Member

    Joined:
    Mar 28, 2006
    Messages:
    21,161
    Likes Received:
    12,085
  3. stormtracker

    stormtracker Loaded Pockets

    Joined:
    Jul 25, 2008
    Messages:
    336
    Likes Received:
    9
    Ok,

    Im in for now, no more banned message : ) Thanks Jon.
     
  4. JonSidneyB
    • Administrator

    JonSidneyB Uber Prepared
    Staff Member

    Joined:
    Mar 28, 2006
    Messages:
    21,161
    Likes Received:
    12,085
    It is past 100 unbanned now.
     
  5. Belush2
    • In Omnia Paratus

    Belush2 EDC Junkie!!!!!

    Joined:
    Mar 28, 2009
    Messages:
    1,071
    Likes Received:
    762
    :naughty: I'm in now!!


    Glad to be back!!!

    Thank You Jon!!!
     
  6. Manatakui

    Manatakui Loaded Pockets

    Joined:
    Nov 17, 2008
    Messages:
    1,187
    Likes Received:
    7
    Thank you for fixing that, Jon. :)
     
  7. JonSidneyB
    • Administrator

    JonSidneyB Uber Prepared
    Staff Member

    Joined:
    Mar 28, 2006
    Messages:
    21,161
    Likes Received:
    12,085
    This is hopefully something that will never happen again. As people were found to be banned they were unbanned one at a time. We do know what happened. When moving to vB4 any users that were a member of any user group that was not stock in vB4 was automatically banned by the software. It was not obvious in the software due to the wording what was causing this. It turns out this happened to a great many forums that moved to vB4 and had non-vB standard user groups in it.