Wappler Version : 7.4.0
Operating System : Ubuntu 25.04
Server Model: NodeJS/Docker
Database Type: MySQL
Hosting Type: Digital Ocean droplets
Expected behavior
What do you think should happen?
Our application should work as it did in 7.3.9.
Actual behavior
What actually happens?
We were previously filtering via a static input on a page (populated with a Data Binding). This worked fine in 7.3.9 and all previous versions of Wappler. However in today's release this is not so. The value is ignored. We have also noticed that some Server Actions have stopped filtering correctly but are trying to debug this. Although our approach may not be the 'correct' method it has ALWAYS worked fine up until today's update.
How to reproduce
Have a Server Action filtered by a get variable.
Add a text input on the page to bind the variable to.
Add the Server Action to the page.
Select the input as the query parameter for the Action.
Seems the input is being ignored Theodor. We have an Action that fetches media related to a property filtered by a propertyuuid which is present in the page and bound to an input. The Action sees this but on the server side it seems to be ignored.
Despite this being set the Action is returning ALL the records in the table and not those that match this variables value.
Haven’t had the chance to investigate yet because I just now updated to 7.4.0 and as soon as I did, all hell broke loose with my app in development. Not even sure how to describe what all is broken. Need to look into further but wanted to come on here and see if I was the only one. @Cheese may be right about the query filtering.
Wappler Version : 7.4.0
Operating System : Mac Tahoe 26.0.1
Server Model: NodeJS
Database Type: MySQL
Hosting Type: Docker
Right on the server side it seems variables with 'output' checked are not outputting correctly from as far as I can narrow it down to... That is what my primary diagnosis of the server side issues seems to point to as the Actions that are outputting incorrectly all have variables set to output (and these are the ones returning everything rather than filtering by this output values). Will look in to it more though...
This query pulls the admin menu instead of the main menu and I checked and qApp.main_menu_id is returning the correct value and qCurrentPage.page_main_menu_id is indeed null so it should use qApp.main_menu_id which is 2 but it appears to be ignoring this conditional and pulling the first menu record which is the admin menu with an id of 1
Suggestion. Due to this being a significant breaking change would it not be a good idea to reset the banner to the previous Wappler version to avoid Users breaking their applications? And hide the latest version announcement...? For us it is not an issue as we simply revert to a backup but for those that don't have a backup it could be a real issue...
I'd love to but inline updates still do not work in Linux (clicking the update alert does nothing). So guess I'll have to wait unless I can get a copy of the updated files?
