Avatar Privacy

I activated the plugin and don’t see any change!?

Did you remember to visit the discussion settings page, activate ‘Show Avatars’? You have to enable avatars for this plugin to be able to do anything.

I saved the settings and still don’t see any changes. How do I know the plugin works?

Depending on which options you selected, you might not see a change in the way the page looks. The changes are visible in the source code though:

• Look at the gravatar image URL of a user without a gravatar. The plugin works if the URL looks like [your site]/wp-content/uploads/avatar-privacy/cache/gravatars/[x]/[y]/[long SHA256 token]-68.png instead of https://secure.gravatar.com/avatar/[other long MD5 token]?s=68&d=http%3A%2F%2F1.gravatar.com%2Favatar%2F[long MD5 token]%3Fs%3D68&r=PG. There aren’t two URLs in there anymore, only one, and the default URL looks the same for two comments without a gravatar.
• You should see the checkbox on the comment form. You need to log out though to see it. If you are logged in, you should see a similar checkbox in your user profile in the WordPress backend.

I still don’t see the checkbox in the comment form!? Everything else works.

Then you probably don’t use a modern theme which makes use of the function comment_form() to create the comment form. Check if you can find this function used in comments.php or a similar file of your theme. If you do and it still doesn’t work, tell me. Otherwise chances are that you do have to add the checkbox manually. Use this function:

<?php if ( \function_exists( 'Avatar_Privacy\gravatar_checkbox' ) ) { \Avatar_Privacy\gravatar_checkbox(); } ?>

What happens if I disable the plugin? Are any of the data altered?

The plugin saves additional data about whether commenters and users want to display a gravatar or not (if you select that mode in the settings). These data are deleted when you properly uninstall the plugin.

Apart from that, the plugin only filters data, but does not permanently change them. Especially, if you deactivate the plugin und have gravatars turned on, they will again show up for everybody, even those commenters and users who opted out of displaying gravatars. You do have to change the default gravatar back manually, though.

Can this plugin be used together with cache plugins?

Yes, it certainly can. You have to be careful though which plugin options you select and how you cache your content. The first plugin option checks if a gravatar exists for a given e-mail address and, if not, displays the default image directly. If you cache the output of this check, the gravatar will not be displayed if the user later decides to sign up with Gravatar.com. If you’re using this option, you should invalidate cached pages with gravatars on them (mostly the single view of entries) regularly.

Can this plugin be used on a multisite installation?

Yes, the plugin can be used on a multisite installation. You can either activate it on individual blogs or do a network activation. As users are global to a multisite installation, their choice regarding Gravatar.com use will affect all sites in the network. So if a user comments on blog A and chooses to display gravatars, this decision will be followed on blog B and C too. On new installations, comment author (i.e. non-user) opt-in is recorded per site, not per network. If you first installed Avatar Privacy 0.4 or earlier, the global table wp_avatar_privacy continues to be used for all sites in the multisite network. This behavior can be overriden by the network admin via the filter hook avatar_privacy_enable_global_table.

Won’t spam comments flood the database table with useless entries for the checkbox in the comment form?

The plugin doesn’t save the value of the “use gravatar” checkbox for comments by registered users (see below), trackbacks/pingbacks (there is no e-mail address) and comments that are marked as spam when they are saved. If you mark a comment as spam later, the table entry is not removed, since the same e-mail address might also be used by non-spam comments. If a comment is marked as spam by Akismet or similar plugins and you later manually mark it as non-spam, what the user selected when submitting the comment will already be lost. This only happens with spam comments, not comments who just need to be moderated, e.g. because of the ‘needs at least one published comment’ rule.

Will the avatar caching make my disk space run out?

While storing the cached avatar images on your own server will take some extra disk space, the plugin makes sure that it does not grow out of bounds by deleting cached gravatars every other day and all other images once a week. When the cached file is accessed again, it is automatically regenerated.

If you don’t have to worry about the amount of disk space consumed, you can extend the maximum age of cached files via the filter hooks avatar_privacy_gravatars_max_age and avatar_privacy_all_images_max_age. The cron job intervals can also be adjusted via hooks (avatar_privacy_gravatars_cleanup_interval and avatar_privacy_all_images_cleanup_interval, respectively).

Can commenters override a registered user’s choice whether to display a gravatar by creating fake comments?

No, for registered users the user profile is checked, not the table for the commenter’s choices. Commenters can not override this value, not even the user themselves if they post a comment when not signed-in.

Which plugins are known to work with Avatar Privacy?

These plugins have been tested successfully in conjunction with Avatar Privacy:

• AntiSpam Bee
• bbPress
• BuddyPress
• Comments – wpDiscuz
• EWWW Image Optimizer
• Simple Author Box
• Simple Local Avatars
• Simple User Avatar
• Theme My Login
• Ultimate Member
• Webmention
• WP User Manager – User Profile Builder & Membership

