- How do I install ferdiunal/laravel-nova-media-field in Laravel Nova?
- Install it with Composer, then register the field class on the Nova resource where you want media management. You will also need Laravel Nova and Spatie Media Library configured in the app, including disk and collection settings. Check the package README for the exact namespace and field options before rolling it out.
- Which Laravel, PHP, Nova, and Spatie Media Library versions does this package support?
- The package is a bridge between Nova and Spatie Media Library, so compatibility depends on all four layers: Laravel, PHP, Nova, and Spatie. The README and Composer constraints are the source of truth, not the last release date alone. Pin versions and run a branch-level proof of concept against your actual application stack.
- Does laravel-nova-media-field support Nova 5?
- A September 2024 release does not by itself prove Nova 5 support. Verify the Composer constraints and test asset publishing and field rendering on a Nova 5 branch before adopting it. If it fails, keep a native Nova file field or a small custom field as fallback.
- Can I use this Nova media field with a custom Spatie Media model?
- The field is built around Spatie Media Library, but undocumented assumptions about the Media model are a known risk. If you use a custom Media model, test associations, collection names, and conversions in a pilot resource. Inspect the package source and confirm it respects your model configuration before replacing existing upload fields.
- Does it support multiple media collections on one Nova resource?
- Multiple collections and existing media are edge cases that should be validated rather than assumed. Pilot the field on one resource with your real collection setup, including ordering and pre-existing media. If the field does not cover your multi-collection workflow, use Spatie directly or a custom Nova field.
- How are file validation and authorization handled in laravel-nova-media-field?
- File validation and authorization should be enforced through your Laravel and Nova policies, not left to the field alone. Test upload rules, policy checks, and any multi-tenancy boundaries in a non-production resource. The package is an admin UI convenience, so keep critical validation in application code.
- Can laravel-nova-media-field upload to S3 or a CDN disk?
- Uploads are handled through Spatie Media Library, so S3 and CDN support depends on your Spatie disk configuration. Configure the disk, visibility, and URL generation in the Laravel app, then verify previews and downloads in Nova. Test large uploads and temporary URL behavior before using it in production.
- Does it support conversions, responsive images, and media ordering?
- Conversions and responsive images are Spatie Media Library features, and the Nova field only needs to preview and manage the resulting media. Confirm that your conversions are queue-backed and that the field displays the correct URLs. Ordering and existing media behavior should be tested on a pilot resource.
- Is ferdiunal/laravel-nova-media-field actively maintained and tested?
- The package is community OSS with thin adoption signals, roughly 12 stars at assessment time, and no vendor SLA. The last release was September 2024, which is recent but not proof of current Nova or Laravel support. Treat maintainer responsiveness and test coverage as risks to validate, and budget for an internal fork or patch.
- What are alternatives or fallback options if this Nova media field breaks after an upgrade?
- If the field breaks after a Nova upgrade, fall back to a native Nova file field or a small custom field backed directly by Spatie Media Library. You can also use Spatie directly in your resource forms without a Nova adapter. Keep the fallback in place until the package proves stable in your stack.