You must be logged in to comment…
Re: hbdchick’s comments:
Well, perhaps i’ve misunderstood. I thought that this is where we get in contact with staff. Whenever I used the “Contact Support” form I was directed to here. Is there somewhere else I should’ve gone?
No need to be snarky, btw. Jeez — could you be more insulting?
My blog was basically shut down for four days because anonymous comments didn’t work — and my blog is all about discussion, so there’d be no point to blog without the discussion.
I left messages here for the staff, not for volunteers, hoping to get a reply from the them to one, simple question: were they trying to repair the bug or not, because if the answer was “not” I would make other arrangements for my blog.
I just want to let you know I agree and that I have been told in the past by Timethief that this is a place for volunteers to answer questions and not members of staff. However, I have seen staff here in other forum questions. I think that staff only don’t appear on those posts where there actually are large-scale problems that they create, without any input from the rest of the community. The only way I learned of this was from Twitter, of all places, from other WP.com bloggers, not from WP.com itself. Why can’t WP.com actually send e-mails to its members to let them know what the hell is going on? Is that too much to ask? For me, I don’t think so. I’ve been with WP.com for six years and this is the first year that I’ve had major problems, mainly because of a lack of communication from staff and/or input from members on changes. I have people who can’t comment now on my blog, which I thought openID was supposed to solve anyway so Blogger and WordPress.com bloggers could comment on each other’s blogs. It sounds like Gravatar isn’t helping either. Hope this week somebody on STAFF can figure this problem out.
Do you have a specific problem with bisitor’s posting comments on your blog? If so please provide deatils for Staff to assist them with sorting out your issue.
By now, I think they (STAFF) should be more than aware of what the problems are, so I’ll just wait a few days to see if they actually can resolve them. They obviously aren’t going to be resolved here in a forum of VOLUNTEERS who have no control over the way WP.com operates.
Staff have provided 3 updates to the original Recent Updates to Commenting thread here > https://en.forums.wordpress.com/topic/recent-update-to-commenting?replies=4
Also, the people who do the support are generally not the same guys who do the fixing/breaking of stuff, merely the ones who have to deal with the fallout.
Yeah, I know. But it doesn’t take much time or effort for support people to call up or walk over to the techie folks and ask: are you guys working on fixing this? I used to work for a dot.com, so I know. I mean, isn’t this what support staff are supposed to be for? To open up a line of communication, as it were, between the inner working of whatever company we’re talking about and the customers?
I just want to let you know I agree and that I have been told in the past by Timethief that this is a place for volunteers to answer questions and not members of staff. However, I have seen staff here in other forum questions.
A member of staff, Chris Rudzki, did leave a comment earlier on in this thread:
Unfortunately, he didn’t answer anybody’s questions or respond at all to any of the issues people were raising, which is why of course everybody kept pressing the issue.
Like I said — I thought this was the place to contact WordPress staff for help. At least this is where I got directed to when I pressed the Contact button. If I should’ve gone somewhere else I’d like to know — for future reference.
To my (helpful) fellow bloggers….
Yes, I’d just like to say THANKS to several of you out there (motre and others) who have been very helpful in trying to sort out this problem! Thank you, thank you, thank you! (^_^)
My fellow wordpress bloggers in Indonesia asking the same thing about this great improvement. I and some bloggers had to post something about it to explain. And we linked to this thread in our posts. This thread helps them to understand more than that wordpress’ sticky-and-closed-thread. It is very dissapointed for us. As happy-unpaid-testers we see no happy-engineers come to this thread and open up a line of communication between a supposed-to be-company and their customers. WordPress is one the best blogging service so we assume they have the best PR too. Or maybe we assume too much.
Another typical WordPress fiasco leaving some members, including myself, frustrated for far too long by a lack of prompt action or clear communication.
Little wonder that it has lead to some acrimonious comments being made, I’m sure only in the heat of the moment.
There seems to be a worrying lack of direction and clarity at WP, which is why I suspect Matt has simply lost inerest in the company, aside from its sale value.
Any danger of this getting fixed? I’ve just been trying to leave a comment on someone’s blog while logged into WP and I keep getting the ‘This email address is associated with a WordPress account, you need to go back and log in’ message. Hell’s bells, Worsepress, I *am* logged in already. I found that logging out and back in again means I can leave a comment – as in one comment, because I get the error message again if I then want to leave another one – but that’s a pretty poor workaround.
Just put things back how they were and tell this Google guy to tough it out while you think of something that actually works.
Still getting complains from readers and they can make all the extra updates and clarifications they want, this update should not be fixed but completely gone. I was thinking about hosting and getting my own domain name outside of wordpress, now I’m pretty much forced to do so..
you guys seems to do all the dirty tactics now to increase the wordpress.com users and traffic.
hope wordpress.com doesn’t start to sink like stumbleupon!
I can’t even start to express my frustration. My blog is still young and needs easy ways to comment, otherwise the reader will never come back. Now the only solution is to allow anonymous comments and try to instruct people simply not to leave their emails. Congratulations, WordPress, that was a hell of a decision!
Haha…OK…I noticed that this rather annoying error message that displays is now in (at least) its 3rd incarnation, and now reads:
That email address is associated with an existing WordPress.com (or Gravatar.com) account. Please click the back button in your browser and then log in to use it.
Congrats, WP, it’s slightly less confusing than the previous versions. However, what’s prohibiting a direct link to a login page? Or better still, why not place a login form directly under the error message? (that is, if you still insist that this complete upheaval is the best way to deal with such a minor problem, which it isn’t).
You see, with that language, you’re assuming that all the wp.com bloggers out there have prominently featured the ‘meta’ widget at the top of their sidebars, so that it’s easy for readers to know what to do after hitting the “back button”. Simply put, they don’t.
/Sorry for all the snark, but it’s frustrating to watch this FAIL playing out in slow motion. (actually it’s more of a double-FAIL, as Matt originally called it a WIN)
OK, I guess you can log in on any WP.com blog by hitting the “W” icon in the commenting form, so I retract that part of my post. The rest stands.
Isn’t WP embarrassed by all this?
OK, I know I keep coming back here, but hopefully people will find my latest thread on the issue helpful:
Guys, what is happening with our comments on WordPress?
I keep receiving e-mails from my readers who get the following error message when they try to comment: “That email address is associated with an existing WordPress.com account, please log in to use it.” The problem is that the readers trying to comment have never had a WordPress account. I understand that the only way to leave a comment now is to put in a “fake” e-mail address. Not good!
Can you please let us know when this issue will be resolved? Thank you!
The topic ‘You must be logged in to comment…’ is closed to new replies.