Re: Re: prevPageToken problem

Ahh, yes. Blogger v2 JSON API shouldn't be used. It grew new functionality
and had a vesion bump to v3. v2 JSON API to v3 upwards migration should
consist solely of a scope change, or replacing your client library with a
newer rev.

See the relevent docs here:
https://developers.google.com/blogger/docs/3.0/reference/index


On Fri, Jan 31, 2014 at 12:23 PM, Doug Jolley <[email protected]> wrote:

> > As the "nextPageToken" effectively remembers your offset from the start
> of
> > the stream of articles, the page offset for the first page is zero, and
> thus the
> > nextPageToken you need to get there is the empty one.
>
> Thanks, Brett.  Upon reflection following the submission of my post, I
> actually realized that on my own.  However, I do appreciate your pointing
> it out.
>
> > Due to various internal implementation reasons,
> > we had to take away the ability to supply previous page tokens.
>
> So, it is my understanding that Google does not regard this as a bug and
> therefore has no plans to ever provide previous page tokens.  That means
> that we developers are going to have to implement the Previous Page
> function on our own.  (Note that this is not a work around.  It's the
> implementation of a new feature.)  I can see how this is possible.  It's a
> bit of an undertaking and having to do so definitely diminishes the utility
> of the API.  Let me ask this question:  Do you think that Google would be
> able to help us by passing back a currentPageToken?   Having both the
> currentPageToken and the nextPageToken readily available would (IMHO)
> simplify the task of implementing the Previous Page function.
>
> > Where in the documentation are we still referencing them?
> > I need to update that part of the docs.
>
> See the section entitled, "Retrieving Posts from a Blog" at this URL, "
> https://developers.google.com/blogger/docs/2.0/json/using".
>
> > Sorry for the confusion...
>
> No problem.  I think up until now most developers have been laboring under
> the assumption that Google was going to come up with a fix.  At least it is
> nice to now have the certainty of knowing that that is not going to happen
> so that we can plan accordingly.
>
> Thanks.
>
>             ... doug
>
>>   --
> You received this message because you are subscribed to the Google Groups
> "Blogger Developer Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/bloggerdev.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 

Brett Morgan | Developer Relations Engineer, Google Maps |
[email protected] | profiles.google.com/brettmorgan

-- 
You received this message because you are subscribed to the Google Groups "Blogger Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/bloggerdev.
For more options, visit https://groups.google.com/groups/opt_out.