Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Button Widget

Button Widget Laravel Package

friendsofvictoire/button-widget

Provides a configurable button widget for the Victoire CMS page builder. Editors insert call-to-action buttons and set labels, links, styles, and target options through a visual form, so no template edits or custom markup are required.

View on GitHub
Deep Wiki
Context7

At a glance

Frequently asked questions about Button Widget
Is friendsofvictoire/button-widget a Laravel package?
No. It ships as FriendsOfVictoire\WidgetButtonBundle, a Symfony bundle for the Victoire CMS page builder. It has no Laravel service provider, facade, package type, or config publish stub. Dropping it into a Laravel app would be a port rather than an integration.
Can I install friendsofvictoire/button-widget in a Laravel application?
Composer will likely fail to resolve dependencies because Victoire-era packages constrain Symfony 2.x or 3.x and PHP 5.x or 7.x, while current Laravel versions require Symfony 6 or 7 components and PHP 8.2 or newer. Even if resolution succeeded, there is no Laravel wiring for the widget. The practical recommendation is to reimplement the concept natively.
What Laravel versions does friendsofvictoire/button-widget support?
None officially. The package is a Symfony/Victoire bundle, not a Laravel package, and it does not target Laravel 8, 9, 10, 11, or any other Laravel release. Its dependency tree is tied to the Victoire CMS ecosystem.
What does the friendsofvictoire/button-widget actually do?
It provides a configurable call-to-action button widget inside the Victoire CMS page builder. Editors set a label, link destination, style, and target through a visual form, and the widget renders markup through a Twig template. It is not a standalone runtime library or reusable UI component.
How do I build a configurable button component in Laravel?
Create a Blade component such as x-button plus a small content-block field type in your admin panel. Back it with an Eloquent model or a JSON column on an existing blocks table, validate input with a FormRequest, and render with Blade. That maps the Victoire concept to native Laravel primitives without importing Symfony or Doctrine dependencies.
Does friendsofvictoire/button-widget have tests or security monitoring?
There is no known test suite, and the package shows no adoption, dependent projects, or release cadence. With no upstream activity it will not appear in CVE advisory feeds, so any vulnerability is yours to find. A button widget that accepts URLs and link targets also warrants review for XSS and open-redirect exposure.
Is friendsofvictoire/button-widget safe for production use?
It is not recommended for a Laravel production stack because of abandonment risk, dependency deadlock, and untrusted-input rendering concerns. The license posture should also be confirmed before lifting any source. A native Laravel implementation gives you maintained code, tests, and security ownership.
What are alternatives to friendsofvictoire/button-widget for Laravel?
The best alternative is a small Blade component plus a block field in whichever admin panel you already use, such as Filament, Nova, or Statamic. The reusable artifact is the data contract for a button block, not the Victoire code. Reimplementing that contract is faster and safer than porting a Symfony bundle.
How is the button widget configured in Victoire?
It is configured through Victoire's widget registry, a Symfony Form type, a Doctrine entity, and a Twig template. Editors set fields such as label, link, style, and target in the CMS admin form. There is no Laravel config file or publishable configuration stub.
What license does friendsofvictoire/button-widget use?
The provided context does not state a license, and being public on GitHub is not a license grant. Confirm the FriendsOfVictoire organization's terms before copying any source. Reimplementing the button concept from scratch avoids license uncertainty entirely.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
novasa/laravel-language-center
opencage/geocode
adolfoholzer/parameters
livenetworks/ln-starter
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core