Maybe the Discover people hasn't gotten back to the site yet....
then a staff member should relay that to the member instead of leaving them out in the wind.
Maybe the Discover people hasn't gotten back to the site yet....
then a staff member should relay that to the member instead of leaving them out in the wind.
three weeks and "the issue has been forwarded..."
very lame.
at the very least, you should have received a pm from a staff member explaining any progress on the issue.
Pretty sure the developer was looking into it when I posted four days ago. Customer support likely just recently found out they were working on it. I provided additional details to a staff member that was working directly with a developer at that point.
Code changes take a little time and have to be tested out of production to make sure nothing else breaks, then scheduled to move into production.
three weeks and "the issue has been forwarded..."
very lame.
at the very least, you should have received a pm from a staff member explaining any progress on the issue.
Pretty sure the developer was looking into it when I posted four days ago. Customer support likely just recently found out they were working on it. I provided additional details to a staff member that was working directly with a developer at that point.
Code changes take a little time and have to be tested out of production to make sure nothing else breaks, then scheduled to move into production.
Actually, I looked just now and it no longer gives that error, so it is probably fixed.
martin, my issue is the silence of staff on this (and many other things).
not how long it takes to fix, the procedure, etc.....
martin, my issue is the silence of staff on this (and many other things).
not how long it takes to fix, the procedure, etc.....
The only real issue is that it wasn't recognized as a bug earlier and referred to a developer as soon as it was clear there was an actual bug.
Staff isn't going to communicate every time a member encounters a bug, outside of the worked support ticket to that member, especially not one that likely impacted very few members. I would have contacted a staff member sooner, but I figured @baddogno referred to this topic and the pointing out that the error given was at the very least incorrect.
I won't disagree that sometimes a site-wide issue impacting a lot of members should receive some wider communication, but in general staff is more concerned with fixing the problem instead of spending cycles posting about it.
They have, in the past put up a banner regarding such issues. At other times they ask mods to post in topics where the issue is brought up, so members are aware of staff activity. I really don't think this particular issue needed more communication other than to the member with the issue and in the topic regarding the issue. While I'm not staff, I communicated that staff was looking at it.
Well you guys have certainly been busy here. I just checked, and as Martin mentioned the Maestro card error is no longer popping up....well actually I only punched in the first 4 digits so I don't know for sure, but it seems to be good to go. I do wish Billing had believed me in the first place instead of giving me the runaround for weeks, but I gather that they are very busy and apparently their stock responses work most of the time. Anyone with a lick of sense of course would have just shrugged their shoulders and used another card.
I'm stubborn though and was genuinely curious how the problem would be handled. In the past I've been known to give a link to other members having issues with paying for their membership along with my assurance that chess.com really wants their money and that Billing will do whatever it takes to get it. In the future, while I will still give a link; the personal assurance maybe not so much...
three weeks and "the issue has been forwarded..."
very lame.
at the very least, you should have received a pm from a staff member explaining any progress on the issue.