I had the same issue. After applying the patch in #16 the exposed filter completely disappeared and is no longer available.
I couldn't get the patch in #2 or #7 to apply - but haven't had time to dig into it.
Using viewsreference_filter 1.0.5 and core 10.2
Using Drupal 10.2. Also had problems with a date field in the node and had smart_date module installed. #15 fixed the issue.
Thanks!
I can confirm that following the instructions in #18 did get the moderation filter working for me with content.
It's still not working with media.
Related note - does not work with Group content or Group media views
I tested replacing group_content_field_data with group_relationship_field_data and drupal.group_content__group_role with group_relationship__group_role in GroupStatistics.php and it worked.
I'll see if I can create a patch a post it here.
I'm getting the same error with Group 4.x and YASM 4.0.5
Anyone have success getting this to work on the 4.x version? The 3.x versions don't appear to work.
laura.gates → credited jdearie → .
I wanted to come back and post the answer to my question - in case others were trying to do the same.
I need to store the full hierarchy of the term select with cshs widget. None of the options in the Item format options in the Submission Display field worked.
After much much research, I discovered {{ item.breadcrumb }}
That token stores the full path. I also updated the Custom Settings / Custom properties. By default, the save_lineage is set to false, so I set it to true. I'm not actually sure I needed to do that last part or not, but I did.
- Click the Advanced tab on the element you wish to edit
- Expand the SUBMISSION DISPLAY fieldset.
- Select Custom... from the Item format field in the SINGLE ITEM fieldset.
- Type
{{ item.breadcrumb }}in the Item format custom HTML field - Scroll down to CUSTOM SETTINGS and set the save lineage to true:
save_lineage: true
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
Changing the text color of webform-progress-tracker .progress-step .progress-text to #5c5c5c might be all that's needed.
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
laura.gates → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
JoiGarrett → credited jdearie → .
seantwalsh → credited jdearie → .
laura.gates → credited jdearie → .
I've installed the patch from #58 and can see the configure visibility option on my block - but when I attempt to add a condition, after htting the Add condition button, I just get the indicator of something happening, but then nothing does.
It doesn't seem to matter which condition I choose.
I'm using layout builder to configure the /user page.
I tried this on another content type that uses layout builder and had the same result.
I am on core 8.7.8 - do I need to be on 8.8?