Loading Profile...
Twitter,
Facebook, or email.
I’m
happy
Invalid blog credentials with SocialSpark 2.0
Trying to authorize via socialspark 2.0. Getting error that credentials were not accepted. (Credentials are being entered correctly.)
Promoted
Responses
-
I’m
happy
1We just released an update to SocialSpark 2.0 for self-hosted WordPress users who were having trouble authorizing. If that's you, check it out and let us know if that solved your problem! -
Hi everyone, and thanks for taking the time to give us your feedback. It's really helping us to nail down issues with Direct Publishing before switching the whole site over to the new version of SocialSpark.
For most configurations, AtomPub just works after it's enabled in the WordPress admin interface, but in the case of PHP run as CGI on top of the Apache web server (forgive me for getting technical here), additional Apache configuration may be required. This is a well-known issue with Dreamhost, and likely many other hosts as well.
PHP run as CGI is the most common of the few issues we're seeing with WordPress. Another possibility, as Jonamerica mentioned, is a WordPress installation that is in a non-standard location (i.e. your blog URL is someurl.com but your WordPress is installed at someurl.com/blog).
Another possibility is an issue with your server's configuration. There's a pretty technical explanation of possible server issues on WordPress's site. And a final, less common issue is a version of WordPress that is very old and does not support AtomPub (if that is the case, we strongly recommend upgrading, at the very least for security reasons).
We are working on a solution for the first few issues now. One will give users a fall-back in case their server configuration is rejecting AtomPub credentials passed over Basic Auth (again, forgive the technical language). Another fix will allow users to tell us if WordPress is installed in a different location from their blog. Please hang tight while we work to implement these workarounds for you, and thanks again for providing this valuable feedback.
Regards,
Jamie Kite
Product Owner, SocialSpark.com
-
I’m
anxious
I am getting Credentials Rejected when trying to "claim" my blog.
This reply was created from a merged topic originally titled
Rejected Credentials.Comment -
-
I’m
happy
can't get direct publishing enabled - it keeps saying my creditials are incorrect, but I have triple-checked my username and password and they are correct.
This reply was created from a merged topic originally titled
can't get authorized for direct publishing. -
-
I’m
frustrated
I've supplied all of the correct information on my WordPress blog and yet it gives me the error: "Your credentials were rejected."
My WordPress blog is self hosted so I'm wondering if this is the problem?
This reply was created from a merged topic originally titled
Unable to verify direct publishing on self hosted WordPress blog.. -
-
I’m
sad
My credentials have been rejected for some reason while attempting to set up my WordPress with Social Spark. Have tried numerous times to correct, however still getting same error message. What may be the problem?
This reply was created from a merged topic originally titled
Can't authorize social spark. -
-
I’m
sad
When i am trying to add my blog details like username and pass i am getting error . "Your credentials were rejected." Why this error is coming ? I am using socialspark v2.0
This reply was created from a merged topic originally titled
Can't authorize the blog. -
-
same thing happened to me - I bet its a bug on their end because its happeneing so often! -
-
I think this problem, for me, is because my wordpress blog isn't at the root, but rather it's at /blog.
it's www,mywordpresssite,com/blog
not www,mywordpresssite,com
If social spark is trying to login by visiting
www,mywordpresssite,com/wp-login.php it will fail - it needs to go to
www,mywordpresssite,com/blog/wp-login.php-
You could have found the problem... My blog, too, is down level from the root.
-
-
-
-
-
My blog does not have /blog in it. So this doesn't fix my problem.
-
-
Hi everyone, and thanks for taking the time to give us your feedback. It's really helping us to nail down issues with Direct Publishing before switching the whole site over to the new version of SocialSpark.
For most configurations, AtomPub just works after it's enabled in the WordPress admin interface, but in the case of PHP run as CGI on top of the Apache web server (forgive me for getting technical here), additional Apache configuration may be required. This is a well-known issue with Dreamhost, and likely many other hosts as well.
PHP run as CGI is the most common of the few issues we're seeing with WordPress. Another possibility, as Jonamerica mentioned, is a WordPress installation that is in a non-standard location (i.e. your blog URL is someurl.com but your WordPress is installed at someurl.com/blog).
Another possibility is an issue with your server's configuration. There's a pretty technical explanation of possible server issues on WordPress's site. And a final, less common issue is a version of WordPress that is very old and does not support AtomPub (if that is the case, we strongly recommend upgrading, at the very least for security reasons).
We are working on a solution for the first few issues now. One will give users a fall-back in case their server configuration is rejecting AtomPub credentials passed over Basic Auth (again, forgive the technical language). Another fix will allow users to tell us if WordPress is installed in a different location from their blog. Please hang tight while we work to implement these workarounds for you, and thanks again for providing this valuable feedback.
Regards,
Jamie Kite
Product Owner, SocialSpark.com-
Notice that you marked this as answered. Will you still be updating this when the workarounds are ready for us to implement?
-
-
We just released some fixes for issues people were having with WordPress earlier today (see note a couple replies below). Have you tried to authorize Direct Publishing since then? You shouldn't need to change your blog configuration at all -- just try re-authorizing in SocialSpark and see if that fixed it. :)
-
-
-
-
-
I’m
indifferent
When trying to authorize social spark for direct publishing it says my wordpress credentials were rejected. I know I am typing it correctly. I do not use the default "admin" account to post to my blog, is that part of the problem? Thanks.
This reply was created from a merged topic originally titled
Can't authorize direct publishing, WP credentials rejected.-
Hi Jim, We have a release coming in the next couple of days that will alleviate some of the WordPress issues. I'll update this thread when that is live!
-
-
-
-
-
I’m
sad
It won't let me claim my self hosted wordpress blog
This reply was created from a merged topic originally titled
Can't Claim. -
-
I’m
happy
1We just released an update to SocialSpark 2.0 for self-hosted WordPress users who were having trouble authorizing. If that's you, check it out and let us know if that solved your problem!
-
Thank you! It worked like a charm!
-
-
-
-
