-
Notifications
You must be signed in to change notification settings - Fork 461
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
convert tedious sql strings to safer orm operations #6779
Conversation
4f2e9fa
to
932c39a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on my dev machine (VM) and it seems to work fine. Would appreciate some additional confirmation before pulling the trigger :)
Edit: noticed the CI testing is failing on these two tests:
1) Admin People
Family Property List:
AssertionError: Timed out retrying after 60000ms: expected 'http://localhost/PropertyEditor.php?PropertyID=0&Type=f' to include 'PropertyList.php'
at Context.eval (webpack://churchcrm/./cypress/e2e/ui/admin/admin.people.spec.js:39:17)
2) Admin People
Person Property List:
AssertionError: Timed out retrying after 60000ms: expected 'http://localhost/PropertyEditor.php?PropertyID=0&Type=p' to include 'PropertyList.php'
at Context.eval (webpack://churchcrm/./cypress/e2e/ui/admin/admin.people.spec.js:52:17)
Not sure if this is a test failure (and we need to update the CI script) or code failure and we're introducing a new failure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See previous comment re CI failures.
@MrClever Thanks for doing the once-over! this change is deprioritized until 5.4.1 is out. I just pushed this up so folks are aware and we avoid potentially duplicated efforts. |
54efd52
to
0df939c
Compare
Description & Issue number it closes
working on making the application safer by going through the ORM (which uses prepared statements) rather than manually crafting sql which could become insecure