make blogapi autodiscovery (rsd) work with flock
| Project: | Drupal |
| Version: | 4.6.3 |
| Component: | blogapi.module |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
just tried the latest flock and it's integrated blog editor. it uses rsd to automatically discover blog services at a certain uri. so i entered my blogs uri and pressed "next". and flock said "please wait while flock attempts to detect your blog settings..." - and that what is. flock was blocked :)
examining the communication between flock and Drupal with packetyzer, i noticed that Drupal sends a proper rsd response. however, as blogapi_rsd() just "print"s it out, the response is sent as "text/html" instead of "application/rsd+xml" as specified in the "<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://example.com/blogapi/rsd" />". at least my webserver does so.
flock doesn't seem to like this. so i added a "header('Content-Type: application/rsd+xml');" before the print. and voila - flock is happy again.
patch attached.
| Attachment | Size |
|---|---|
| blogapi_3.patch | 581 bytes |
#1
Committed to HEAD and DRUPAL-4-6.
#2
I noticed after applying this patch that I had to empty the cache table to get it to work. Very slick though!
#3
I'm a dev @ flock, and I verified this - XMLHTTPRequest does not know what to do with the rsd file that is sent back from drupal. Thanks for this !
#4
#5
Hello,
Using Flock developer preview, version .4.9
Attempting to connect to a Drupal 4.6.3 site, I completed the following steps:
1. Downloaded and applied blogapi_3.patch to blogapi.module
2. Uploaded patched blogapi.module; activated blogapi.module
3. Cleared the cache table on the database
4. Using Flock, attempted to post a sample blog entry/autodetect my blog using the integrated blog editor; received the error message: "There was an error detecting your blog settings." For the URL of the blog, I tried both the primary site address (http://sub.mysite.com/) and the specific URL of my blog (http://sub.mysite.com/blog/x) -- in both instances, I received the same error message.
One complicating factor: this is on a multisite install, and other drupal sites are running at sub1, sub2, sub3, etc.
So, is this a bug, something obvious I am missing, or some functionality not yet supported in Flock?
Thanks for any help/suggestions.
#6
this is fixed in 4.6.4 - no need to use the patch.