Weave Code
File Widget Laravel Package
friendsofvictoire/file-widget
A file management widget for Laravel that adds upload, browse, and preview controls to your admin panels or dashboards. Drop it into a view, point it at a disk, and manage files without building custom UI.
friendsofvictoire/file-widget is a lightweight PHP package that provides a reusable file widget for attaching, previewing, and managing uploaded files inside your application's forms and admin interfaces. It wraps common file-handling concerns—selection, validation, and display—into a single configurable component, so you can drop consistent file management into any screen without rebuilding it each time.
- Configurable file input for single or multiple uploads
- Inline previews and metadata for attached files
- Validation hooks for type, size, and count limits
- Framework-agnostic API that integrates with existing form builders
- Simple templates for quick styling and layout overrides
Frequently asked questions about File Widget
- Is friendsofvictoire/file-widget a Laravel package?
- No. friendsofvictoire/file-widget is a Symfony bundle (WidgetFileBundle) built for Victoire DCMS, not a Laravel package. It has no Laravel service provider, publishable config, Blade views, or Laravel-facing API surface.
- Can I install friendsofvictoire/file-widget in a Laravel 10 or 11 application?
- Almost certainly not. The bundle is from 2016 and typically pins PHP ^5.5|^7.0 and Symfony ^2.x|^3.x, which conflict with PHP 8.x and Laravel 10/11 dependencies. A composer require will likely fail resolution, and forcing it with --ignore-platform-reqs is not advisable.
- What Laravel versions does friendsofvictoire/file-widget support?
- None officially. There is no Laravel support matrix because the package targets Victoire CMS on Symfony, not Laravel. Treat any Laravel version as unsupported until a throwaway composer require spike proves otherwise.
- What PHP version does friendsofvictoire/file-widget require?
- It targets the PHP 5.5/7.0 era. The 2016 bundle predates PHP 8 and relies on features removed or changed in modern PHP, so runtime fatals are likely even if Composer is forced through. Do not use --ignore-platform-reqs as a workaround.
- What does friendsofvictoire/file-widget do in Victoire CMS?
- It adds upload and file-selection fields to Victoire CMS widget forms. Editors can attach documents and media directly while editing pages in the page builder, without leaving the content editor.
- Do I need Victoire CMS to use friendsofvictoire/file-widget?
- Yes. The widget abstraction is defined by Victoire's WidgetBundle and depends on Symfony's DI container, Twig, Doctrine ORM, and the Victoire admin UI for registration and rendering. Laravel has no corresponding widget subsystem, so the code has no drop-in slot without the host CMS.
- How do I configure friendsofvictoire/file-widget?
- There is no Laravel-style configuration. Registration and rendering happen through Victoire's widget lifecycle and Symfony DI, with no publishable config file or Blade views. Configuration is therefore tied to the Victoire admin UI and host Symfony application.
- What is a Laravel alternative for file uploads and media in an admin panel?
- Use spatie/laravel-medialibrary for attachment-to-model semantics, conversions, and storage abstractions. If the admin is Filament-based, use Filament's FileUpload or SpatieMediaLibraryFileUpload; for a standalone browser, consider laravel-file-manager or a custom Livewire component. These are Laravel-native, maintained, and give modern upload hardening.
- Is friendsofvictoire/file-widget maintained and safe for production?
- No. The last release was 2016-08-22, with roughly eight years of upstream drift and no security patches. It is a leaf package with 1 star and 0 dependents, and 2016-era file-handling code is a security-sensitive surface for MIME sniffing, SVG/XSS, and path traversal. Reject it for production and treat it as a low-value design reference only.
- How do I test friendsofvictoire/file-widget in a Laravel project?
- You cannot meaningfully test it in a Laravel project because there is no Laravel test surface or integration point. The fastest decisive check is a throwaway composer require against your target Laravel/PHP matrix and to capture the resolver output. Real testing would require the Victoire/Symfony stack, which is outside a Laravel application.
Weaver
How can I help you explore Laravel packages today?