Have logged an issue for this here and have also provided a fix for this issue. Can you please apply patch from here and test if it solves your problem? Also please try to comment on PR if the patch works for you. This will fasten process of merging PR into core so that it can be available in next release.
Yes this happened since 5.8. I have submitted a PR for this issue. You can either apply patch or wait for 5.18 release.
Note: Since this change involves update to settings file, you will
need to clear civicrm cache after applying patch.
Nice find. Thanks for posting. Yes the inner join is generally better than a subquery.
To answer your secondary question, to get it merged you need to create a ticket at https://lab.civicrm.org/dev/core/-/issues/new and then if you're able to also make an associated pull request at https://github.com/civicrm/civicrm-core against master. See also https://docs....
You must report it to the extension author. The CiviCRM core team doesn't have any control over third parties who write extensions.
To find the author's preferred place to report a bug:
Go to Administer menu » System Settings » Extensions.
It might be in Administer menu » Customize Data and Screens » Manage Extensions if you upgraded from an older ...
I'm happy to report that the original issue was resolved with an update to 5.5.1. With this update made, the errors illustrated in my original post are no longer occurring.
Because we've long used CiviCRM without this error and first noticed it with 4.7.31 (and consistently with subsequent upgrades), we believe that this new upgrade has returned the ...
Yes it appears to be a bug. You should file one.
Here seems to be the conditions:
Importing update or fill, i.e. contact already exists
Has no existing email address or any existing has is_primary flag = 0
Has a street address or are also importing one
There seems to be no way via import to fix these or to import them correct. Well, if you are also ...
I have the similar problem with the "thank you" page for donations. It started to displayed the same message instead of "thank you" page. We noticed, that URL is not correct: problem is caused by "&" string in URL. When it is replaced with just &, it works fine and "thank you" page is displayed correctly.