Bug Posting/replies and PM/replies and edting posts

Discussion in 'Support & Feedback' started by Revelations-Decoder, Jun 5, 2013.

0
Page 2 of 2
  1. digitalpoint

    digitalpoint Overlord of no one Staff

    Messages:
    38,334
    Likes Received:
    2,613
    Best Answers:
    462
    Trophy Points:
    710
    Digital Goods:
    29
    #21
    I did some looking through the code, and I really didn't see anything that would cause that. The internal flood check system is per action... so it would only block a report if you reported something else in the last 30 seconds.

    I'm tossing around the idea of the flood check being bypassed for established members, but I can also see it opening up some issues that might not be worth it (for example it would allow established members to post sequential replies to threads quickly when they really should be editing the last post anyway).
     
    digitalpoint, Jun 9, 2013 IP
  2. Revelations-Decoder

    Revelations-Decoder Well-Known Member

    Messages:
    3,028
    Likes Received:
    152
    Best Answers:
    4
    Trophy Points:
    190
    #22
    I just had the same problem deathshadow is having again to Shawn, as went to reply to a post only to be told to wait 30 seconds (it took me longer than that to write the reply so it wasn't due to having just posted). First time this has happened to me for a few days...
     
    Revelations-Decoder, Jun 9, 2013 IP
  3. digitalpoint

    digitalpoint Overlord of no one Staff

    Messages:
    38,334
    Likes Received:
    2,613
    Best Answers:
    462
    Trophy Points:
    710
    Digital Goods:
    29
    #23
    digitalpoint, Jun 9, 2013 IP
  4. deathshadow

    deathshadow Acclaimed Member

    Messages:
    9,732
    Likes Received:
    1,999
    Best Answers:
    253
    Trophy Points:
    515
    #24
    While it's happening to me on every blasted post attempt.

    "Flood detection" is usually annoying crap for anyone actually using a forums. Once someone registers, it's a BS way to try and prevent spamming that NEVER works right.

    Of course, NOW I'm getting 400 errors too.

    ... and double posts.
     
    deathshadow, Jun 9, 2013 IP
    Revelations-Decoder likes this.
  5. Revelations-Decoder

    Revelations-Decoder Well-Known Member

    Messages:
    3,028
    Likes Received:
    152
    Best Answers:
    4
    Trophy Points:
    190
    #25
    Revelations-Decoder, Jun 9, 2013 IP
  6. Revelations-Decoder

    Revelations-Decoder Well-Known Member

    Messages:
    3,028
    Likes Received:
    152
    Best Answers:
    4
    Trophy Points:
    190
    #26

    I had same problem as it notified I didn't/couldn't/hadn't post(ed) hence my double post that I just deleted
     
    Revelations-Decoder, Jun 9, 2013 IP
  7. digitalpoint

    digitalpoint Overlord of no one Staff

    Messages:
    38,334
    Likes Received:
    2,613
    Best Answers:
    462
    Trophy Points:
    710
    Digital Goods:
    29
    #27
    Flood prevention has nothing to do with stopping spammers... more to do with stopping things like double posts (like if a user clicks "Post Reply" multiple times).

    It looks like the flood prevention is actually working as designed, but why your first post reply is timing out for you (or whatever is happening) is the real issue.
     
    digitalpoint, Jun 9, 2013 IP
  8. digitalpoint

    digitalpoint Overlord of no one Staff

    Messages:
    38,334
    Likes Received:
    2,613
    Best Answers:
    462
    Trophy Points:
    710
    Digital Goods:
    29
    #28
    Posting replies has a couple backend tasks that it runs that are ultimately dependent on external (and sometimes third-party services). I suspect we might be seeing something taking too long to process on the backend, and your browser thinks it never actually posted properly.

    Normally, the only process along those lines that is happening when a new post is created is the search engine indexer... Normally it's relatively instant to insert the content into the search engine, but I've seen it once in awhile take awhile (probably doing some data shard reallocation between nodes at that split second or something).

    Anyway... long story short is I already had planned on decoupling the indexing process from the posting of the content, I just never got around to it. I just now did it... so now the stuff being index is thrown into an internal queue that is processed on class __destruct() (meaning you don't have to wait on the indexing process as a user for your reply to show). Since I haven't seen what you guys are seeing happen to me anytime recently, it's just theory... but let me know if you guys are still seeing it now that the search indexer is not a blocking process for users.
     
    digitalpoint, Jun 9, 2013 IP
  9. Revelations-Decoder

    Revelations-Decoder Well-Known Member

    Messages:
    3,028
    Likes Received:
    152
    Best Answers:
    4
    Trophy Points:
    190
    #29
    Just made a reply in a thread and so far so good :) (though it wasn't happening every time so time will tell).
     
    Revelations-Decoder, Jun 9, 2013 IP
  10. deathshadow

    deathshadow Acclaimed Member

    Messages:
    9,732
    Likes Received:
    1,999
    Best Answers:
    253
    Trophy Points:
    515
    #30
    Well, let's see since it's been pretty much endemic here.

    Hmm... so far so good.
     
    deathshadow, Jun 9, 2013 IP
    Revelations-Decoder likes this.
Page 2 of 2