fix: #3610873 Drop the Industry filter and name the exposed filters after the event fields.

Rajab Natshahrequested to merge
issue/varbase_events_base-3610873:issue/varbase_events_base-3610873-events-filters into 1.0.x

The listing was cloned from the Blog/News listing and inherited its Industry exposed filter (field_tags). Industry is a News and Blog concept; events do not have it. The exposed filter is removed. The field_tags field STAYS on the Event content type and the Related events display still keys on it — only the exposed filter goes. The listing now exposes Search by and Type only.

The exposed filter identifiers now follow this recipe's own fields: search (node title) and event_categories (field_event_categories, the Event categories vocabulary), instead of the Blog-inherited type / industry. Labels stay "Search by" and "Type". This changes the query parameters on the listing URL (?search=&event_categories=...).

The Better Exposed Filters settings are aligned with the News listing so the two listings behave the same.

Known, not fixed in this MR: the keyword filter's placeholder (bef.filter.search_title.advanced.placeholder_text: "Search by...") is set in config and reaches the saved view, but the placeholder attribute never reaches the rendered markup, so the field shows a visible "Search by" label and an empty box. Needs a follow-up.

Issue

https://www.drupal.org/project/varbase_events_base/issues/3610873

Related

One change split across three projects, cross-linked:

Verified together on a fresh drush site:install of the Educare site template: 0 errors, the events listing exposes Search by + Type, the grid renders through vartheme_bs5_educare:views-view-grid, and /events, /events/upcoming and /events/past all return HTTP 200. The filter row was checked in a real browser.

AI-Generated: Yes (Used Claude Code to remove the Blog-inherited Industry exposed filter and rename the exposed filter identifiers to match this recipe's own fields.)

Checkpoints

  • File an issue about this project
  • Addition/Change/Update/Fix to this project
  • Testing to ensure no regression
  • Automated unit/functional testing coverage
  • Developer Documentation support on feature change/addition
  • User Guide Documentation support on feature change/addition
  • UX/UI designer responsibilities
  • Accessibility and Readability
  • Reviewed by a human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Update Release Notes
  • Release
Edited by Rajab Natshah

Merge request reports