blog api

No, Blog API REALLY Sucks...

Okay, the Blog API sucks even worse than I just described.

If you use it to edit content that is already published

1. You lose all of your categories/free-tagging. So after I made a post, then edited it on the website manually to add the tags I wanted, I tried to re-edit it in my external client app (Drivel). Submitting the update wiped all categories that it had been previously assigned.

2. Upon an update, the original node is wiped and replaced. I was under the impression that it would just update the text in the body field, if that was what was edited. Nope, it created a new node. This messed up my Pathauto automatic URL and everything. I had to go and manually restore it to get back what I wanted.

So in short, this blows. I think I will not be using it any more until some improvements are made. I will leave it enabled just in case I want to use it, but I can't see using it for much.

Blog API Sucks

So I thought it would be cool to activate the Blog API. I soon found its limitations.

What this does is allow users to post content to their blog via an external client application. I am currently using Drivel under Linux. I got it set up and working and am using it to write this post. However, to me one of the biggest drawbacks to using it much is the category setting / lack of functionality.

It is nice to be able to type up a basic entry offline. I find that text entry is more responsive and I don't have to worry about some web weirdness or anything losing my text. But the two biggest pains are:

Syndicate content