Sorry, i post my nick in name topic... sorry

No one solution?
I have returned to firefox and safari until flock works fine...

I have the same problem: I host my own Wordpress blog but can't seem to get Flock to find any API key. I'm not sure if I am doing the right things to configure it manually but I experience the same things as TaZZiTo. Any help?

yep, the same here
I have a self-hosted WP 2.3.1 blog and flock says: There is no API ... (I'm using the newest Flock 1.0.1)

oops, I tested it once again - and it works.
yesterday it didn't
I don't know why, because I didn't change anything. But I'm glad it works now.

humm... not working for me. trying to connect to my self-hosted wp 2.1.3 install.

Same problem here. Error message is:

There was an error detecting your blog settings. Click OK and re-enter the username and password. To manually configure your blog, click Cancel.

Manual configuration doesn't help. Is Wordpress supported?

It detected the API wrong, but just by setting it up manually, putting in my login and password after it detects, and letting it save, I can update from within Flock perfectly, tags and all. Try just making a post after you plug in your url and data.

It detected the API wrong, but just by setting it up manually, putting in my login and password after it detects, and letting it save, I can update from within Flock perfectly, tags and all. Try just making a post after you plug in your url and data.

I don't understand how Wordpress could have detected the API wrong, but whatever. Setting it up manually hasn't helped me, as I keep getting the same error. I've tried "ATOM" and all those different options from the drop-down menu. It just keeps asking me for my login and password again.

I'm using the login and password I use to edit my blog posts.

hbsolomon,

What configuration did you have to set manually to get Flock working with Wordpress? We've been able to configure Flock with it in our QA lab.

Thx,
Mike Dosik
Director, Engineering Services
Flock, Inc.

Mike, was there any editing necessary for mod_security/htaccess? I'm really surprised you guys got it to work before launch, because no one I've asked to download Flock has successfully set up their self-hosted Wordpress blog with it.

I am having the same issues. I have a self-hosted Wordpress blog and I never can get past the username/password screen. It just keeps throwing out an error and then asking for it again. It's very frustrating.

There is a lot of reasons why your server configuration may make self-hosted blogs not work. If you want to get an idea of whether your server is correctly configured or not:
* Look at the source code of your page. Find the "RSD" file referred in header.
* Open that file in Flock. Look what API is preferred, and find the URL to xmlrpc.php.
* Open that file in Flock. It should say "XML-RPC server accepts POST requests only.". Sometimes you will see that the file is not accessible, and you need to change rights.

If that doesn't help, see if other desktop blogging tools work. If it works everywhere except in Flock, then congratulations! You found a bug. Please fill it in bugzilla (or come back here to get help filling it). If it doesn't work in any desktop client, then ask for help on Wordpress.org to get your XML-RPC working.

Voted for it. Thanks for posting, Daniel. Hey, everyone else in this thread! Sign up and vote on that bug report, because I want this fixed! =)

Hi, i can´t configure my wordpress based blog, flock and ScribeFire says to me that it can´t find any API in my blog...

Help me....~!

Hi, i can´t configure my wordpress based blog, flock and ScribeFire says to me that it can´t find any API in my blog...

Help me....~!

Guys, try to go to the bug report Daniel was kind enough to provide. Voting and commenting on that thread will help us get this issue addressed!

Hi, I just made it.
It is working now. I have 2 blogs on the same server. In one the Blog This was working and in the other it wasn't.
I compared the 2 xmlrpc.php files and found one difference.

The one working had this line different:
# fix for mozBlog and other cases where '<?xml' isn't on the very first line
if ( isset($HTTP_RAW_POST_DATA) )
$HTTP_RAW_POST_DATA = trim($HTTP_RAW_POST_DATA);

The one which was not working had this:

# fix for mozBlog and other cases where '<?xml' isn't on the very first line
if ( isset($HTTP_RAW_POST_DATA) )
$HTTP_RAW_POST_DATA = mysql_escape_string(trim($HTTP_RAW_POST_DATA));

I copied the working xmlrpc.php file (BACKUP YOUR OLD ONE!) to the other server and everything worked.
I hope this helps everyone.

@daniel -- thanks! I just tried your fix and so far it looks to be working great.

Thanks so much for sharing this.

I tried Daniel's fix for mine and the code I had was already correct. Flock still won't detect wp as my API. Any other ideas?

actually nevermind I got it working

The solution for me was:
Create an an .htaccess file, upload to website root directory. The file contains:

SecFilterInheritance Off

ref: http://codeinzen.net/2007/10/27/xml-rpc-issue-with-wordpress/

sorry - the code in previous post didn't copy properly. See the referenced site.
(http://codeinzen.net/2007/10/27/xml-rpc-issue-with-wordpress/)

I had the same problem connecting my blog with Flickr, so at least in my case, I do not believe it is a problem on the Flock side. I scoured the forums in regards to the flickr/blog issue, and found about 30% of the folks finding solutions....none worked for me nor many others....

Daniel's Fix worked for me. I.e, editing xmlrpc.php to remove the "mysql_escape_string". I'm not sure whether to call this a Flock problem or a Wordpress problem, but other clients (MarsEdit, Ecto) worked without needing this hack.

I can't endorse this fix in general. "mysql_escape_string" is often used to clean up input to prevent SQL injection attacks-- removing it could have security ramifications.

people...
i had the same problem, and first checked everything in this post:
erwan
November 28, 2007 - 2:19pm

Everything seemed fine, but still no movement. Than i figured it had to be a simpler problem...

maybe some of you are looking too far... if you are using wordpress.org...
Go to this link: http://yourblog.com/wp-admin/options-writing.php
and make sure that the checkbox that goes with the line "Enable the WordPress, Movable Type, MetaWeblog and Blogger XML-RPC publishing protocols." is checked! By default it is turned off.

This simple "fix" has killed the "bug" for me.
Works like a charm.

Any luck for you guys?

Indeed, that worked a trick for me ;-)

Ubertight - Bert Deckers...

You are a prince among men... It worked like a charm!

Everything was solved just as Ubertight - Bert Deckers describe.
Thanks, regards.

Spent about an hour messing with the "flock-ing" thing until I found this post. Thanks much for making my afternoon!