I wanted to add a new blog and In the third step I have to enter “https://example.com/xmlrpc.php” but I don’t have this page . I mean when I wanted to enter this page , It showed me 404 error and It wasn’t .
I want to know what should I do ? What should I enter in this box ?
Thanks
]]>BUT if I go into my WP admin, edit the post (uploaded by BlogDesk), delete the image then use the Image Upload tool to grab the exact same file from the media library and reinsert it into the post – bam – the thumbnail shows up.
I have tested this with and without the plugin “Get The Image” – no change.
I did look at the html script in WP before and after reinserting the image. The photo shows up like this:
<img src="https://manofaustin.com/wp-content/uploads/2009/06/junkamilksat-11.jpg" alt="JUNkamilK3" width="375" height="434" />
I then delete it and reinsert through the image uploader and the same file now shows up in the post like this:
<img class="alignnone size-full wp-image-3056" title="junkamilksat-1.jpg" src="https://manofaustin.com/wp-content/uploads/2009/06/junkamilksat-11.jpg" alt="junkamilksat-1.jpg" width="375" height="434" />
Looks like it’s a script issue. BlogDesk does give options for alignment which I have used but no change. I contacted BD but they believe it’s a WP issue.
Anyone else having this problem? Any ideas on resolving this?
THANKS!
]]>could someone help me. what’s wrong with my wordpress ?
thank you.
]]>WP’s xmlrpc.php calls a file class-IXR.php in the wp-includes folder. The problem I have is that my hosting server (GoDaddy) is case sensitive. and the file had the name class-ixr.php. After I changed the filename to match the xmlrpc call, no more problems (so far.)
Just something to look at so you do not tear your hair out like I did.
]]>I have tried
-Ecto
-W.Bloggar
-BlogDesk
I think Ecto seems best, I don’t mind paying for it, I just couldn’t figure out how to edit past posts with it, maybe I’m just slow.
What do you think?
]]>Actually, both also support FTP uploads, and these do in fact work, but for a specific project I want the WP DirectUpload to be used, so I’m working toward that end.
We’re talking about links in the posted message – for example, an document in PDF format.
Some files will upload okay – pictures (jpg, gif, probably others although I haven’t tried others yet) work, as do .txt files. It looks like MS .doc files work, but neither PDF nor Open Office .odt will post – they generate xmlrpc errors. .doc files upload okay.
In the wp-admin post/edit upload of .doc works, upload of .pdf works, but .odt is rejected with the message: “File type does not meet security guidelines” – yup, yup, .doc files are okay despite the notorious macro exploits, but .odt files don’t meet security guidelines.
I have two questions: (1) what might I try to do about the problem with the xmlrpc upload failure, and (2) how do I whack the security guideline into accepting .odt files?
WP servers are my own and a client’s Fedora Core 4 machines with virtual domain hosting.
]]>Conditions:
Fairly new blog hosted at Dreamhosts.com. Latest WordPress according to them. Freshly downloaded copy of BlogDesk. Dell laptop running XP SP1.
Symptoms:
The first two posts I made using BlogDesk went to the server fine but would not show up on my blog. They showed up in the “manage posts” control panel and even previewed properly from the control panel but they would not display.
I had this very same problem over the weekend while testing ETCO. I didn’t spend any time troubleshooting that one. I’m trying to evaluate all the blog editors so I didn’t want spend much time with any one package.
After experimenting around with the control panel I decided to brows the sql database for my blog. dreamhosts.com has a nice browser. I selected the table wp_posts and looked over the data.
I found that in the wp_posts table, the post_status had been set to “future” on the problem posts. Those were the only two records that contained “future”. The rest contained “published” or “draft” as appropriate. I confirmed that this field is changed by the control panel “status” buttons by setting it to “draft” and checking the database. Clicking the “publish” button in the WP control panel, however, set it back to “future”. I manually edited the table and set post_status to “publish” and the article showed up properly in my blog.
Problem is, I can’t make the problem come back. It seemed to go away after I did another post from BlogDesk and selected “change time to” and changed the time one minute. That killed the bug. Unchecking the box did not bring the bug back.
As it stands now, posting from BlogDesk is working properly. However, this did happen on two posts. It also happened with ETCO on every of the several posts I tried.
I don’t do forums so if you have questions, please go here: https://www.neon-john.com and click the “mail John” button.
John
]]>My xmlrpc.php file is in https://wilde-world.co.uk/xmlrpc.php
However when I try to get Flickr to point to it so I can blog photos, it says it has an error and suggests that my blog and username and password is to blame.
I also try to get ScribeFire to point to my blog and while it finds my blog’s xml-rpc on its own it won’t log in either with my admin account or the seperate account I have set up with it, claiming that the username and/or password is incorrect.
This is not true as I can log in directly to my WordPress install using both accounts so they do work.
So, what is wrong with my XML-RPC guys?
]]>I tried BlogDesk today with my WordPress 2.0.4 (german version) blog. Everytime it tries to get the blog id it got the error 403 – the server understood the command but don’t allow it.
I wrote some stuff about the 403 error already and so I already tried to renamed the file, changed the file permissions to 777, added a new user to the blog and tried this user/password combination, disabled all plugins but nothing I got everytime the 403 error in blogdesk.
When I enter the xmlrpc.php in the browser I got the message “XML-RPC server accepts POST requests only.” and my hoster told me that they don’t block this file.
What could be the problem?
Thanks
Thomas
PS: The new Live Writer from microsoft got the same 403 problem.
]]>