Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments Block: Default Avatar returning 404 #53279

Closed
jordesign opened this issue Aug 3, 2023 · 6 comments
Closed

Comments Block: Default Avatar returning 404 #53279

jordesign opened this issue Aug 3, 2023 · 6 comments
Labels
[Block] Comments Affects the Comments Block - formerly known as Comments Query Loop [Type] Bug An existing feature does not function as intended

Comments

@jordesign
Copy link
Contributor

Description

When viewing the Comments block (in single post, or page templates) the default avatars are returning broken images. Viewing the console shows that the URL https://secure.gravatar.com/avatar/?d=mm&f=y&r=g&s=80 is returning a 404.

Step-by-step reproduction instructions

  1. Open the Site Editor and view a single or page template which contains a Comments block.

Screenshots, screen recording, code snippet

Screenshot 2023-08-03 at 11 57 30 am

Environment info

Wp 6.3 RC3
No plugins
TT3

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

@jordesign jordesign added [Type] Bug An existing feature does not function as intended [Block] Comments Affects the Comments Block - formerly known as Comments Query Loop labels Aug 3, 2023
@t-hamano
Copy link
Contributor

t-hamano commented Aug 3, 2023

I was able to reproduce the problem in the environment started with wp-env, although the URL is slightly different.

comment

Edit: I was able to reproduce the avatar block by itself.

@t-hamano
Copy link
Contributor

t-hamano commented Aug 3, 2023

The fundamental problem may be that the avatarURL returned by the ueDefaultAvatar() hook is somehow inaccessible.

wp.data.select('core/block-editor').getSettings().__experimentalDiscussionSettings.avatarURL

@t-hamano
Copy link
Contributor

t-hamano commented Aug 3, 2023

I thought the problem might be related to the Gravatar endpoint and not the Gutenberg issue. Therefore, I have submitted a core ticket.

https://core.trac.wordpress.org/ticket/58970

@t-hamano t-hamano removed the [Type] Bug An existing feature does not function as intended label Aug 3, 2023
@kraftbj
Copy link

kraftbj commented Aug 3, 2023

Relayed to the Gravatar team and reported in their internal repo

@jordesign jordesign added the [Type] Bug An existing feature does not function as intended label Aug 3, 2023
@t-hamano
Copy link
Contributor

t-hamano commented Aug 4, 2023

Thank you, @kraftbj!

@t-hamano t-hamano closed this as not planned Won't fix, can't repro, duplicate, stale Aug 4, 2023
@kraftbj
Copy link

kraftbj commented Aug 4, 2023

The fix has been deployed. Some caching may still interfere with some requests until it all flushes out.

Working example: https://secure.gravatar.com/avatar/?s=101&d=mm&f=y&r=g

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Comments Affects the Comments Block - formerly known as Comments Query Loop [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

3 participants