Closed (won't fix)
Project:
Blog API
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Mar 2011 at 04:20 UTC
Updated:
10 Feb 2012 at 06:11 UTC
I guess the node object of drupal 7 is different from drupal 6, however, I modified something about language and the node object structure, and It can work a little.
I'll post my patch, with which I can post articles via blogapi now(just a simple post, contains title, mt_excerpt, description, etc), but the taxonomy still can't be set, and newMedia feature has not test yet.
| Comment | File | Size | Author |
|---|---|---|---|
| new-post-function.patch | 5.2 KB | alan.liu |
Comments
Comment #1
paul o brien commentedusing Ecto on Mac.
applied patch new-post-function.patch.
but still get message 'Received HTML from server instead of XML. Is the access point correct?'
any suggestions?
Comment #2
rjohnson42 commentedAs I said in my issue post, when the blogapi module is called from ScribeFire and Word to create a post, the blogapi code calls drupal_submit_form to simulate a login by the user, but for some reason this call fails and does not return code to the blogapi module, but returns some kind of error to the application. If I use the Python xmlrpc client to make a blogapi call, it all works fine. I have not yet seen what is different about these two cases. My Python tester is able to create a new media object, create a post, get a post and edit a post using metaWeblog.
Comment #3
cweagansThe 2.x rewrite will fix this.