Weave Code
Socialpage Widget Laravel Package
friendsofvictoire/socialpage-widget
Adds a configurable social page widget to Laravel apps, letting you embed and display feeds or page content from social platforms via a simple Blade component and publishable config. Lightweight, framework-friendly, and easy to drop into any layout.
friendsofvictoire/socialpage-widget adds a configurable social page widget to Laravel applications, making it easy to embed social profiles or page content directly in Blade views. It keeps embed markup and settings organized so social content can be reused across layouts without duplicating code.
- Blade-ready widget/component for quick rendering
- Configurable page and display options
- Responsive, embed-friendly output
- Publishable configuration for Laravel projects
- Simple integration with existing views and layouts
Frequently asked questions about Socialpage Widget
- Is friendsofvictoire/socialpage-widget a Laravel package?
- No. Despite being described as a Laravel widget package, friendsofvictoire/socialpage-widget is the FriendsOfVictoire WidgetSocialPageBundle, a Symfony bundle built for Victoire DCMS. It ships no service provider, no Illuminate contracts and no framework-agnostic API, so there is nothing for Laravel to auto-discover or register. Any use in a Laravel application would be a port of the source code, not an integration.
- Can I install it in a Laravel 11 application with Composer?
- Composer resolution will almost certainly fail against a modern Laravel stack. The dependency constraints are of the 2016 vintage, with Symfony ^2.7|^3.0 era glue that conflicts with Laravel 10 or 11 running PHP 8.2+ and Symfony 6/7 components. Forcing installation with --ignore-platform-reqs is a red flag rather than a workaround, because the code would still target classes and APIs that no longer exist.
- Which social networks and API endpoints does the widget call?
- The widget is a presentation-layer plugin: a widget class extending Victoire's BaseWidget and WidgetInterface, a Twig template, and a small configuration form for social account settings. Outbound calls live inside the widget class and date from 2016, so they are near-certainly built on deprecated endpoints such as older Facebook Graph versions or the pre-v2 Twitter API. Audit the class before assuming any of those endpoints still respond.
- Does the widget cache social feed responses, or fetch on every render?
- That is undocumented in the package, and the silence is the problem. There is no documented cache layer and no Laravel cache integration, so the safe assumption is that data is retrieved at render time. Fetching a remote social API during page render adds latency and a failure point to every request, so any port should wrap retrieval in Cache::remember with an explicit TTL.
- Where are OAuth tokens and app secrets stored?
- Credential handling is unknown and undocumented. Tokens and app secrets were most likely stored in Victoire CMS configuration, potentially without encryption, and the package offers no key rotation or environment-based configuration story. Treat any values found in the repository as compromised and issue fresh credentials rather than migrating the old ones.
- Is the package still maintained, and when was the last release?
- The last release was 2016-08-22, roughly nine years ago, and the parent Victoire project is also inactive. The repository has 1 star and 0 dependents, so there is no community validation, no downstream consumers surfacing breakage and no security response path. You would own every future fix yourself.
- What PHP, Symfony and Twig versions does composer.json require?
- Expect constraints of the PHP ^5.5|^7.0 and Symfony ^2.7|^3.0 era, with Twig 2 or 3 assumptions in the templates. Read composer.json directly before planning anything, because those constraints determine whether even a partial install is possible. In practice, assume they are incompatible with PHP 8.2+, Symfony 6/7 and current Laravel releases.
- How do I port the Twig widget template to a Laravel Blade component?
- Read the Twig template and convert it to a Blade component or partial; this is the highest-fidelity, lowest-risk carry-over from the repository. Move the social account settings into a config file or a Nova or Filament field rather than replicating the Victoire configuration form. Leave the widget registry, DI tags and extension hooks behind, since they have no Laravel analogue.
- How should I reimplement the feed retrieval as a Laravel service with caching?
- Build a service class behind a config/socialpage.php entry and never call the social API during page render. Wrap the call in Cache::remember with a TTL that matches how fresh the feed needs to be, and ship the whole thing behind a feature flag so it can be disabled without a deploy. Use a maintained SDK or direct Graph or X API calls instead of porting the 2016 HTTP client, since a from-scratch implementation is often around 200 lines and cheaper than a port.
- What alternatives should I evaluate before porting this package?
- Evaluate maintained options first: official platform embed scripts, a maintained social-feed SDK, or an off-the-shelf feed aggregator. Only port the bundle if the exact visual output is a hard product requirement. Given the package's age, near-zero adoption and inactive upstream, the replace-versus-port decision should be made explicitly before any implementation work starts.
Weaver
How can I help you explore Laravel packages today?