Loading Profile...
How do I find out about updates to TypePad's AtomAPI?
TypePad seems to have updated the AtomPub implementation within the last few days. This has broken our client (an exporter). Where do you update customers on upcoming related changes to this API?
I searched on
http://everything.typepad.com/
http://developer.typepad.com/
I searched on
http://everything.typepad.com/
http://developer.typepad.com/
3
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company .
The best answer from the company
-
Hi everyone, I’m Nima @ Six Apart and I work with David Recordon on our API Platforms. Earlier this week David told you about our plan to fix this bug.
It’s clear that as we dig into the problem that it’s more complex to address for the whole community than we thought, so we’re going to address the root cause – meaning it’s going to take more cycles to fully solve the issue.
We plan to enable getting comments via the Atom Pub API, and expect to release that the week of August 17th. In the meantime, if you have any burning issues we’re more than happy to work directly with you on a work-around via comment feeds.
I’m happy to help
The company says
this answers the question
-
Inappropriate?I would be also interested in getting to know this. It seems the comment identifiers are changed from rel="entry.comments" to rel="replies" but on the urls provided in this attribute I do not receive any content. Also it seems that now blog_ids and post_ids are strings and not integers any longer. -
Inappropriate?As you might know, over the past year we've been working on transitioning all of TypePad's blogs to a new platform. As a result you'll see changes such as IDs becoming strings and other small changes (like the link relations) in our APIs. Unfortunately, our Comments service endpoint in AtomPub does not currently seem to be working. I've begun working with our engineering team to resolve this bug and will provide an update once I know when it will be fixed.
While I know that this won't fit into your AtomPub implementation directly, we do offer per-post feeds of comments which you can discover on an entry's permalink page like http://blog.davidrecordon.com/2008/12.... Hopefully these feeds will be able to help until our AtomPub Comments service is fixed.
As for where to subscribe to updates, we try to include them in Everything TypePad when they are user facing though this specific issue is a bug versus a desired change to the API. You should also watch http://developer.typepad.com/ as we'll be making some changes to it over the next few months. -
Inappropriate?Thanks for the timely response David. Really appreciate you keeping us posted on when this is fixed. Do you expect it to be resolved this week?
Thanks also for the suggestion for a possible work around. Unfortunately, it seems for these couple of customer's blogs that I've tried removing the .html and appending /comments/atom.xml from a permalink page don't seem to work. I'm guess they don't have those templates added, and I hate to mess around with their live sites.
Is there a feed to subscribe to where changes like those in IDs is shared? This sort of change can obviously have significant impact to AtomPub clients depending on how they are coded and the programming environment.
Back near the beginning of April, Typepad also changed the login mechanism breaking the TP web importer than a member of the WordPress community had been working on. Although, it was reasonable to resolve the issue. Knowing about it would have been very useful.
http://developer.typepad.com/ does not advertise a feed nor http://developer.typepad.com/apis/ato... , also http://developer.typepad.com/apis/ato... does not seem to be dated (nor it's change log).
Thanks again for all of your help. -
Inappropriate?The fix for this API is currently scheduled for our release the week of June 22nd, though we're more than happy to work directly with any customers on a work around via comment feeds between now and then. Over the next few months we'll be updating http://developer.typepad.com/ with more documentation and feeds.
-
Inappropriate?This is great news. Thank you!
-
Inappropriate?It seems the change make it worse. Our AtomPub client is now getting no content. Do you have a working example client?
I’m frustrated
-
Inappropriate?After further debugging:
Problem 1 is RSD seem to be gone from blogs. Makes finding the atom endpoints extra fun -- won't this breaks many blog clients?!
Problem 2 still no comments.
I’m frustrated
1 Comment Add a comment
This answers the question
-
Problem 1 seems to be specific to this customer's template. Sorry, for that distracting detail.
We've adjusted to the other changes, but Problem 2: still no comments. Any help would be greatly appreciated. -
Inappropriate?Hi David,
Is there a time estimate on the comments API issue? "we're more than happy to work directly with any customers on a work" I'm a customer and we have a number of blogs on the platform. Please let me know how this issue can be resolved. I'm available any time to discuss. Thanks...
I’m confused
-
Inappropriate?Hi everyone, I’m Nima @ Six Apart and I work with David Recordon on our API Platforms. Earlier this week David told you about our plan to fix this bug.
It’s clear that as we dig into the problem that it’s more complex to address for the whole community than we thought, so we’re going to address the root cause – meaning it’s going to take more cycles to fully solve the issue.
We plan to enable getting comments via the Atom Pub API, and expect to release that the week of August 17th. In the meantime, if you have any burning issues we’re more than happy to work directly with you on a work-around via comment feeds.
I’m happy to help
The company says
this answers the question
2 Comments Add a comment
This answers the question
-
Hi Nima,
What are the suggested workarounds for this? If we need to stand up specific comment templates or pages, please let us know, it's critical we get this sorted out by the end of this month. Any help would be appreciated and more than happy to jump on a call with you if that's needed. If you need to reach me directly, I'm at clarence_kwei@timeinc.com
Thank you. -
Working around it with the comments feed seems to be an option in general. One thing I could not figure out so far is how to get more than 100 comments from the feed. In the regular atom pub feed there was an option to add the parameters /offset=0/limit=20 to the feed url in order to page through the comments. This seems not to be working with the comments feeds at /comments/atom.xml . Could you please advise how to get all comments with the comments feeds
-
Inappropriate?Hi Clarence,
At the current time, Thorsten's suggested workaround is a good solution in the short term.
1 Comment Add a comment
This answers the question
-
Not really as it is only working for up to 100 comments per post. How to receive the rest?
-
Inappropriate?Hi all - I'm going to find the right person on our staff to help with this, since I don't know off the top of my head.1 Comment Add a comment
This answers the question
-
Is there any movement on this? I'm about to send Chris Alden an email. Please let me know. Thanks.
-
Inappropriate?Clarence, Thorsten,
Yes, the temporary work around is hard limited to 100 comments per post. Your situation must be a long tail if you have more than 100 comments per post. Have you also tried using the blog export function and scraping the comments that way?
Thanks,
Nima
3 Comments Add a comment
This answers the question
-
These are really big blogs. Any time I've tried to use the export function, it's stopped long before a complete export.
-
The last time I tried to export such a large blog it stops at around 120 MB download size or better said after 5 Minutes. This seems to be caused by the keepalive time of the webservers on TypePad side. Paired with the speed limitation TypePad seems to have in place I was not able to get more than 120 MB through the exporter. Please let me know if there is something we can try to get around this limit.
-
as Nima said above - the full fix for this should be out in a few weeks. In the meantime, the workaround is hard-coded at 100 comments. I wish there was a speedier resolution for you, but that's where we're at currently as far as I know.
-
Inappropriate?Today, we discovered that your encoding for AtomPub appears to be broken -- it goes back to at June 16th. All html tags are encoded as <default1:>. For example, <default1:em>Straw Dogs</default1:em>.
We are noticing <default1>Straw Dogs</default1> meaning that the closing tag does not include the information about what tag is transformed. Also, not there is a space now between the tags which is also annoying.
We are trying to come up with a solution to work around this on our end.
Why is this? Seems like unnecessary, and causes a lot of extra processing.
I’m incredibly frustrated
3 Comments Add a comment
This answers the question
-
I guess b/c of the space, the code was lost, it should be <default1 :em>Straw Dogs</default1>
-
On further investigation, I don't know when this issue was introduced, because to fix author mapping we had recently re-imported the blogs.
Do you know of a know of an (open source) AtomPub client that can process the </default1> , so we can model our code after it? -
Turns out the the </default1> only tags were caused by someone turning on "WordPress should correct invalidly nested XHTML automatically"
EMPLOYEE
EMPLOYEE
EMPLOYEE
