Problem/Motivation
After the release of views 3.16 this module generates a lot of warnings, due to the $join->extra being set with a string instead of an array.
Proposed resolution
Simply refactor the code generating the warning by building the extra clause as an array.
Remaining tasks
Review (this being my first patch ever :-))
User interface changes
The user interface is not affected.
API changes
No API changes.
Data model changes
No data model changes.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | select_translation-warnings_with_views-2876095-6-D7.patch | 500 bytes | ao2 |
| #2 | select_translation-warnings_with_views-2876095-0-D7.patch | 726 bytes | nironan |
Comments
Comment #2
nironan commentedComment #3
nironan commentedComment #4
ao2 commentednironan, the patch seems OK, and after a quick research it seems that it's also compatible with Views 2.x.
I cannot test it because I don't use Drupal 7, so it'd be nice to have a RTBC by someone else, but I don't consider this a blocker.
BTW, can you paste the exact warnings that you get without the patch? And what change in Views 7.x-3.16 triggers it?
It's good to have these details in the long commit message and/or in the release notes.
Thanks,
Antonio
Comment #5
ao2 commentedPing.
Comment #6
ao2 commentedThe warning seems to occur in views after commit 36eef6e which makes the code rely more strongly on the assumption that the $extra parameter is an array, as actually documented in the API.
The previous code was more forgiving that it needed to be.
And in the related issue I see that the error message is
Can you confirm the analysis?
The minimal fix in select_translation would be something like in the attached patch.
Can you please try it in place of your previous one?
Thanks,
Antonio
Comment #7
ao2 commentedPing.
@nironan were you able to test the minimal patch from #6?
Thanks,
Antonio
Comment #8
kmontyI can confirm this was a bug caused by the change made to resolve #1930288: views_join: wrong handling of $extra parameter. Not only was it throwing PHP notices as the OP mentioned, this bug was causing significant performance impacts on a major client site. Patch number #6 resolved both the notices and negative performance impacts.
I will mark as RTBC, but understand if you want additional eyes on this before committing. Thank you ao2 for the quick fix!
Comment #9
ao2 commentedOK @kmonty thanks for the test.
I am going to apply the patch in #6 then and release a new stable 7.x version on Monday. if @nironan too finds some time to test it before then I'd appreciate that, but I don't consider this a blocker.
Thanks,
Antonio
Comment #10
nironan commented@ao2, sorry for the late reply. I just managed to test your patch and it works! Thank you
Comment #12
ao2 commentedOK, fix pushed.
I'll release a new stable version today.