Weave Code
Nova Media Field Laravel Package
optimistdigital/nova-media-field
A Laravel Nova field for attaching and managing media on your resources. Upload images or files, preview selections, and store them with your models, giving editors a simple media picker inside the Nova admin panel.
Simple media field with multiple image support, image browsing and thumbnail generation
Frequently asked questions about Nova Media Field
- What is optimistdigital/nova-media-field and what does it do?
- It is a Laravel Nova field package that adds a media picker to your Nova resources. Editors can upload one or more images or files, browse existing media, preview selections, and attach them to a model. Server-side thumbnail generation is handled with Intervention Image. Architecturally it is a thin extension: a PHP Field subclass, a compiled Vue component, and no domain logic or schema of its own.
- Which Laravel and Nova versions does nova-media-field support?
- The last release was January 2023 and the repository is archived, which places it in the Nova 3/4 and Laravel 8/9 era. On Nova 5 with Laravel 11 or newer, expect Composer constraints to block installation outright. Even if constraints resolve, Nova's front-end toolchain changed enough between majors that a prebuilt field component may load but silently misbehave.
- How do I install optimistdigital/nova-media-field?
- Installation is a standard composer require of optimistdigital/nova-media-field, followed by registering the field class on the relevant Nova resource. You also need a configured filesystem disk and either the GD or Imagick PHP extension for thumbnail generation. The hard part is not the command but constraint resolution against your Nova and Laravel versions.
- Is nova-media-field still maintained?
- No. The repository is archived and the last release was in January 2023, so there will be no compatibility updates, security patches, or upstream fixes. Ownership of maintenance effectively transfers to your team the moment you adopt it. The MIT license and small surface area make forking genuinely practical, but the compiled Vue component is the hardest part to patch.
- How does nova-media-field store multiple images on a model?
- It stores multiple image references against a single model column, almost certainly as a JSON array. There is no separate schema, pivot table, or service layer, so the persistence shape lives entirely in that one attribute. Review the actual column type, JSON structure, and disk configuration in your app before building any UI on top of it.
- Can I use nova-media-field with Nova 5 and Laravel 11?
- Treat that as conditional at best. The package predates Nova 5, and while a prebuilt Vue field may load, the component toolchain changed between majors and can misbehave without throwing obvious errors. Feasibility depends on the host app being frozen at a matching Nova version. Confirm your Nova version and upgrade roadmap before committing.
- Does nova-media-field generate thumbnails, and is that synchronous?
- Yes, it generates thumbnails server-side using Intervention Image, requiring GD or Imagick. The package is small and simple, so thumbnail generation is most likely synchronous on upload rather than queued, though you should verify this in a spike. Also note Intervention Image v2 versus v3 is a breaking API split, so the pinned version can constrain what the rest of your app uses.
- What are the alternatives to optimistdigital/nova-media-field?
- Nova's native File and Image fields support multiple uploads without any third-party dependency. Pairing spatie/laravel-medialibrary with a custom Nova field gives you a maintained, structured media model. Also check whether the vendor, Optimist Digital (now Outl1ne), has shipped a namespaced successor such as outl1ne/nova-media-hub that covers the same use case.
- Should I fork nova-media-field or replace it?
- Replacing it with a maintained equivalent has the highest upfront effort, roughly three to five dev days including data migration, but the lowest total cost of ownership. Forking internally takes about one to two dev days to publish under your own namespace and verify, plus ongoing upkeep, and only makes sense if the UI is well-loved and your Nova version is stable. Adopting as-is is reasonable only for a short-lived internal tool pinned to Nova 3 or 4.
- What risks should I consider before using nova-media-field in production?
- Archival is not a future risk here but a realized one: no patches, no fixes, no compatibility updates. The narrow blast radius helps, but the package adds UI convenience rather than capability. Deleting a model may not cascade to deleting files, and multi-image ordering, cropping, or per-image metadata are not modeled. Wrap the field behind your own subclass so swapping it later stays cheap.
Weaver
How can I help you explore Laravel packages today?