ANN: Blogger GData bugfixes

Late last week we pushed out a few bug fixes to the GData
API:

 - <title> element is no longer a post snippet for
posts with no title
 - published date is now settable via the API


-- Pete

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Blogger Data API" group.
To post to this group, send email to bloggerDevgooglegroups.com
To unsubscribe from this group, send email to
bloggerDev-unsubscribegooglegroups.com
For more options, visit this group at http:
//groups.google.com/group/bloggerDev?hl=en
-~----------~----~----~----~------~----~------~--~---

Hey thanks.  The published date change is much appreciated.

-John


On Aug 27, 7:00 am, "Pete Hopkins ☠"
<phopk...google.com> wrote:
> Late last week we pushed out a few bug fixes to the
GData API:
>
>  - <title> element is no longer a post snippet
for posts with no title
>  - published date is now settable via the API
>
> -- Pete


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Blogger Data API" group.
To post to this group, send email to bloggerDevgooglegroups.com
To unsubscribe from this group, send email to
bloggerDev-unsubscribegooglegroups.com
For more options, visit this group at http:
//groups.google.com/group/bloggerDev?hl=en
-~----------~----~----~----~------~----~------~--~---

Removing the title element seems to break some feed
consumers, like
the "recent comments" Blogger widget and Firefox's
"live bookmarks"
feature.  Is there a reason for this change?  Is it
possible/likely
that the change will be rolled back?

On Aug 27, 9:00 am, "Pete Hopkins ☠"
<phopk...google.com> wrote:
> Late last week we pushed out a few bug fixes to the
GData API:
>
>  - <title> element is no longer a post snippet
for posts with no title
>  - published date is now settable via the API
>
> -- Pete


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Blogger Data API" group.
To post to this group, send email to bloggerDevgooglegroups.com
To unsubscribe from this group, send email to
bloggerDev-unsubscribegooglegroups.com
For more options, visit this group at http:
//groups.google.com/group/bloggerDev?hl=en
-~----------~----~----~----~------~----~------~--~---

On 8/28/07, César <crinconet.com.mx> wrote:
>
> Removing the title element seems to break some feed
consumers, like
> the "recent comments" Blogger widget and
Firefox's "live bookmarks"
> feature.  Is there a reason for this change?  Is it
possible/likely
> that the change will be rolled back?

Right now we're looking at ways to balance making the Atom
feed a
correct representation of the post -- for Atom Publishing
Protocol
clients -- and making the feed work the best in various feed
readers.

I'm open to suggestions in this area.

However, a fix at least for the Blogger Feed widget to work
better
with feeds that don't have titles is in the works.

-- Pete

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Blogger Data API" group.
To post to this group, send email to bloggerDevgooglegroups.com
To unsubscribe from this group, send email to
bloggerDev-unsubscribegooglegroups.com
For more options, visit this group at http:
//groups.google.com/group/bloggerDev?hl=en
-~----------~----~----~----~------~----~------~--~---

I see.  RFC 4287 does mandate explicitly:

"atom:entry elements MUST contain exactly one
atom:title
element." (§4.1.2)

Empty titles are not explicitly forbidden.  However, in
§4.1.1.1 there
is this note:

"It is advisable that each atom:entry element contain a
non-empty
atom:title element, a non-empty atom:content element when
that element
is present, and a non-empty atom:summary element when the
entry
contains no atom:content element."

Given this, and the fact that at least the Firefox client is
widely
deployed and absolutely needs the titles (certainly a
shortcoming in
the client), I really do think some kind of title should
always be
generated.

Personally, I think a snippet from the content is the best
option, at
least for comments.  But if that is not palatable, how about
"comment
in <post's title>"?  That doesn't work as good in
a "live bookmark",
but it does convey a piece of useful information not
available
anywhere else in the entry, namely the post title.

 -CR

On Aug 28, 3:11 pm, "Pete Hopkins ☠"
<phopk...google.com> wrote:
> On 8/28/07, César <crin...et.com.mx> wrote:
>
>
>
> > Removing the title element seems to break some
feed consumers, like
> > the "recent comments" Blogger widget and
Firefox's "live bookmarks"
> > feature.  Is there a reason for this change?  Is
it possible/likely
> > that the change will be rolled back?
>
> Right now we're looking at ways to balance making the
Atom feed a
> correct representation of the post -- for Atom
Publishing Protocol
> clients -- and making the feed work the best in various
feed readers.
>
> I'm open to suggestions in this area.
>
> However, a fix at least for the Blogger Feed widget to
work better
> with feeds that don't have titles is in the works.
>
> -- Pete


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Blogger Data API" group.
To post to this group, send email to bloggerDevgooglegroups.com
To unsubscribe from this group, send email to
bloggerDev-unsubscribegooglegroups.com
For more options, visit this group at http:
//groups.google.com/group/bloggerDev?hl=en
-~----------~----~----~----~------~----~------~--~---

