[ZBXNEXT-4989] offset parameter for API calls - New Ticket !! Created: 2019 Jan 30 Updated: 2019 Feb 01 Resolved: 2019 Feb 01 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | API (A) |
| Affects Version/s: | 4.0.2, 4.0.3, 4.0.4rc2 |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Major |
| Reporter: | RENAN SAVIDAN | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Standard - Only API requests to server (not possible to modify the code on the server) |
||
| Issue Links: |
|
||||||||
| Description |
|
Hi, I know this issue/topic has already been discussed a little bit. I am working for a client and I can only request from "my" server to his ZABBIX server ; no modification possible on the client's ZABBIX server. I need an offset parameter in the API request (used with limit) so I can code a pagination on the WordPress website I am developing. Too many results in my tables on the page, I need to paginate. The previous ticket says something about a patch, I can't patch the code on the ZABBIX server as I already said. Which solution do I have ? On my opinion it is useless and idiot to request the full results from my page because then I have to add a complexity layer in my WordPress website's code to handle all these results - I save datas nowhere, I only display them (they are not even cached ; this is mandatory). I hope you understand my issue - the project is expected to be published soon and I want to avoid extra-complexity if possible especially because it seems it is quite an ordinary need. I hope you can provide tips or answers guys. Thank you in advance, Best regards.
|
| Comments |
| Comment by Alexander Vladishev [ 2019 Jan 31 ] |
|
Closed as duplicate of ZBXNEXT-2132. You can vote for this feature! |
| Comment by RENAN SAVIDAN [ 2019 Feb 01 ] |
|
Hi, This issue was closed because it is a duplicate. I understand and I knew it is a duplicate. But it doesn't help me at the moment. I get it, this feature is really not available but if the issue remains open maybe some people around can give me an advice or a workaround ? It is not only about a "missing feature" it is really about something I have to solve and the issue closed I won't get any useful reply I guess. Maybe I am wrong about how works this forum but I hoped I could get tips for my problem more than "duplicate and closed issue". Thank you. |
| Comment by dimir [ 2019 Feb 01 ] |
|
RENAN SAVIDAN, this is not the way it works here (and on any other issue tracker, I believe). We have only one ticket per request. Why? Because this way a request will get more votes and potentially will be implemented sooner. Besides, all the information being in single place is easier. Do you agree? People know, if they found a duplicate there is definitely a link to the issue it duplicates and they will go and add vote/comment there. I hope you understand the idea. |
| Comment by RENAN SAVIDAN [ 2019 Feb 01 ] |
|
OK OK I won't insist It's just I don't know where else I could ask my question - I still have no workaround... Thank you, Regards. |