Technical problems with WordPress
I seem to experience some problems with WordPress. To be more specific the problems arise when I am trying to post a comment or click like on blogs that are under their own domain (blogs that have an example.wordpress.com adress are fine). Here’s a screenshot of the error message that I get:

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.
Of course I am already logged in and the email address is mine.
A similar thing happens if I want to click “like” on a post, I’ll be asked to log in (again: blogs that have an example.wordpress.com adress are fine). After I’ve clicked like & logged in, nothing happens. So I click like again, and I’ll be asked to log in again.
Here’s a screenshot from RobertSantafede.com:

Just one more step to like this post (but you’ll have to repeat this step forever and ever like Sysifos).
At first I thought the errors was related to my browser, so I decided to try commenting with Chrome instead of Firefox, but had no luck…
So, after having read about this on the WordPress forum (http://en.forums.wordpress.com/topic/recent-update-to-commenting?replies=4) I now believe that the error is to be found here:
Update #2
We discovered another bug that prevented some users from commenting if they attempted to comment on a blog with a custom domain name and had third-party cookies disabled. This bug has been fixed as well and we’re sorry for any inconvenience this might have caused.
According to user johnnytesting “It’s to stop counterfeit commenting. It may have been implemented poorly, but it was needed. Previously, if I had timethief’s email address, I could pretend to be timethief. So now, if someone tries to comment with an email in the WP database, WP wants to make sure it’s legit. That’s all.”
But, the problem still remains and as I discovered; multiple posts have been made on the subject.
http://en.forums.wordpress.com/topic/you-must-be-logged-in-to-comment?replies=185
http://en.forums.wordpress.com/topic/about-the-recent-update-to-commenting?replies=5
This entry was posted on March 18, 2012 by Cardinal Guzman. It was filed under the internet and was tagged with Chrome, computer, Error message, firefox, technical problems, wordpress.



Hello Cardinal,
When I see you, became curious!
I saw all the photo unusual, beautiful.
Many of you “artists”, you live in the U.S.
and I can learn things to me so far.
Do you have a particular style, oh yes, unusual!
and thanks to w.p. I was able to meet the world.
And you!
I’m sorry I do not know English, write with greater capacity.
but you are my very nice and I really like what you can communicate with your photos and your thoughts.
the problems of w.p. … eh my dear friend, I do not know where to start.
I understand very little about computers and technology, are a donkey
And while much of what I can do .. write invent and make videos.
menimale that there is a translator …. otherwise I could not write and understand what you write.
But I understand Princess
Good Sunday Cardinal and all your friends. you are fantastic!
italian wind
March 18, 2012 at 09:44
Don’t worry about being a computer-donkey, there’s lots of them out there: most people that use a computer probably fits into that category
I figured out the technical problems I had with WordPress, so it’s all good now (kind of).
I wish you a wonderful week Principessa!
March 19, 2012 at 07:13
March 19, 2012 at 07:56
Thank for sharing. I’m new at blogging and don’t really know all the ends and outs of it.
BE ENCOURAGED! BE BLESSED!
March 18, 2012 at 15:27
Hmm, interesting. I’ve run into a similar error when using Noscript in Firefox, but only until I ‘allow’ the site and refresh. That bug has to be annoying, I hope you get it working again.
March 19, 2012 at 05:35
I also run no-script & Firefox, but that’s not a part of the problem in this case.
The ‘error’ was that I had to let Firefox allow cookies from third-parties. When I did so, it was possible to write comments on custom domain names again.
March 19, 2012 at 07:00
Looks like you solved the problem…
March 22, 2012 at 09:20
I admired your useful post. good information. I hope you write more. I will carry on watching
March 24, 2012 at 18:48