Please note that several Jetpack by WordPress.com modules do not work well with Avatar Privacy because they generate their HTML markup on the WordPress.com servers.

If you find any problems with particular plugins, please tell me!

What happens if I remove the plugin?

There is a difference between deactivating the plugin and uninstalling it. The plugin gets deactivated if you do so on the plugins page or if you simply delete the plugin files via FTP. No uninstallation tasks are performed then, so you can activate and deactivate the plugin as you want without losing the plugin’s settings.

If you deactivate the plugin und have gravatars turned on, they will again show up for everybody, even those commenters and users who opted out of displaying gravatars. If you changed the default avatar to one of the new local avatar images, the gravatars will not be displayed until you change the default avatar image back.

OK, but I really want to get rid of everything. How do I that?

If you want to completely uninstall the plugin and get rid of any data in the database, you should properly uninstall it: Deactivate the plugin first via the WordPress plugins page and then click ‘delete’ (same page, next to the plugin). For multisite installations, this has to be done by the network administrator on the network plugins page.

The plugin saves additional data about whether commenters and users want to display a gravatar or not (if you select that mode in the settings). The following data are stored by the plugin and deleted upon uninstallation:

• custom table(s) [prefix]_avatar_privacy (global or per blog on new multisite installations)
• usermeta values per user: use_gravatar, avatar_privacy_hash, avatar_privacy_user_avatar
• option per blog: avatar_privacy_settings
• option per network (sitemeta) on multisite installations: avatar_privacy_salt
• transient per commenter: avapr_check_[mail hash]

The default avatar image is set to the mystery man if you selected one of the new local default avatar images.

Hide FAQ

2.7.0 (2023-05-01)

• Feature: Avatar Privacy is now compatible with PHP 8.2.
• Feature: The plugin now honors the wp_delete_file filter when deleting files.
• Change: Requires at least PHP 7.4.
• Change: Upgrades identifier column of avatar_privacy_hashes table to 256 characters on supported MySQL/MariaDB versions (as it was in 2.4.0).
• Change: The library yzalis/identicon has been removed as a dependency.
• Change: Avatar Privacy now honors the wp_delete_file filter hook.
• Bugfix: Icons from Webmentions using Gravatar will get cached now.
• Bugfix: Uploading avatars for users with no role on the primary site of a Multsite network now works as expected.

2.6.0 (2022-04-18)

• Feature: The size of uploaded images is now checked to make sure processing does not overload the server. By default, all uploaded images have to be smaller than 2000×2000 pixels. The constraints can be adjusted with these new filter hooks:
  • avatar_privacy_upload_min_width
  • avatar_privacy_upload_min_height
  • avatar_privacy_upload_max_width
  • avatar_privacy_upload_max_height
• Feature: Improved caching to reduce the number of database queries.
• Change: Requires at least WordPress 5.6 and PHP 7.2.
• Change: Support for Internet Explorer (all extant versions, i.e. 9, 10, and 11) has been dropped.
• Change: A fabulous new plugin icon designed by Johanna Amann.

2.5.2 (2021-04-30)

• Bugfix: When a user is deleted, their local avatar image is removed as well.
• Bugfix: The dependency version for JS and CSS files is properly calculated. (This also fixes the apparently empty PHP warning when WP_DEBUG is enabled.)

2.5.1 (2021-03-13)

• Bugfix: Fixes PHP 8.0 deprecation warning in the level-2/dice package.

2.5.0 (2021-03-11)

• Feature: Avatar Privacy is now compatible with PHP 8.0.
• Feature: Integration for the following plugins had been added:
  • Simple Local Avatars
  • Simple User Avatar
• Change: The library scripturadesign/color has been removed as a dependency.
• Change: Additional hardening.

2.4.6 (2021-02-21)

• Bugfix: Unchecking the Gravatar opt-in and anonymous commenting checkboxes in a user’s profile screen works again.

2.4.5 (2021-02-07)

• Bugfix: Gravatar opt-ins by anonymous commenters are now properly saved on WordPress 5.5 and later.

2.4.4 (2021-02-03)

• Bugfix: Gracefully handle changes to WordPress’ default DB collation (no more Illegal mix of collations errors).

2.4.3 (2021-01-15)

• Bugfix: Don’t break stuff (another build process fix, for real this time).

2.4.2 (2021-01-15)

• Bugfix: An unfortunate oversight in the build process led to crashes instead of the intended graceful failure when the installation requirements were not met.

2.4.1 (2021-01-10)

• Bugfix: Don’t break the site when the options value in the DB has become corrupted.
• Bugfix: Workaround for maximum database key length when using MySQL < 5.7.7 or MariaDB < 10.2.2.

