Re: prevPageToken no longer valid?

Brett Morgan <[email protected]>
Newsgroups gmane.comp.web.blogger.api
Message-ID <CAAFdGScVMGVYg=Tr-H6bvgv-=DTzgqJXoLhVSNbXY+iyMpbwJg@mail.gmail.com>
Ahh sorry, yup. The prevPageToken just went away, because it was invalid in
a number of valid use cases. I'm still in the process of pushing the new
docset for the new release.

brett


On Fri, Oct 11, 2013 at 1:54 PM, Roger <[email protected]> wrote:

> I have had a working query requesting the top 20 most recent blog posts
> that looks like this:
>
> <script src="https://www.googleapis.com/blogger/v3/blogs/{blogId}/posts?callback=blogDataReceived&key={myKey}&maxResults=20&fields=prevPageToken,nextPageToken,items(id,title,published)"></script>
>
>
> Recently (not sure when) this query started failing with the error "Invalid field selection prevPageToken". Sure enough, if I take out prevPageToken, it works but I don't get the previous page token.
>
>
> I reviewed the docs and as far as I can tell it is still a valid field. Did something change?
>
>
> Roger
>
>  --
> 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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.