I'm seeing the same published date behavior as
before--custom dates
during POST are respected, but they can't be changed on PUT.
What
exactly was the change that went in last week?

On Aug 27, 7:00 am, "Pete Hopkins ☠"
<phopk...google.com> wrote:
>  - published date is now settable via the API


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Blogger Data API" group.
To post to this group, send email to bloggerDevgooglegroups.com
To unsubscribe from this group, send email to
bloggerDev-unsubscribegooglegroups.com
For more options, visit this group at http:
//groups.google.com/group/bloggerDev?hl=en
-~----------~----~----~----~------~----~------~--~---

I was going to make the same point but decided to experiment
more
first.  At first blush it looks like you can't modify the
date via
POST.

-jm


On Aug 28, 2:35 pm, "Joe Cheng [MSFT]"
<joe.ch...gmail.com> wrote:
> I'm seeing the same published date behavior as
before--custom dates
> during POST are respected, but they can't be changed on
PUT. What
> exactly was the change that went in last week?
>
> On Aug 27, 7:00 am, "Pete Hopkins ☠"
<phopk...google.com> wrote:
>
> >  - published date is now settable via the API


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Blogger Data API" group.
To post to this group, send email to bloggerDevgooglegroups.com
To unsubscribe from this group, send email to
bloggerDev-unsubscribegooglegroups.com
For more options, visit this group at http:
//groups.google.com/group/bloggerDev?hl=en
-~----------~----~----~----~------~----~------~--~---

On 8/29/07, loghound (John McLaughlin) <loghoundgmail.com> wrote:
>
> I was going to make the same point but decided to
experiment more
> first.  At first blush it looks like you can't modify
the date via
> POST.

*sigh*. It appears that with the production setup we have a
bug
whereby changing the post date in this manner is causing an
exception
that prevents the post from being saved. Looking into this.
Sorry to
get your hopes up.

-- Pete

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Blogger Data API" group.
To post to this group, send email to bloggerDevgooglegroups.com
To unsubscribe from this group, send email to
bloggerDev-unsubscribegooglegroups.com
For more options, visit this group at http:
//groups.google.com/group/bloggerDev?hl=en
-~----------~----~----~----~------~----~------~--~---

On 8/31/07, Pete Hopkins ☠ <phopkinsgoogle.com> wrote:
> On 8/29/07, loghound (John McLaughlin) <loghoundgmail.com> wrote:
> >
> > I was going to make the same point but decided to
experiment more
> > first.  At first blush it looks like you can't
modify the date via
> > POST.
>
> *sigh*. It appears that with the production setup we
have a bug
> whereby changing the post date in this manner is
causing an exception
> that prevents the post from being saved. Looking into
this. Sorry to
> get your hopes up.

Ok, this should be working for reals now. Give changing post
date via
a PUT another go.

-- Pete

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Blogger Data API" group.
To post to this group, send email to bloggerDevgooglegroups.com
To unsubscribe from this group, send email to
bloggerDev-unsubscribegooglegroups.com
For more options, visit this group at http:
//groups.google.com/group/bloggerDev?hl=en
-~----------~----~----~----~------~----~------~--~---

On 8/28/07, César <crinconet.com.mx> wrote:
> Personally, I think a snippet from the content is the
best option, at
> least for comments.  But if that is not palatable, how
about "comment
> in <post's title>"?  That doesn't work as
good in a "live bookmark",
> but it does convey a piece of useful information not
available
> anywhere else in the entry, namely the post title.

We pushed out a fix in this area last night. Comment entries
now have
a snippet of comment text as the title. Posts will not have
snippetized titles, however.

-- Pete

> On Aug 28, 3:11 pm, "Pete Hopkins ☠"
<phopk...google.com> wrote:
> > On 8/28/07, César <crin...et.com.mx> wrote:
> >
> >
> >
> > > Removing the title element seems to break
some feed consumers, like
> > > the "recent comments" Blogger
widget and Firefox's "live bookmarks"
> > > feature.  Is there a reason for this change? 
Is it possible/likely
> > > that the change will be rolled back?
> >
> > Right now we're looking at ways to balance making
the Atom feed a
> > correct representation of the post -- for Atom
Publishing Protocol
> > clients -- and making the feed work the best in
various feed readers.
> >
> > I'm open to suggestions in this area.
> >
> > However, a fix at least for the Blogger Feed
widget to work better
> > with feeds that don't have titles is in the works.
> >
> > -- Pete
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Blogger Data API" group.
To post to this group, send email to bloggerDevgooglegroups.com
To unsubscribe from this group, send email to
bloggerDev-unsubscribegooglegroups.com
For more options, visit this group at http:
//groups.google.com/group/bloggerDev?hl=en
-~----------~----~----~----~------~----~------~--~---