Skip to content

Conversation

@AKSHAT2802
Copy link

@AKSHAT2802 AKSHAT2802 commented Jul 30, 2025

Trac ticket: https://core.trac.wordpress.org/ticket/48088

This PR enhances the get_avatar_data() function by serving a local default avatar (the Mystery Man) when no email or hash is available, thereby avoiding unnecessary external requests to Gravatar.

What This PR Does

  • Adds a short-circuit in get_avatar_data():
  • A local image is served instead of calling Gravatar.
  • Introduces a new image asset:
    wp-includes/images/avatar-default.png

How to Test

  • Call get_avatar() with:
    echo get_avatar( '', 96, 'mm' );
  • The returned URL should point to includes_url( 'images/avatar-default.png' ).
  • The browser should display the local image (mystery avatar).
  • Requests with valid emails will continue to use Gravatar normally.

@AKSHAT2802 AKSHAT2802 marked this pull request as ready for review July 30, 2025 10:26
@github-actions
Copy link

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props akshat2802.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant