- Issue created by @webdrips
- Status changed to Postponed: needs info
over 1 year ago 7:54am 7 February 2023 - 🇳🇱Netherlands Lendude Amsterdam
@webdrips thanks for reporting this.
If I just follow your steps to reproduce on a clean Drupal install I don't see this issue.
The steps seem a bit minimal, since the block isn't actually placed with them. Looking at the stack trace it seems to be placed using Layout builder, is that relevant or do you get this error when you place it anywhere?
Also the stack trace doesn't appear to touch the Combined field filter at all, so is that needed to trigger this or can you trigger this with other exposed filters too? - 🇳🇱Netherlands Yuri
I have the exact same error.
In my case I don't use the combined fields filter.
But, I did use an exposed filter in a views block display, which triggered the error, regardless whether ajax was turned on or not.
Using Drupal distribution Open Social 11.7.1 which uses Drupal 9.4.11 - 🇺🇸United States webdrips
Hi @Lendude ahh yes sorry about that.
This is a bit more complex as we're using the exposed filter as a "normal" block, and the view block was placed using the Layout Builder as you suggested. We use a patch for layout builder to provide visibility rules. We're essentially taking the approach of trying to use Drupal's core modules as much as possible for maintainability.
In this case, we added the block with the layout builder, and used a taxonomy term value to control visibility.
The patch that allows that is here: https://www.drupal.org/project/drupal/issues/2916876 ✨ Add visibility control conditions to blocks within Layout Builder Needs work
We have 27 core patches for this project, so there may be others involved in pulling this off.
If I remove the combined filter block, the error disappears. If I put it back, I need to click search (with or without a value in the search field doesn't matter).
I'm happy to show you the issue over Zoom if it helps at all.
- Status changed to Active
7 months ago 10:21pm 16 November 2023 - Assigned to samit.310@gmail.com
- Status changed to Needs work
4 months ago 8:11am 11 March 2024 - Merge request !69893338057: Deprecated function: preg_match() → (Open) created by samit.310@gmail.com
- Issue was unassigned.
- Status changed to Needs review
4 months ago 10:02am 11 March 2024 - Status changed to Needs work
4 months ago 1:28pm 11 March 2024 - 🇺🇸United States smustgrave
#2 it was mentioned that this wasn't reproducible.
But if this is a bug research needs to be done to find why that parameter is empty vs just putting a check in.
- 🇺🇸United States maskedjellybean Portland, OR
The patch from the MR works for me in 10.1.8 to resolve this error thrown by a view. The view then functions as it should. Not sure what to make of that.