Delete Current Avatar sets avatar to gravatar icon #203

Closed
opened 2025-11-02 03:13:45 -06:00 by GiteaMirror · 8 comments
Owner

Originally created by @strk on GitHub (Jan 5, 2017).

I've no idea why but hitting "Delete Current Avatar" button in an organization
page turns the avatar into a Gravatar logo. Hitting "Update Avatar Setting"
after that gives a new random avatar (which doesn't happen again upon hitting
"Update Avatar Setting" again).


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally created by @strk on GitHub (Jan 5, 2017). - Gitea version (or commit ref): 79d527195d98d74867a067ce93a4dace2b86d2bb (1.1.0-dev) - Can you reproduce the bug at https://try.gitea.io: Yes I've no idea why but hitting "Delete Current Avatar" button in an organization page turns the avatar into a Gravatar logo. Hitting "Update Avatar Setting" after that gives a new random avatar (which doesn't happen again upon hitting "Update Avatar Setting" again). <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40667221-delete-current-avatar-sets-avatar-to-gravatar-icon?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>
GiteaMirror added the topic/uiissue/staletype/bug labels 2025-11-02 03:13:45 -06:00
Author
Owner

@bkcsoft commented on GitHub (Jan 6, 2017):

AFAIK Organizations shouldn't even hit Gravatar 😕

@bkcsoft commented on GitHub (Jan 6, 2017): AFAIK Organizations shouldn't even hit Gravatar 😕
Author
Owner

@glothriel commented on GitHub (Jan 9, 2017):

Well. The same function is invoked when user deletes avatar. Organizations in gitea/gogs are in fact User instances.

@glothriel commented on GitHub (Jan 9, 2017): Well. The same function is invoked when user deletes avatar. Organizations in gitea/gogs are in fact User instances.
Author
Owner

@lunny commented on GitHub (Feb 24, 2017):

move this to v1.2 since no PR to fix this.

@lunny commented on GitHub (Feb 24, 2017): move this to v1.2 since no PR to fix this.
Author
Owner

@elvarb commented on GitHub (Dec 4, 2017):

Also means that if you import users from ldap when gravatar is enabled and then disable gravatar the default user avatar will become the avatar generator instead of whatever default avatar you have.

@elvarb commented on GitHub (Dec 4, 2017): Also means that if you import users from ldap when gravatar is enabled and then disable gravatar the default user avatar will become the avatar generator instead of whatever default avatar you have.
Author
Owner

@elvarb commented on GitHub (Dec 4, 2017):

Deleting the ldap user and resyncing just means you get the random avatar again instead of the default avatar.

@elvarb commented on GitHub (Dec 4, 2017): Deleting the ldap user and resyncing just means you get the random avatar again instead of the default avatar.
Author
Owner

@elvarb commented on GitHub (Dec 4, 2017):

There is no way to have the default avatar show up for all users, its either default gravatar logo or the random avatar generator. Few options I see

  • Setting to disable random avatar generator, fall back to default avatar png
  • Setting to use any avatar generator, for example http://avatars.adorable.io/
@elvarb commented on GitHub (Dec 4, 2017): There is no way to have the default avatar show up for all users, its either default gravatar logo or the random avatar generator. Few options I see * Setting to disable random avatar generator, fall back to default avatar png * Setting to use any avatar generator, for example http://avatars.adorable.io/
Author
Owner

@stale[bot] commented on GitHub (Feb 10, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 10, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (Feb 24, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 24, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#203