[meta] BlogAPI 7.x-2.x Release Blockers [#1435162]

Comment #0.0

cweagans

He/Him

English

Boise, ID, USA

commented 10 February 2012 at 06:32

Issue summary:

View changes

Adding tasks

Log in or register to post comments

Comment #1

archimedes commented 23 May 2012 at 16:19

Any idea when these blockers will be resolved, and a 7.x-2.x release will be published?

Log in or register to post comments

Comment #2

cweagans

He/Him

English

Boise, ID, USA

commented 24 May 2012 at 04:53

I haven't had a lot of time to work on it lately. I've just started at Advomatic, though, and they do give me some time to spend on Drupal contribution. I'll see if I can spend some time on Blog API next week.

Thanks for your interest!

Log in or register to post comments

Comment #3

amccaugh commented 4 June 2012 at 18:08

Also posting to show interest in the resolution of release blockers. Been quite a while since I've noticed any new information

Log in or register to post comments

Comment #4

schultz11 commented 14 June 2012 at 20:36

I get a permissions error attempting to post from both Ecto and MarsEdit.

Log in or register to post comments

Comment #5

csc4 commented 27 September 2012 at 11:57

Also hoping to see a release - project page says it's been 27 weeks since the last release despite chip in target being met and Drupal 8 now seems to be imminent a Drupal 7 version would be great!

Log in or register to post comments

Comment #6

amccaugh commented 27 November 2012 at 22:08

Well, looks like cweagans (Cameron Eagans) took the donated money (~$700) and ran. I contacted the donors of the ChipIn program and they were unable to get a response either, I'm going to try to get a hold of the Acquia company too but it's a bit of a pain. Really unfortunate about the whole thing, BlogAPI really is a great program.

Log in or register to post comments

Comment #7

cweagans

He/Him

English

Boise, ID, USA

commented 27 November 2012 at 22:42

I haven't gone anywhere. I've been busy and haven't been able to spend as much time on Blog API as I was hoping to. The code is mostly complete, but non functional - right now, I'm writing tests for the functionality so that I can see what's wrong. BlogAPI is a gigantic PITA to debug because most BlogAPI clients don't give detailed debugging information.

All I can say is that there has been progress, but not as much as I (or you) would have hoped. Sorry for the wait.

Log in or register to post comments

Comment #8

cweagans

He/Him

English

Boise, ID, USA

commented 27 November 2012 at 22:42

Title:

[META] BlogAPI 7.x-2.x Release Blockers

» [meta] BlogAPI 7.x-2.x Release Blockers

Now with less capslock.

Log in or register to post comments

Comment #9

amccaugh commented 31 March 2013 at 05:38

I don't understand, from reading the other open issues you've claimed it's "almost complete" for the better part of 6 months now. You can claim all you want that you've been working on it, but there's simply nothing to show for it -- not even code that doesn't work. It's been *over a year* since there was any kind of update to the source. Not to underestimate the complexity of getting code like this to work on multiple blogging clients, but it's ridiculous to claim you've been working on it if you can't even get an open source blogging client like Thingamablog to post, for example, only text.

Log in or register to post comments

Comment #10

cweagans

He/Him

English

Boise, ID, USA

commented 11 April 2013 at 15:34

This email went out last night to people that have previously contacted me about BlogAPI. Reposting here for anyone that didn't get that message:

Good evening everyone,

As you probably know, BlogAPI was successfully funded by a ChipIn in December of 2011, in large part by Acquia (thank you Acquia and everyone else that contributed!).

However, since then, I've had some personal issues come up that have made it difficult to find time to work on BlogAPI. I know that 16 months is a long wait for the module, and I do apologize for that. I won't try to make excuses because anything that I can say will not do justice to the fact that it has taken so long to get the module in a working state. I dropped the ball, and I'll own that.

However, you might be happy to know that as of tonight, BlogAPI is working with ScribeFire. In the next few days, I'll be continuing to manually test and refine the code so that it works with other BlogAPI clients (MarsEdit is next on the list, followed by Windows Live Writer, Ecto, and perhaps MacJournal). There are a handful of automated tests in place currently. I'll also be continuing to add tests for the functionality currently in the module so that the testbot can tell me/us when I'm doing something wrong.

If you have any questions/concerns/comments/rants, feel free to reply to this email.

Again, I'm sorry for the delay. Talk to you soon!
--
Cameron Eagans

Log in or register to post comments

Comment #11

JuggoPop commented 30 April 2013 at 22:14

@cweagans - I have been looking at software called "Clarify" (which seems to be a forked version of ScreenSteps, made by the same company)... I came across this thread:

http://help.bluemangolearning.com/m/publish-to-web/l/10786-configuring-d...

In that, they show how to use Blog API on Drupal to setup automatic posting from ScreenSteps to Drupal 6. Their comments say they are waiting on a release of Blog API for 7 before making sure it works as expected on their end. Do you know anything about a connection with ScreenSteps? or at what stage you might say it is solid enough to give it a try, etc?

I don't see that listed in your test list (which I understand, as it is not a blog really) but I was just wondering what portions of the unique connections you might know need to be in place for something like this.

Thank you for any info you have in response.

Log in or register to post comments

Comment #12

cweagans

He/Him

English

Boise, ID, USA

commented 30 April 2013 at 22:28

I have no idea what they're doing under the hood, but I'm assuming that if it works with D6 BlogAPI, it will also eventually work with D7 BlogAPI with no changes on their part (since D7 BlogAPI is going to be exposing the same API, albeit at a different endpoint. If they're using the EditURI feature correctly, things should "just work". If they've hardcoded /xmlrpc.php into their application, then things will probably not work as expected.

I left a comment there letting them know I'm the BlogAPI maintainer and to please send any technical details they have my way, and I'll try to make sure that it continues to work in D7 (though I cannot promise regular testing).

Log in or register to post comments

Comment #13

breaklaw commented 22 May 2013 at 13:55

Is anyone up for another ChipIn? With all due respect to the maintainer, I'm in a situation of being forced to upgrade to D7, and now having no feasible workflow for posting new content. I haven't found a fix yet so it is very much worth it to me to try to throw money at this problem. Was the last total 700? I can start it off with half that right now if people are interested. I'm sure we can get someone to hack together something out of the two D7 blogapi modules and the D6 WLW version.

Log in or register to post comments

Comment #14

cweagans

He/Him

English

Boise, ID, USA

commented 22 May 2013 at 20:36

I am at Drupalcon this week and I'm working with a couple of people getting BlogAPI ready for a release. My goal is to have at least an alpha release by Sunday night.

Log in or register to post comments

Comment #15

bruce.wins commented 21 June 2013 at 14:34

So did anything happen with the new Chip In? Years keep going by and it does seem that at least a few people are interested. Is there a Drupal Group or a place to post threads about a ChipIn or another type of group effort?