Closes #744

There were several bugs that needed to be addressed before the filtering logic would work correctly.

1. Fixed an operator precedence bug in `pre_get_posts` in `functions.php`: This bug likely wasn't apparent before seeding the test data with over 100 entries. A missing set of parentheses in functions.php caused a side effect where posts_per_page got forced to -1 on any REST API request that included a taxonomy filter (directory_category or directory_tag), which caused WordPress to calculate a negative max page count and reject even page=1 with a rest_post_invalid_page_number 400 error. The fix was wrapping the three `||` conditions in parentheses so the guards apply correctly. https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/fdf6879b1b54fa2b0ad1b9a9fbb78d08c9954bb3

2. Added support for displaying the directory categories on each Directory Feed entry, with a toggle to show/hide it. I felt this was necessary to the logic of using directory_category as a filter in the Directory Feed block. If the user is filtering by category, they need to see the categories for each entry to confirm that the filter is working. https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/0b79720da4c48e2fc9c1f69ad977d67e816728c0

3. Fixed a bug where case sensitivity was calling some filters to silent fail (e.g. the user typed "teaching" instead of "Teaching". The issue was a strict equality comparison on line 191. Added `toLowerCase()` on both sides of the comparison. https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/730dc2252386de986763a23b0905416c64a0dfc0

4. Added a "Filter Logic" dropdown to the Directory Feed block, giving editors control over how category and tag filters combine when both are active, with three options: 
https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/f4f2d0fb8e5f496549c042fde0408be2db7ed994
     * Any tag AND any category (default)
     * All tags AND all categories 
     * Any tag OR any category

5. Fixed a bug that was causing editor preview and published front end to mismatch. `handleOrderBy` was setting `orderByParam` to an empty string when the user reset sorting to the default, rather than explicitly setting `&orderby=date&order=desc`, causing the REST API to fall back to its own implicit default. https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/f75473454453ac3ad41ba137b640fed7c579902a

6. Fixed editor/front-end sort mismatches as well as a bug with how `offset` was being applied. `Offset` was being applied before sorting and filters, which caused it not to work as expected. https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/f75473454453ac3ad41ba137b640fed7c579902a https://github.com/UA-Stratcom/ua-theme_v3/pull/759/commits/890f812afff908d1b239daa995b80c52ecfed781

## How to Test
1. Add a **Directory Feed** block in the editor.
2. In the **Filters** panel, type a tag or category name with the wrong casing (e.g. `"teaching"` when the term is `"Teaching"`).
3. Confirm the list updates to show the correct filtered results in the editor and the front end.
4. Confirm category labels appear on each person by default, and that you can toggle them on and off.
5. In the **Filters** inspector panel, confirm the dropdown has three options and that each produces the correct results. Use posts where you know the exact category/tag assignments.
7. Confirm the "Sort By", "Posts Per Page", "Offset", and "Max Pages" settings still work as intended before and after filtering with categories and tags.

Test with:
- Only a category selected (no tag)
- Only a tag selected (no category)
- Both a category and a tag selected
- Both multiple categories and multiple tags selected

<img width="1719" height="1033" alt="Screenshot 2026-05-04 at 2 47 27 PM" src="https://github.com/user-attachments/assets/a13a9f00-d459-4513-b851-c07aae32a7a0" />


Note: No need to go through all of the copilot review spam in this PR. It was going back and forth about how expensive it was to fetch all the directory entries before sorting and offsetting, verses how it would be inaccurate if you sorted and capped before fetching, but I think it's at a good place now.

enhancement

Add combiner logic for directory feed filters

Closes #744

1. Fixed an operator precedence bug in `pre_get_posts` in `functions.php`: This bug likely wasn't apparent before seeding the test data with over 100 entries. A missing set of parentheses in functions.php caused a side effect where posts_per_page got forced to -1 on any REST API request that included a taxonomy filter (directory_category or directory_tag), which caused WordPress to calculate a negative max page count and reject even page=1 with a rest_post_invalid_page_number 400 error. The fix was wrapping the three || conditions in parentheses so the guards apply correctly. https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/fdf6879b1b54fa2b0ad1b9a9fbb78d08c9954bb3

2. Added support for displaying the directory categories on each Directory Feed entry, with a toggle to show/hide it. I felt this was necessary to the logic of using directory_category as a filter in the Directory Feed block. If the user is filtering by category, they need to see the categories for each entry to confirm that the filter is working. https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/0b79720da4c48e2fc9c1f69ad977d67e816728c0

3. Fixed a bug where case sensitivity was calling some filters to silent fail (e.g. the user typed "teaching" instead of "Teaching". The issue was a strict equality comparison on line 191. Added `toLowerCase()` on both sides of the comparison. https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/730dc2252386de986763a23b0905416c64a0dfc0

4. Added a "Filter Logic" dropdown to the Directory Feed block, giving editors control over how category and tag filters combine when both are active, with three options: 
https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/f4f2d0fb8e5f496549c042fde0408be2db7ed994
     * Any tag AND any category (default)
     * All tags AND all categories 
     * Any tag OR any category

5. Fixed a bug that was causing editor preview and published front end to mismatch. `handleOrderBy` was setting `orderByParam` to an empty string when the user reset sorting to the default, rather than explicitly setting `&orderby=date&order=desc`, causing the REST API to fall back to its own implicit default. https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/f75473454453ac3ad41ba137b640fed7c579902a

6. Fixed editor/front-end sort mismatches https://github.com/UA-Stratcom/ua-theme_v3/pull/758/commits/f75473454453ac3ad41ba137b640fed7c579902a

## How to Test
1. Add a **Directory Feed** block in the editor.
2. In the **Filters** panel, type a tag or category name with the wrong casing (e.g. `"teaching"` when the term is `"Teaching"`).
3. Confirm the list updates to show the correct filtered results in the editor and the front end.
4. Confirm category labels appear on each person by default, and that you can toggle them on and off.
5. In the **Filters** inspector panel, confirm the dropdown has three options and that each produces the correct results. Use posts where you know the exact category/tag assignments.
7. Confirm the "Sort By", "Posts Per Page", "Offset", and "Max Pages" settings still work as intended before and after filtering with categories and tags.

Test with:
- Only a category selected (no tag)
- Only a tag selected (no category)
- Both a category and a tag selected
- Both multiple categories and multiple tags selected

<img width="1719" height="1033" alt="Screenshot 2026-05-04 at 2 47 27 PM" src="https://github.com/user-attachments/assets/a13a9f00-d459-4513-b851-c07aae32a7a0" />

## Description

There are 2 issues with page metadata on the directory template pages:

1. The title for the directory index says "Directory Archive" when it should simply be "Directory", and the pages for a tag or category say "TAG Archives"
2. The thumbnail for rich link embeds will pull from (I think the first) image on the page, which is usually someone's portrait. The image should be omitted or set to a safe default.

There may be other issues with the metadata, so we should review all fields with a tool like https://metatags.io/

## Workarounds

There are no workarounds for this issue, other than making a child theme to override the meta tags


invalid

Theme 3.7.3

Review metadata for directory page templates

## Description

If merged, this PR will fix issue of Directory Feed taxonomies filter

## How to test
1. Dashboard -> Directory -> Directory Categories / Directory Tags  -> Add categories with long name
2. Dashboard -> Directory -> Add Person -> add few records and assign new categories
3. Page -> Add Directory Feed -> and filter categories -> preview page
4. Directory Page -> on the left sidebar -> check the categories and tags page records should be sorted by last name

Following Issues will be closed
#682 
#675 
#679

Directory Feed taxonomies filter issue fixed

## Description

If merged, this PR will fix the error coming in the editor for Directory Feed

Directory feed error on the backend - Tags fetch limit

## Background

Heading text wraps by individual letter on certain screen sizes rather than some form of intelligent wrapping.
Visible within this section on afford.ua.edu:

![textwrapping](https://github.com/UA-Stratcom/ua-theme_v3/assets/110553212/53e894da-0535-422b-becc-68843914efce)


## Description

A plugin to determine best-case hyphenation and wrapping, or enabling the \&shy; character or \<wbr> element within the WordPress code editor for manual insertion 

## Workarounds

No current workaround available/known

## Additional information

Related issue: https://github.com/UA-Stratcom/minerva/issues/179


blocked

Heading text in the columns block wraps by individual letter

Many times an accessibility audit will flag the text on a cover block as insufficient contrast. I initially wanted to write it off as a known false positive but after giving it some thought, it might be nice to add a default background on a layer behind the image.

This would get rid of the false positives, but more importantly it would address an edge case where the text may genuinely have insufficient contrast if the image fails to load for whatever reason.

The default background should use the background CSS variable so that contrast requirements are guaranteed.

An issue related to an accessibility concern

Known Issues

Fixed on dev

Open Issues