Weave Code
Socialbuttons Widget Laravel Package
friendsofvictoire/socialbuttons-widget
A Laravel widget package for adding social media share buttons to your application. It provides a reusable component for displaying links to popular social networks, helping visitors share your content. Suitable for Blade templates and widget-based layouts, it is lightweight and easy to integrate in...
At a glance
Frequently asked questions about Socialbuttons Widget
- Is friendsofvictoire/socialbuttons-widget a Laravel package?
- No. Despite being listed as a Laravel/PHP package, it ships as WidgetSocialButtonsBundle, a Symfony bundle built for the Victoire CMS. There is no Illuminate service provider, no composer extra.laravel block, and no Blade views. It has no Laravel-facing entry point and should not be installed in a Laravel application.
- Can I install friendsofvictoire/socialbuttons-widget with Composer in Laravel?
- Composer may resolve the package, but installing it would pull in Symfony components, Victoire widget contracts, and Doctrine-backed widget entities. That dependency graph is far larger than the few dozen lines of share-link markup the bundle actually provides. There is no Laravel integration to make it work, so the install would add risk without delivering usable functionality.
- Does this package support Laravel 8, 9, 10, or 11?
- No. The last release was on 2019-04-04, during the Symfony 2/3 era, and it predates modern Laravel package discovery and Blade component conventions. It does not target any Laravel version, and there is no maintainer activity to suggest future support.
- Which social networks does the SocialButtons widget support?
- The bundle uses Twig/HTML partials to render share links, and given its 2019 vintage it almost certainly includes Google+ (shut down in April 2019) plus legacy Twitter and Facebook share endpoints. The realistic 2025 set such as X/Twitter, Facebook, LinkedIn, WhatsApp, Bluesky, or Mastodon would need to be verified in the template and likely rewritten. Do not assume current network coverage without auditing the source.
- How do I add social share buttons to a Laravel Blade template?
- Build a small Blade component, for example resources/views/components/social-share.blade.php, that renders plain anchor links for each network. Store the network-to-share-URL mapping in a config array or PHP enum so marketing can change targets without a deploy. Use urlencode() on the canonical page URL and add target=_blank with rel=noopener noreferrer nofollow. This avoids third-party JavaScript and the CSP and consent burden that comes with it.
- Is friendsofvictoire/socialbuttons-widget abandoned or maintained?
- It is effectively abandoned. The last release was 2019-04-04, it has 1 star and 0 dependents, and its parent ecosystem, the Victoire CMS, is itself dormant. There is no security response path and no maintainer available to patch a rendered third-party endpoint if it becomes an XSS or tracking vector. Treat it as reference material, not a dependency.
- What is the best alternative to this package for Laravel social share buttons?
- For most Laravel applications the best alternative is an in-house Blade component that renders static share links, which takes an estimated 1-2 days. It gives you full control over which networks you support, how URLs are encoded, and whether any third-party JavaScript is loaded. If you prefer a package, choose one that explicitly supports your Laravel version, has recent releases, and publishes Blade views rather than Symfony bundles.
- Does the SocialButtons widget work with CSP and GDPR consent banners?
- Almost certainly not without changes. A social-buttons widget of this vintage predates modern privacy and CSP expectations: it has no consent gating, no guaranteed rel=noopener noreferrer attributes, and likely uses inline scripts or third-party iframes that conflict with a strict Content-Security-Policy. Static anchor links rendered by your own Blade component are the safer route and sidestep both concerns.
- How hard is it to reimplement this widget's functionality in Laravel?
- The portable value is a single Twig/HTML partial of a few dozen lines, so a reimplementation is small. Encode the share-URL templates in a config array or enum, render them through one Blade component, and you have replaced the bundle. Most teams estimate 1-2 days including design and testing; sharing counts would be a separate project.
- Can I reuse the bundle's Twig template in a Laravel Blade view?
- You can adapt the markup manually by translating the Twig syntax to Blade, but there is no automatic converter and no Laravel package to bridge them. The useful part is the knowledge of which share URL each network expects, not the template itself. Lift that pattern into a Blade component and leave the Symfony bundle and its dependencies behind.
Weaver
How can I help you explore Laravel packages today?