Vilito
Joined: Oct 15, 2014
|
 Posted:
Sep 20, 2024 - 15:31 |
 
|
Description of the Issue:
I'm currently using the FUMBBL API to retrieve match data for the FUMBOWL PreSeason 2024 tournament (ID: 62824). I’m encountering a persistent issue where the API fails to provide the third page of match results.
Here’s a detailed explanation of the behavior:
First Page Fetch:
I use the following API call to fetch the first page of matches:
| Code: | | https://fumbbl.com/xml:group?id=13713&op=matches&t=62824 |
This returns the first 25 matches as expected, along with the <nextPage> element containing a paging value. For example:
| Code: | | <nextPage>4569744</nextPage> |
Second Page Fetch:
I use the paging value from the first page to fetch the second page of matches:
| Code: | | https://fumbbl.com/xml:group?id=13713&op=matches&t=62824&paging=4569744 |
This successfully retrieves the next set of 25 matches (for a total of 50 matches across two pages). However, no <nextPage> element is returned, even though I know there are more matches in the tournament that should be accessible.
Third Page Issue:
The API does not return a <nextPage> value for the third page, which prevents me from fetching additional matches beyond the second page. Given that there are 42 matches in the first round and over 30 in the second round, the inability to access the third page is a significant issue.
Steps to Reproduce:
Fetch the first page of matches for tournament ID 62824 using:
| Code: | | https://fumbbl.com/xml:group?id=13713&op=matches&t=62824 |
Retrieve the <nextPage> value from the response and use it to fetch the second page:
| Code: | | https://fumbbl.com/xml:group?id=13713&op=matches&t=62824&paging=<paging_value_from_first_page> |
Observe that no <nextPage> element is provided in the second page response, despite there being more matches available in the tournament.
Expected Behavior:
After retrieving the second page, the API should return a <nextPage> value to allow access to the third page and beyond. Given that the tournament has more than 70 matches, I expect to be able to retrieve all matches across multiple pages.
Attempts to Bypass the Issue:
I have manually experimented with adjusting the paging values, but no additional pages are returned.
I have also tried adding parameters like includeScheduled=1, but the issue persists.
I’ve verified that this behavior is not related to any team-specific or forfeited games.
Request:
Could you please investigate this issue with the pagination in the API for the FUMBOWL PreSeason 2024 tournament? I need to be able to access the third and subsequent pages of matches to retrieve the complete match data.
Thank you for your assistance. |
|
|
koadah
Joined: Mar 30, 2005
|
| Posted:
Sep 20, 2024 - 16:23 |
|
|
BBCode Wonders
Search
