Making WordPress.org

Opened 3 weeks ago

Closed 3 weeks ago

#8269 closed defect (bug) (fixed)

Activity Not Displayed for "In Loving Memory" User Profiles

Reported by: klydexa's profile klydexa Owned by:
Milestone: Priority: normal
Component: Profiles Keywords: needs-patch
Cc:

Description

## Issue Summary

Activities are not being displayed on user profiles when the profile status is marked as *"In Loving Memory"*.

## Problem Description

Users with profiles configured as *"In Loving Memory"* are unable to view activity feeds or related activity data on the frontend/profile page. The activity section either appears empty or is completely hidden.

## Expected Behavior

Activity feeds and associated user activities should continue to display normally for profiles marked as *"In Loving Memory"*, unless intentionally restricted by business logic.

## Current Behavior

When a user profile is set to *"In Loving Memory"*:

  • Activity feed does not render
  • Related activities are missing from the profile page
  • No fallback or empty state message is shown

## Steps to Reproduce

  1. Open a user profile
  2. Set the profile status to *"In Loving Memory"*
  3. Visit the frontend profile page
  4. Navigate to the Activity section
  5. Observe that no activities are displayed

## Possible Root Cause

  • Conditional logic may be excluding profiles with the "In Loving Memory" status from activity queries/rendering
  • Activity API response may be filtered incorrectly
  • Frontend component visibility condition may not support memorialized profiles

## Impact

  • Users cannot view historical activity for memorialized profiles
  • Inconsistent user experience across profile types
  • Potential regression affecting profile visibility logic

## Suggested Investigation

  • Verify backend activity query conditions
  • Check profile status filters in API responses
  • Review frontend conditional rendering for activity modules
  • Confirm whether memorial profiles should support activities per product requirements

Change History (1)

#1 @yani.iliev
3 weeks ago

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in revision 24758

Note: See TracTickets for help on using tickets.