- Is ladela/personal-translations-widget-bundle a Laravel package?
- No. The package self-identifies as a Bundle and follows Symfony bundle conventions, not Laravel package conventions. It has no Laravel service provider, config publishing, facade, or Blade-neutral UI layer described. Treat it as Symfony-only unless you can prove otherwise.
- Can I use this translations widget in a Laravel admin panel?
- Not without significant bridging work. You would need to bring Symfony dependency injection, event conventions, and a Twig-era widget into a Laravel container, which likely costs more than building a small native translation editor. There is no evidence of Laravel-compatible packaging. For a Laravel app, reimplementing the widget is the safer path.
- What does this package actually do?
- It adds a ready-to-use Symfony widget for editing personal translations in an admin interface. It is built around Gedmo personal translations and is meant to manage localized content alongside your entities. It is not a full Laravel translation system or a standalone translation manager.
- What are the installation requirements for this bundle?
- You must resolve the package as a Symfony bundle and also install its parent personal-translations dependency. There is no Laravel service provider or config publish step to rely on. Before installing, inspect composer.json for PHP, Symfony, and Twig constraints and confirm they resolve in an isolated app.
- Does it require the Gedmo personal translations bundle?
- The description indicates it depends on a sibling personal-translations bundle built on Gedmo personal translations. That parent package is not vendored or described in the provided context, so treat it as a required dependency to validate first. Confirm the exact package name and version constraints before any integration work.
- Which Symfony and PHP versions are supported?
- The provided context does not publish clear version constraints, and this is a Symfony bundle rather than a Laravel package. You need to inspect its composer.json and the parent bundle for PHP, Symfony framework, and Twig requirements. At this adoption level, expect legacy Symfony 2.x or 3.x-era constraints and verify resolution on a current PHP runtime.
- Is this package actively maintained and safe for production?
- The signals are weak: 2 stars, 0 dependents, a composite score of 0.07, and a single-maintainer profile. There is no evidence of a security audit, CVE visibility, or maintainer bandwidth to respond to disclosures. Abandonment, dependency, and behavioral risks are high. It is not recommended for production without a deep review and a fallback plan.
- How does it compare to Laravel translation management alternatives?
- It is not a Laravel alternative because it lacks Laravel packaging and Blade integration. For Laravel, use native lang files, spatie/laravel-translation-loader, or a small custom admin screen. The widget's functional scope is small enough that a native Laravel reimplementation is likely faster than bridging Symfony conventions.
- Can I test or evaluate it without adopting it?
- Yes, but do it in an isolated throwaway Symfony app or branch. First confirm whether your host is Laravel or Symfony, then run a dependency-resolution spike with the parent personal-translations bundle. Timebox a prototype and do not integrate it into a Laravel application just to evaluate the widget.
- What should I do if my app is Laravel and I need editable translations?
- Do not force-fit this Symfony bundle into Laravel. Reimplement the small translation editing surface natively with Blade and a translations table, or use a package such as spatie/laravel-translation-loader. That approach avoids the abandonment, framework-mismatch, and transitive dependency risks. It is likely only a few days of work.