Reply   |   Start a new discussion topic
Developer Forum » api/user/max-family errors
Started by Private User on 2/21/2012
Displaying all 4 messages
Private User
2/21/2012 at 12:09
1) The next_page URL are missing the /api/ part and does not work
2) The count parameter does not work
Private User
2/27/2012 at 12:21
We are moving away from the to - last weeks release has the setting for switching the URLs prematurely turned on. The new schema will be available in the near future and will be announced in this forum. We will support both URL schemas until all apps migrate to using

Which count parameter do you refer to? The count is not supported across all API calls. In some cases it is very expensive to calculate the size of the paginated list and we deliberately omit the count.
Private User
3/4/2012 at 5:05
To be able to give some user progress when for example loading max family I tried to start with to find how many pages that will be loaded and to be able to load multiple pages in parallel when that number is large.

I do however see that the count is useless for something else since in the theory the count may change during the load process, so it is better to test if you have a next_page link to see that you got all pages.

The redirect by the way to a Page not found
Private User
3/4/2012 at 15:33
Will platform/oauth URL's like change too?