Opened 5 years ago
Closed 5 years ago
#8151 closed defect (bug) (fixed)
Avatar endpoints are loaded even they have been disabled from the WP Admin options screen
Reported by: | imath | Owned by: | imath |
---|---|---|---|
Milestone: | 5.1.0 | Priority: | normal |
Severity: | normal | Version: | 5.0.0 |
Component: | REST API | Keywords: | has-patch commit |
Cc: |
Description
We should check for these settings before loading the Group and xProfile Avatar Attachment controllers.
Moreover, the User Avatar Endpoint should be attached to the xProfile component instead of the members component.
Attachments (3)
Change History (14)
#3
@
5 years ago
- Owner set to imath
- Resolution set to fixed
- Status changed from new to closed
In 12483:
#4
@
5 years ago
- Keywords has-patch removed
- Resolution fixed deleted
- Status changed from closed to reopened
It looks like it's best to revert these commits. For further details see this discussion on slack.
#7
@
5 years ago
- Keywords has-patch commit added
- Resolution fixed deleted
- Status changed from closed to reopened
As discussed during October 30 dev-chat: until the Member Avatar dependency to xProfile is removed in BuddyPress Core, we will make sure to load the Member Avatar Controller only if the xProfile component is active.
8151.3.patch is moving the Member Avatar controller into the xProfile component.
Documentation about this fact has been updated, see Member Avatar chapter.
8151.2.patch is updating Unit Tests to take the fact Avatars are now loaded by the xProfile component and add tests to check the Member avatar controller is not loaded when avatar uploads are disabled.