Today we released a much-requested feature for Blogger's GData feeds: the orderby parameter.
Now you can add orderby=published or orderby=updated to a GData query to get the posts sorted in that order.
Some notes: - updated is the default - This has no effect on comments feeds, whose updated and published dates are the same - Pagination in the by-updated feed is limited to the most recently published 500 posts. We hope to eventually remove this limitation.
Great! I didn't request this, but I can tell my users are going to be happy with it, since MarsEdit tends to organize things in a "by published" order.
Did I interpret things naively? I just tried tacking the parameter to the end of the GET URL for the feed (an approach that I later noticed is endorsed by the GData documentation). This gave me the following URL (for instance):
> Today we released a much-requested feature for Blogger's GData feeds: > the orderby parameter.
> Now you can add orderby=published or orderby=updated to a GData query > to get the posts sorted in that order.
> Some notes: > - updated is the default > - This has no effect on comments feeds, whose updated and published > dates are the same > - Pagination in the by-updated feed is limited to the most recently > published 500 posts. We hope to eventually remove this limitation.
> Great! I didn't request this, but I can tell my users are going to be > happy with it, since MarsEdit tends to organize things in a "by > published" order.
> Did I interpret things naively? I just tried tacking the parameter to > the end of the GET URL for the feed (an approach that I later noticed > is endorsed by the GData documentation). This gave me the following > URL (for instance):
> On Mar 13, 7:55pm, "Pete Hopkins ☠" <phopk...@google.com> wrote: > > Today we released a much-requested feature for Blogger's GData feeds: > > the orderby parameter.
> > Now you can add orderby=published or orderby=updated to a GData query > > to get the posts sorted in that order.
> > Some notes: > > - updated is the default > > - This has no effect on comments feeds, whose updated and published > > dates are the same > > - Pagination in the by-updated feed is limited to the most recently > > published 500 posts. We hope to eventually remove this limitation.
On Mar 16, 10:36 am, "Pete Hopkins ☠" <phopk...@google.com> wrote:
> On 3/15/07, danielpunkass <jal...@gmail.com> wrote:
> It looks like the old Blogger proxying / redirecting GData > implementation is barfing on the new parameter.
> Either use www2 directly or use the Blog*Spot feeds for now.
Thanks - I have been working on the assumption that the blogger.com URLs were the preferred access point to the API. I am not able to easily access my blog through the API "www2.blogger.com/api" for instance, even with an AuthCode.
Is there a preferred way of deriving the new access URLs from the RSD/ service.post information, or is it that the RSD information needs to be updated on blogspot?
> Today we released a much-requested feature for Blogger's GData feeds: > the orderby parameter.
> Now you can add orderby=published or orderby=updated to a GData query > to get the posts sorted in that order.
> Some notes: > - updated is the default > - This has no effect on comments feeds, whose updated and published > dates are the same > - Pagination in the by-updated feed is limited to the most recently > published 500 posts. We hope to eventually remove this limitation.
> Great! I didn't request this, but I can tell my users are going to be > happy with it, since MarsEdit tends to organize things in a "by > published" order.
> Did I interpret things naively? I just tried tacking the parameter to > the end of the GET URL for the feed (an approach that I later noticed > is endorsed by the GData documentation). This gave me the following > URL (for instance):
> But when I fetch that URL, I am seeing a 400 result code with response > text:
> Invalid parameter: "orderby".
> Is it possible the new feature hasn't propogated out to the public > feeds yet? Or am I doing something wrong?
> Thanks, > Daniel
> On Mar 13, 7:55 pm, "Pete Hopkins ☠" <phopk...@google.com> wrote:
> > Today we released a much-requested feature for Blogger's GData feeds: > > the orderby parameter.
> > Now you can add orderby=published or orderby=updated to a GData query > > to get the posts sorted in that order.
> > Some notes: > > - updated is the default > > - This has no effect on comments feeds, whose updated and published > > dates are the same > > - Pagination in the by-updated feed is limited to the most recently > > published 500 posts. We hope to eventually remove this limitation.
> On Mar 15, 10:15 am, "danielpunkass" <jal...@gmail.com> wrote: > > Great! I didn't request this, but I can tell my users are going to be > > happy with it, since MarsEdit tends to organize things in a "by > > published" order.
> > Did I interpret things naively? I just tried tacking the parameter to > > the end of the GET URL for the feed (an approach that I later noticed > > is endorsed by the GData documentation). This gave me the following > > URL (for instance):
> > But when I fetch that URL, I am seeing a 400 result code with response > > text:
> > Invalid parameter: "orderby".
> > Is it possible the new feature hasn't propogated out to the public > > feeds yet? Or am I doing something wrong?
> > Thanks, > > Daniel
> > On Mar 13, 7:55 pm, "Pete Hopkins ☠" <phopk...@google.com> wrote:
> > > Today we released a much-requested feature for Blogger's GData feeds: > > > the orderby parameter.
> > > Now you can add orderby=published or orderby=updated to a GData query > > > to get the posts sorted in that order.
> > > Some notes: > > > - updated is the default > > > - This has no effect on comments feeds, whose updated and published > > > dates are the same > > > - Pagination in the by-updated feed is limited to the most recently > > > published 500 posts. We hope to eventually remove this limitation.
