Weave Code
Disqus Widget Laravel Package
friendsofvictoire/disqus-widget
Laravel package that adds a Disqus comment widget to your application, with a Blade component and configurable shortname so you can drop threaded comments into any page. Simple setup and minimal overhead.
friendsofvictoire/disqus-widget provides a simple Disqus comments widget for Laravel applications. Configure your Disqus shortname once, then render a comment thread from your Blade views without manually wiring the embed script each time. It keeps Disqus setup centralized and reusable across posts, pages, or other content.
- Blade-based widget for rendering Disqus threads
- Configurable Disqus shortname
- Publishable configuration file
- Lightweight setup for Laravel views
Frequently asked questions about Disqus Widget
- Is friendsofvictoire/disqus-widget a Laravel package?
- No. Despite how it is sometimes described, friendsofvictoire/disqus-widget is a Symfony bundle (FriendsOfVictoire/WidgetDisqusBundle) built as a widget plugin for Victoire CMS on the Symfony 2/3 era. Its architecture assumes a Symfony kernel, Victoire's widget registration system, Doctrine ORM entities for widget configuration, and Twig rendering inside Victoire's page-composition pipeline. None of that maps to Laravel's service container, Blade, Eloquent, or Livewire/Filament widget models, so in a Laravel context it is structurally inapplicable rather than merely a low fit.
- Can I install friendsofvictoire/disqus-widget in a Laravel project with Composer?
- Composer may resolve the package, but nothing will register a service provider, Blade directive, or view component, so you get no working Disqus output. A decade-old bundle will also pull transitive dependencies that are themselves unmaintained, and composer audit will almost certainly flag them. Do not add friendsofvictoire/disqus-widget to composer.json for a Laravel application.
- Does friendsofvictoire/disqus-widget support Laravel 10, 11 or 12?
- No. The last release was 2016-11-08, long before any modern Laravel version, and it carries no Laravel service provider, no Blade views, and no Laravel version constraints. It targets Symfony 2/3 and Victoire CMS, with no PHP 8.x or Symfony 5/6/7 compatibility path. There is no upgrade route that makes it a supported Laravel dependency.
- What is the maintenance status of friendsofvictoire/disqus-widget?
- It has been dormant for roughly nine years since its 2016 release. Ecosystem signals are minimal: about one star, zero dependents, and a composite score around 0.065, so there is effectively no user base, no bug reports, and no third-party fixes to inherit. There is no security patch path, and the underlying Victoire CMS lineage itself has very limited ongoing activity.
- How do I add Disqus comments to a Laravel Blade view instead?
- Build a small first-party component: a config/disqus.php file or settings row holding shortname, enabled, and an environment toggle, plus a Blade component such as x-disqus-thread that emits Disqus's current embed.js with a disqus_config block and the page identifier. Add an admin surface in Filament, Nova, or a settings page for the shortname and per-content-type enablement, and roll it out behind a feature flag defaulting to off. The whole build, including tests, is roughly a day's work and avoids a dead dependency.
- How do I configure the Disqus shortname and thread identifier in Laravel?
- In the original bundle this is Doctrine-backed widget configuration plus options passed through a Twig template, which has no Laravel equivalent. In Laravel, keep the shortname and an enabled flag in config/disqus.php or an Eloquent-backed settings model, and pass the per-page identifier and URL into your Blade component as props. Treat the bundle's configuration schema (shortname, identifier, page URL, theme and language flags) as the only reusable reference material.
- How do I test a Disqus comment widget in a Laravel application?
- Keep the widget behind a config flag that defaults to off, then write feature tests asserting the component renders the expected embed markup, shortname, and thread identifier for a given model. Stub or intercept the third-party script in tests so nothing hits Disqus during CI, and cover the disabled state so no markup leaks onto pages where comments are off. Because the vendor script is external, assert your own contract rather than Disqus behaviour.
- What are the alternatives to friendsofvictoire/disqus-widget for Laravel comments?
- Disqus comments are a commodity feature, so the realistic alternatives are a first-party Eloquent thread and comment model with a Livewire component, a Filament or Nova comment panel, or hosted options such as Giscus, utterances, Isso, or Commento. The build-versus-buy decision hinges on comment volume, moderation workflow, and whether you want third-party cookies on your pages. Coupling the feature to an abandoned CMS bundle is a poor trade in every case.
- Is the Disqus embed code in this bundle outdated?
- Yes. The 2016-era embedding snippet predates the current embed.js contract with disqus_config, so copying it verbatim can produce deprecated behaviour and missing or incorrect thread identifiers on modern sites. Read the template only to understand the markup pattern, then re-implement against Disqus's current documentation in your own Blade component.
- What privacy and security concerns should I review before using Disqus?
- Disqus sets third-party cookies and is a US-based processor, so GDPR, CCPA, and similar reviews need to clear before you ship it, including consent handling. On the package side there has been no security patch path since 2016 and no dependency hygiene, so any inherited code is frozen risk. Decide explicitly who owns the Disqus account, shortname, and moderation policy, and confirm whether the requirement is Disqus specifically or just a comments system.
Weaver
How can I help you explore Laravel packages today?