Minor issue with "give trading feedback" alert

Help Discussion in 'BeerAdvocate Talk' started by LambicPentameter, Jun 27, 2015.

Thread Status:
Not open for further replies.
  1. LambicPentameter

    LambicPentameter Initiate (0) Aug 29, 2012 Nebraska

    First off, I love the new feature that prompts a user to leave trading feedback once their trading partner has already left feedback.

    However, it seems like the prompt is firing for anyone with an open trade, even if they have provided feedback already.

    Example: I have provided feedback for my two open trades, but they remain open because the other users have yet to provide feedback to me. But I am getting a "leave trading feedback" prompt.

    Thanks and keep up the great upgrades!
     
    #1 LambicPentameter, Jun 27, 2015
  2. Todd

    Todd Founder (13,518) Aug 23, 1996 Finland
    STAFF Mod Team Society Pooh-Bah

    Thanks. I'll look into this. Who are the other two users?
     
    #2 Todd, Jun 27, 2015
  3. LambicPentameter

    LambicPentameter Initiate (0) Aug 29, 2012 Nebraska

    Users are:

    Shaggy9356
    Jordandid

    Thanks!
     
    #3 LambicPentameter, Jun 27, 2015
  4. Todd

    Todd Founder (13,518) Aug 23, 1996 Finland
    STAFF Mod Team Society Pooh-Bah

    The backend data looks accurate. Let me know if you're getting the alert now. Could be a caching issue before I applied some updates.
     
    #4 Todd, Jun 27, 2015
  5. LambicPentameter

    LambicPentameter Initiate (0) Aug 29, 2012 Nebraska

    I haven't seen it again since this morning, so it seems like it's working now. Thanks!
     
    #5 LambicPentameter, Jun 27, 2015
  6. dbrauneis

    dbrauneis Grand High Pooh-Bah (8,071) Dec 8, 2007 North Carolina
    Mod Team BA4LYFE Society Pooh-Bah Trader

    I got the alert initially yesterday (and dismissed it). I have no open trades and have not been a trader in the past.
     
    #6 dbrauneis, Jun 27, 2015
  7. Todd

    Todd Founder (13,518) Aug 23, 1996 Finland
    STAFF Mod Team Society Pooh-Bah

    It was definitely a caching issue from a code change. Going to close this down for now.
     
    #7 Todd, Jun 27, 2015
Thread Status:
Not open for further replies.