- How do I install awcodes/filament-gravatar in a Laravel app?
- Install it with Composer using composer require awcodes/filament-gravatar, then follow the repository's registration steps for your Filament version. In most setups you add the Gravatar column directly to a Filament table schema. Confirm the exact namespace and column class in the README before wiring it into production.
- Which Laravel and Filament versions does awcodes/filament-gravatar support?
- Support is defined by the package's composer.json constraints, so check those before upgrading Laravel or Filament. Because it integrates with Filament's table builder, match the package version to your panel's Filament major version. Pin a compatible release in composer.json and verify it in CI.
- How do I add a Gravatar column to a Filament table?
- Add the package's Gravatar column to your table schema and point it at the record attribute that contains the email address. Filament then renders the avatar for each row based on that email. No upload field or storage configuration is required.
- Can I change the Gravatar size or use a fallback image?
- Yes. The column is designed to let you configure the avatar size and a fallback or default image. Use the column's fluent methods in your table definition to set those options. Check the README for the exact method names for your installed version.
- Does awcodes/filament-gravatar work with any Eloquent model?
- It works with any Eloquent model that exposes an email attribute or an attribute you can point the column at. That makes it suitable for users, customers, team members, or other records with an email field. The model does not need a custom interface or trait.
- Do I need to store or upload avatar images for this plugin?
- No. The plugin resolves avatars from Gravatar using the record's email, so there is no upload handling, file storage, or image resizing in your application. Your app only renders the remote Gravatar URL. Keep that network dependency in mind when planning offline or air-gapped environments.
- Is there a config file I can publish for awcodes/filament-gravatar?
- The package is designed as a lightweight column, so most configuration happens on the column instance rather than in a published config file. If your installed version provides publishable configuration, the README will list the vendor:publish command. Verify the config surface for your exact release before relying on global defaults.
- How do I test a Gravatar column in Filament?
- Write a Filament table test that asserts the column renders for a model with an email address. Because Gravatar images are remote, avoid asserting on the actual image response in unit tests; assert the generated URL or column configuration instead. Run your PHP and Filament version matrix in CI to catch compatibility issues.
- What happens if a user has no Gravatar or the email is missing?
- Gravatar usually returns a default image when no matching avatar exists, and the column can be configured with a fallback image. If the email attribute is null or empty, the generated Gravatar URL will not identify a real avatar. Handle missing emails in your model or hide the column conditionally if that matters for your UI.
- Is awcodes/filament-gravatar production-ready, and what are the alternatives?
- It is a small convenience dependency rather than infrastructure, so pin exact versions and review the release notes before adopting it. The v4.2.1 release fixed a PHP 8.4-only mb_trim issue from v4.2.0, so verify your PHP matrix in CI. Alternatives include Filament's built-in avatar or initials column, or a standalone Gravatar package such as creativeorange/gravatar if you need Gravatar outside tables.