2.4.0 (2021-01-10)

• Feature: Legacy (default) avatars are now properly cached and resized.
• Feature: There are now API methods to get and set a user’s (local) avatar (and their Gravatar and anonymous commenting policies).
• Feature: New WP-CLI commands relating to local avatars added.
• Feature: Integration for the Simple Author Box plugin has been added.
• Change: Requires at least WordPress 5.2 and PHP 7.0.
• Change: The yzalis/identicon package has been updated to version 2.0.
• Change: Some unused files have been removed from the vendor-scoped directory.
• Change: A new per-site database table for fast hash lookup has been introduced (base name avatar_privacy_hashes).
• Change: General code clean-up and removal of PHP 5.6 workarounds.
• Bugfix: Gravatars will be properly regenerated for comment authors that have not set a policy (when the site-admin has switched the default to “opt-out”).
• Bugfix: When a user requests deletion of their personal data, this now includes the uploaded avatar image files.
• Bugfix: A timestamp is added to uploaded avatar images for better browser caching in the Profile screen.

2.3.4 (2020-03-22)

• Bugfix: Allow plain URLs as default avatars. Use the filter hook avatar_privacy_allow_remote_default_icon_url to allow third-party domains and avatar_privacy_validate_default_icon_url if you want to implement your own image URL validation.
• Bugfix: Properly handle trackback/linkback avatars. This includes a workaround for avatars provided by the Webmention plugin. You can use avatar_privacy_allow_remote_avatar_url to prohibit third-party domains (the default is to allow them for webmentions) and avatar_privacy_validate_avatar_url if you want to implement your own image URL validation.
• Change: Due to the trackback/linkback bug fix, the priority for pre_get_avatar_data filter can now be adjusted using the avatar_privacy_pre_get_avatar_data_filter_priority hook instead of being hardcoded.

2.3.3 (2019-12-27)

• Bugfix: Timestamps in WP-CLI commands now always use GMT.

2.3.2 (2019-11-09)

• Bugfix: Some error messages were not getting translated because of a WP.org infrastructure change.

2.3.1 (2019-09-29)

• Bugfix: Will not crash on WordPress 4.9 anymore when the Gutenberg plugin is not activated.
• Bugfix: The label for the block settings panel of the Avatar block was incorrect.

2.3.0 (2019-09-28)

• Feature: New shortcode [avatar-privacy-form] (optional parameter: avatar-size) to allow changing Avatar Privacy’s user settings on the frontend of the site.
• Feature: Two blocks have been added to the Block Editor to allow displaying a user’s avatar and to change the settings related Avatar Privacy on the frontend.
• Feature: Three new generated default avatars:
  • Bird Avatars,
  • Cat Avatars (both designed by David Revoy), and
  • RoboHash (designed by Zikri Kader).
• Feature: Integration for the following plugins had been added:
  • BuddyPress
  • Theme My Login
  • Ultimate Member
• Feature: New template function \Avatar_Privacy\gravatar_checkbox() for legacy themes added.
• Feature: There is a CLI interface to some parts of Avatar Privacy:
  • wp avatar-privacy db show: Show information about the custom database table(s).
  • wp avatar-privacy db list: List entries in the custom database table(s).
  • wp avatar-privacy db create: Create the custom database table.
  • wp avatar-privacy db upgrade: Upgrade the structure of the custom database table.
  • wp avatar-privacy uninstall: Remove data added by Avatar Privacy.
  • wp avatar-privacy cron list: List active cron jobs created by the plugin.
  • wp avatar-privacy cron delete: Delete cron jobs created by the plugin.
• Change: avapr_get_avatar_checkbox() has been deprecated in favor of \Avatar_Privacy\get_gravatar_checkbox().
• Change: The ID and name of the use_gravatar comment form checkbox has been changed to avatar-privacy-use-gravatar. Please update custom CSS rules accordingly.
• Change: Additional inline styling is added to the avatar-privacy-use-gravatar comment form checkbox to work around common theme limitations. Styling can be disabled using the avatar_privacy_comment_checkbox_disable_inline_style filter hook.
• Change: All external PHP dependencies have been moved to the namespace Avatar_Privacy\Vendor to reduce the chance of conflicts with other plugins.
• Bugfix: Gravatars are only cached if they are actually images to prevent issues with temporary Varnish errors on Gravatar.com.

2.2.2 (2019-06-23)

• Bugfix: Re-allow installation on 4.9.x for increased compatibility with possible future WordPress Core changes. The 2.2.x branch of Avatar Privacy is the last that will support WordPress < 5.2.

2.2.1 (2019-06-08)

• Bugfix: Compatibility with Windows servers.

2.2.0 (2019-05-12)

• Feature: Integration for the following plugins had been added:
  • wpDiscuz
  • WP User Manager

