-
-
Notifications
You must be signed in to change notification settings - Fork 827
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
dev/core/issues/726, Fixed fatal error when searched using group type #13603
Conversation
(Standard links)
|
@pradpnayak is this something that we can replicate in a unit test? |
test this please |
@eileenmcnaughton sure, will do! |
I tested & confirmed that I can replicate this & the above fixes - once you get a chance to add a test it's all good IMHO |
@jitendrapurohit how does this tie into the one you just submitted? (@pradpnayak was going to do a test but hasn't gotten to that) |
If I apply this fix with or without my PR applied, I get a DB syntax error on my usecase described at #13727 (comment) as the where clause that will be formed on searching
Notice the 0 added at the end of the condition in all the cases. Maybe, we should limit it more to not execute this line in case of empty or null operators. |
Yes, early return makes sense - we might also try using CRM_Core_DAO::createSQLFilter to generate the string. We obviously don't have much test cover on this fn |
This really does want a test but I'm gonna let it slip through without as
|
The error mentioned above still replicates for us. This time it displayed a fatal error on one of the mailing page - Steps in https://lab.civicrm.org/dev/core/issues/768 can be followed to replicate it easily on search builder. We fixed it by -
@eileenmcnaughton @pradpnayak does it makes sense to avoid this assignment for NULL operators? |
@jitendrapurohit are we ignoring the op later on? |
Overview
https://lab.civicrm.org/dev/core/issues/726
Before
After
Comments
Error occurs when there is no group of Mailing list or Access list.