- Is kphoen/sms-sender-bundle a Laravel package?
- No. It is a Symfony2 bundle that registers through AppKernel and uses Symfony DependencyInjection extensions, not a Laravel service provider. Laravel has no bundle concept, so the package cannot be installed or used as a normal Laravel package.
- Can I use kphoen/sms-sender-bundle in a Laravel application?
- Not directly. Making it work would require vendoring the code, stripping the Symfony DI extension, and re-registering services manually, which is effectively a port. The reusable part is the underlying kphoen/sms-sender sender abstraction, but that library is also old and is not a Laravel integration.
- Does kphoen/sms-sender-bundle support Laravel 10 or PHP 8?
- No. The package has been dormant since 2014-10-21, has no PHP 7 or PHP 8 support, and will not resolve on modern PHP 8.1+ or Laravel 10+ without ignoring platform requirements and forking. There is no maintained path for current Laravel versions.
- How do I install kphoen/sms-sender-bundle?
- Historically you would add it to a Symfony2 composer.json, register the bundle in AppKernel, and configure provider credentials in the bundle config. On a modern stack Composer will likely fail because of PHP and dependency constraints. For a Laravel app there is no supported installation procedure.
- What SMS providers does kphoen/sms-sender-bundle support?
- It is provider-agnostic through the SMS Sender library transports, so support depends on the concrete sender adapters shipped with that 2014-era library. It does not bundle modern Twilio, Vonage, or MessageBird SDK integrations. Any provider integration today should be treated as legacy and likely needs rewriting.
- Is kphoen/sms-sender-bundle maintained?
- No. The maintainer marked it deprecated, it has had no release since 2014, and there are effectively zero dependents. Security issues and compatibility fixes should not be expected. Treat it as a historical reference rather than a dependency.
- What are good Laravel alternatives for sending SMS?
- Use a maintained provider SDK such as Twilio, Vonage, or MessageBird, or a Laravel notification channel that wraps one of those SDKs. Define your own small SmsSender contract in the app and bind one adapter per provider. That gives you swappability without inheriting a deprecated Symfony bundle.
- Does kphoen/sms-sender-bundle handle retries, queuing, or delivery receipts?
- No, not in any production-ready way. It is a thin 2014 wrapper around a sender interface and does not provide retry policies, idempotency keys, typed rate-limit exceptions, webhook handling, or DLR processing. Those concerns must be implemented in your application or delegated to a modern provider SDK.
- Can I reuse the kphoen/sms-sender library without the Symfony bundle?
- You can read the library for its sender abstraction and message API shape, but it is not a practical modern dependency. It predates PSR-18 HTTP clients and current provider SDKs, so most teams are better off writing a small application-owned interface and adapters. Use the bundle only as a design reference.
- Why is a Symfony bundle a bad fit for Laravel?
- Symfony bundles rely on AppKernel registration, container compilation, and XML or YAML service definitions under Resources/config. Laravel uses service providers with register and boot methods plus its own container bindings and facades. There is no bridge or community precedent for running Symfony2 bundles inside Laravel.