After 7.4 update: database single query Bug

Wappler Version : 7.4.0
Operating System : kubuntu
Server Model: nodejs
Database Type: sqllite
Hosting Type: wappler

Expected behavior

When i do a database single query with a condition the condition does work in the preview AND should work in the live app too.

Actual behavior

I am just doin Brians video tutorial, and upgraded from 7.3.9 to 7.4.0. after that only the seo data from the first called site is going into the database. this is because the database single query which sould check if the page is already in, ignores the condition. i did various tests on this behaviour. even it works in the preview sql window, the query ALWAYS returns the first line in the table during runtime because the condition is ignored, which leads to no insert because it thinks that it is already there.

i found out, that the behaviour goes back to normal if i set the lib/core/app.js back to the 7.3.9 version. → there are some sql changes in there, they are clearly broken.

How to reproduce

i think that my explanation and the bug itself is easy to reproduce. i can do a video or share the whole project, if needed, but basically you should have enough information and the fix should be easy either way.

Have you installed the latest inline extension update?

hi Teodor, thx for the fast reply. thats clearly the issue.

but i am sorry, this brings me to the next issue: nothing happens if i click on this button. is there a trick how to start this update? maybe its a linux issue…

[edit]: more info: the popup you show in de screenshot does open too. but if i click/spam the button, nothing happens. a hidden or misplaced popup seems not to be the case. → the use “cheese” had the same update issue within his linux wappler. but looks like he solved it somehow.

[edit2]: i looked the first bugs page to see if my report is a duplicate, but i can’t find your linked thread “7.4.0 breaks database query filtering” in the list. why is it hidden? (its interesting, if you use the forum search with exactly the thread name, it is not findable too.)