2.1.0 (2019-04-14)

• Feature: Improved compatibility with multisite installations. Plugin data will be properly deleted on uninstallation or when a site is removed. (“Large Networks” will still have to take manual action to prevent timeouts.)
• Feature: Network settings for enabling/disabling global table use on multisite. Existing global data will be migrated to the site-specific tables when global table use is disabled (but not in the other direction).
• Change: usermeta keys are now prefixed (avatar_privacy_use_gravatar instead of use_gravatar).
• Change: Generally improved code quality through unit tests.
• Bugfix: New multisite installations were incorrectly detected as “legacy”, making them use the global table (instead of per-site tables). Affected installations can be switched via the new network settings page.

2.0.5 (2019-02-23)

• Bugfix: Fixed a previously undiscovered compatibility issue with recent versions of EWWW Image Optimizer.

2.0.4 (2019-02-22)

• Bugfix: Updated included libraries for improved compatibility with other plugins.

2.0.3 (2018-11-30)

• Bugfix: Prevent warnings when trying to retrieve the avatar for an invalid user ID.

2.0.2 (2018-09-09)

• Bugfix: Updated included libraries for improved compatibility with other plugins.

2.0.1 (2018-08-16)

• Bugfix: The plugin no longer fails with a fatal error on PHP 5.6 (accidentally introduced in 2.0.0).

2.0.0 (2018-08-11)

• Feature: Administrators can now upload site-specific default avatar images.
• Feature: The default policy previously only accessible via the avatar_privacy_gravatar_use_default hook can now be set from the Discussion settings page.
• Feature: New filter hooks avatar_privacy_gravatar_link_rel and avatar_privacy_gravatar_link_target to filter the rel and target attributes of all links to Gravatar.com.
• Bugfix: The REST API returned incorrect avatar URLs for registered users (workaround for trac ticket #40030).
• Bugfix: The gravatar use cookie is only set when the comment author has given consent.
• Change: Internal restructuring to make maintenance easier.

1.1.1 (2018-06-11)

• Bugfix: Changing the default gravatar policy via avatar_privacy_gravatar_use_default works again for registered users.

1.1.0 (2018-06-10)

• Feature: Supports the new privacy tools on WordPress >= 4.9.6 (export and deletion of personal data, suggested privacy notice text).
• Feature: Registered users can opt into allowing logged-out comments with the same mail address to user their profile pictures.
• Feature: The plugin is now compatible with bbPress.
• Feature: The position of the use_gravatar checkbox can be adjusted via the new filter hook avatar_privacy_use_gravatar_position.
• Change: Trashed comments and comments marked as spam do not trigger a validation request to Gravatar.com if the admin has set the default gravatar use policy to “enabled” via the filter hook avatar_privacy_gravatar_use_default.

1.0.7 (2018-06-06)

• Bugfix: The use_gravatar is actually checked when the cookie has been set.
• Bugfix: A (harmless) PHP warning has been fixed.

1.0.6 (2018-05-29)

• Bugfix: Only valid response codes from Gravatar.com are cached (200 and 404).
• Bugfix: Plugin transients are cleared on plugin upgrades.
• Bugfix: The workaround for trac ticket #42663 introduced in 1.0.5 is expanded to all uses of wp_get_image_editor().

1.0.5 (2018-05-22)

• Bugfix: Prefer GD-based implementations of WP_Image_Editor to work around trac ticket #42663.
• Bugfix: The rel and target attributes are allowed in use_gravatar checkbox labels and by the default, the noopener and nofollow values for the rel attribute are added to the Gravatar.com link.
• Bugfix: Invalid 0-byte image files are not saved anymore.

1.0.4 (2018-05-20)

• Bugfix: When the plugin is uninstalled, the default avatar image is really reset to mystery if necessary.
• Bugfix: The use_gravatar checkbox is compatible with more themes now.

1.0.3 (2018-05-17)

• Bugfix: The plugin no longer fails with a fatal error on PHP 5.6.

1.0.2 (2018-05-16)

• Bugfix: PNG avatars were not created correctly when EWWW Image Optimizer was enabled.

1.0.1 (2018-05-14)

• Bugfix: Non-multisite installations triggered an SQL error in some situations.

1.0 (2018-05-13)

• Feature: All default avatars are generated on your server.
• Feature: Gravatar.com avatars are cached locally. (The cache is cleaned regularly via a cron job to prevent unlimited growth.)
• Feature: Registered users can upload their own avatar images to your server.
• Change: Refactored according to modern development principles.
• Change: Removed settings in favor of sensible default values and filter hooks:
  • Gravatar.com usage is opt-in and gravatars are only displayed if the exist.
  • The default behavior for legacy comments can be customized via the avatar_privacy_gravatar_use_default filter hook.
• Change: All static default icons are now SVG images.