Wappler Version : 4.9.0
Operating System : Windows 11
Server Model: NodeJS
Database Type: MySql
Hosting Type: Docker
Expected behavior
When adding a custom variable for a paged query’s offset parameter, that it would use this variable with no problems.
Actual behavior
This is the payload.
This is the response. Notice the limit. Regardless of the payload, it is ALWAYS 25.
I DO HAVE TO STRESS, when using the standard $_GET.offset variable, this works perfectly, even with a custom limit variable. When you change the $_GET.offset variable to, for example, $_GET.logs_offset, the above happens.
How to reproduce
Just create a paged query, then change the variable for the offset parameter. When changing the query params from, say, a select element, nothing will happen. The payload is correct, however the ServerConnect query comes back with a limit of 25, always.
I am having this exact issue currently. This seems to be a bug that still exists.
Additionally, regardless of what you set the offset variable in the paged query properties, the default $_GET.offset still works, seemingly showing that the offset variable is not actually working (despite being set correctly in the json)
So probably something is not properly set on your page, where you change the offset. Maybe provide more details about your setup - both server side and on the page.
May also be worth noting that these queries were insert as a “Database Query” and then converted to paged using the query type dropdown. Maybe that has something to do with it, but I haven’t tested that theory
Ah sorry, I just noticed that as well, but in this case it was just a screenshot error as I had multiple tabs open (I’ve got two paged queries which are both having this issue custom_ and default_), but the issue does actually still occur with the correct parameter as well.