Skip to content

EXLM-5361: exclude stale Upcoming from Browse filters and tabbed cards - #2818

Open
nitin-rachabathuni wants to merge 4 commits into
mainfrom
EXLM-5361-browse-aq
Open

EXLM-5361: exclude stale Upcoming from Browse filters and tabbed cards#2818
nitin-rachabathuni wants to merge 4 commits into
mainfrom
EXLM-5361-browse-aq

Conversation

@nitin-rachabathuni

@nitin-rachabathuni nitin-rachabathuni commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

Jira ID: EXLM-5361

Test URLs:

AI Review Notes

Wire the same el_event_start_time >= now rule used by Events Hub and global search into Browse base aq and Coveo card pipeline requests that target Upcoming Event V2.
Browse URL hash aq was overwriting headlessBaseSolutionQuery, so stale Upcoming still returned. AND the shared exclude rule on every Headless search request.
Keep Community|User guard when Headless aq is blank, and always apply stale Upcoming exclude on Coveo card pipeline requests (not only Upcoming V2 contentType).
Avoid substituting only the generic Community base on empty aq — honor the page-configured Browse/Events Headless base query first.
@aem-code-sync

aem-code-sync Bot commented Jul 30, 2026

Copy link
Copy Markdown

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

  • Re-run all PSI checks
  • Re-run failed PSI checks
  • Re-sync branch
Commits

@aem-code-sync

aem-code-sync Bot commented Jul 30, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant