Is there a way to suppress this output? This is spamming the cron logs and also sending mails if you use MAILTO= in the crontab.
Maybe I'm missing something but how does this module even work without this patch? I'm upping this to major. With this patch it's adding the column to "node_field_data" and it's excluding nodes as intended.
sanderjp → made their first commit to this issue’s fork.
The patch does not seem to work for Views pages, but I'm not sure how that can be fixed.
sanderjp → made their first commit to this issue’s fork.
sanderjp → created an issue.
I have seen the issues described here on a number of websites we maintain, where the translations are used correctly after a deploy. Some time later however the English defaults are back again.
The patch of #9 does seem to fix the broken translations after a cache rebuild. We will now test and see if the English defaults are still being reset after a while.
I'm surprised this Major core issue is hardly getting any attention at all.
Looks good, seems to work for me as well.
But should we add the full yarn.lock file of nearly 3k lines?
SanderJP → created an issue.
The reset facets option ("Adds reset facets link") will be shown now as well when a search query is used.
The main difference between hook_field_widget_multivalue_form_alter (D9) and hook_field_widget_complete_form_alter (D10) is in D9 $elements is the widget itself:
In D10 we get the parent container element $field_widget_complete_form containing the widget:
The attached patch is assuming this parent container setup is consistent for all fields but I've only tested this on a node entity type. But this patch allows me to use the Visibility Conditions again.
SanderJP → created an issue.
I would not recommend using this patch. The changes to `web/core/misc/states.js` are breaking form states on textfields and textareas, you cannot make those fields required anymore. Took me way too long to figure that out.
I just ran into a similar issue where the address search is working for anonymous but not for logged in users. Can you test if the attached patch fixes the issue? I've removed setting the form-autocomplete class on the search input. It fixes my issue but I'm not sure yet if this change has any other effects, a quick search seemed it was only used for some styling.