- Issue created by @portulaca
- Assigned to PrabuEla
- Issue was unassigned.
- Status changed to Needs review
about 2 years ago 9:47am 30 January 2023 - Assigned to PrabuEla
By and large we havenโt been promoting workarounds like this but are more interested in the root cause.
- Issue was unassigned.
The last submitted patch, 6: 3337146-6.patch, failed testing. View results โ
The last submitted patch, 8: 3319083-6.patch, failed testing. View results โ
The last submitted patch, 10: 3337146-7.patch, failed testing. View results โ
- Status changed to Needs work
about 2 years ago 1:46pm 30 January 2023 - ๐ฎ๐ณIndia ameymudras
Thanks @PrabuEla for the patch, I think the method validateArgument shouldn't be called with empty arguments in the first place. We need to find the root cause of the issue rather than just handling the error.
- Status changed to Postponed: needs info
about 2 years ago 1:47pm 30 January 2023 I am marking this as postponed because we need precise bug reproduction instructions.
- ๐ญ๐ทCroatia portulaca
I was able to get the message to appear again, although it's not consistent when it appears, it's very elusive. Sometimes it's after Views have been saved, sometimes after visiting the Views Page, sometimes after adding new Block to the page and visiting it.
I imported the same Views to a clean install and I can't reproduce it there. I Installed Simplenews because I have it on the page where the message appears and because it seems to be relying on Taxonomy (or it used to?) and I notice I don't have the same Newsletter configuration on the clean install. It may be an upgrade bug, I need more time to test and rule out Simplenews.
- ๐ญ๐ทCroatia portulaca
I found the cause, it was another views that was active on the same page and it didn't appear, I had forgotten about it.
Steps to reproduce
To reproduce getting the log message you can use Standard Drupal installation (Tags Vocabulary).
Here is the export of the Views in question, and the log message on D10 (original message is for D9):
https://gitlab.com/-/snippets/2491413
After you import the Views place the Block "
Terms
" into a region of your theme, visit a page where the Block is supposed to be visible and it will trigger the log message.Views still output correct results (on the test site as well as on the site where the whole setup makes sense), the only downside AFAICT with this particular setup is the log message.
Other conditions:
"Specify validation criteria" under "When the filter value IS available or a default is provided" must be turned ON to trigger the message.
If it's left to "Basic validation" the Page where the Block is shown is WSOD.
If Validator gets set to "Taxonomy term name" it's still showing WSOD on the page with the Block:
> Drupal\Core\Database\InvalidQueryException: Query condition 'taxonomy_term_field_data.name IN ()' cannot be empty. in Drupal\Core\Database\Query\Condition->condition() (line 106 of /var/www/html/viewstest/web/core/lib/Drupal/Core/Database/Query/Condition.php).
If I turn on "Transform dashes in URL to spaces in term name filter values" the page with the Block appears and it triggers the reported message.
"Transform spaces to dashes in URL" under "More" doesn't seem to affect getting the log message.
Let me know if you need any more info.
- ๐ฎ๐นItaly trickfun
I have same error with Drupal 10.1.6 and PHP 8.2
Patch doesn't work.
Thank - ๐ฆ๐บAustralia pameeela
Moved steps to issue summary. Confirmed the deprecation warning appears with the provided view config, but didn't look into it.
- Status changed to Active
6 months ago 10:22pm 15 September 2024 - ๐ฆ๐บAustralia pameeela
Could still probably use an IS update to make it a bit more concise. It would also be preferable to explain the views config rather than just providing a same yml file.
- First commit to issue fork.
- ๐บ๐ธUnited States mcoughli
I may be missing something but I was confused by the fact that the latest patch appears to confirm an argument passed IS null, rather than ensuring the opposite...
Also even if that was the correct check, there's nothing to stop a null value from being used in the taxonomy storage load, which also will generate an error.
I've submitted a merge request with a change that I believe ensures the argument value is NOT null before proceeding with everything else. Hopefully this helps. (And if so I may argue for backporting...) - ๐บ๐ธUnited States smustgrave
Issue summary still appears to need some attention.