- How do I send an SMS notification in Laravel with Kudisms?
- Create a Laravel notification class and return the package's Kudisms channel from its via method. The channel uses your configured API credentials and sender ID to deliver the SMS to the notifiable's phone number. Use Laravel's Notification facade or the Notifiable trait to trigger it, and queue the notification if you do not want the request to wait on the gateway.
- What PHP and Laravel versions does kudisms-notification support?
- The 2.0.0 release requires PHP ^8.3 or ^8.4 and Illuminate ^12.0 or ^13.0, so it targets Laravel 12 and 13. That means applications still on Laravel 11 or PHP 8.2 cannot install 2.0.0 without upgrading the framework or runtime first. The constraint also excludes PHP 8.5, so check your platform roadmap before adopting it.
- How do I install and configure toneflix-code/kudisms-notification?
- Install it with Composer using the package name for the line you are adopting, then publish the package config if you need to customise defaults. Set the Kudisms API credentials and sender ID in your environment or config, and confirm the config filename and key names after the 2.0.0 rename. Finally, reference the channel from your notification's via method.
- Does kudisms-notification support queued SMS notifications?
- Yes. The package is described as compatible with queued notifications, so you can implement ShouldQueue on your notification or dispatch it through a queue. That keeps the HTTP call to Kudisms off the request path and lets Laravel retries and failure handling apply. Test the queued path as well as the synchronous path.
- Can I send a Kudisms SMS to multiple recipients in Laravel?
- Yes. Laravel notifications can be sent to one or many notifiables, and the package's blurb explicitly supports one or many recipients. Use Notification::send with a collection of notifiables that expose phone numbers, or send on-demand notifications for ad hoc numbers. Watch provider rate limits and consider chunking or queuing large sends.
- Is toneflix-code/kudisms-notification maintained and production-ready?
- The 2.0.0 release shows active maintenance, including Testbench and Pest dev dependencies and support for a newer Laravel major. However, the vendor and namespace rename resets ecosystem signals such as stars and download counts, so verify the Packagist record and GitHub repository transfer independently. Check whether 2.0.0 declares replace or provide for the old package name, pin a version, and review the rename diff for behavioural changes before production use.
- What changed in kudisms-notification 2.0.0 and how do I migrate?
- 2.0.0 renames the vendor from toneflix-code to toneflix and the namespace from ToneflixCode\KudiSmsNotification to Toneflix\KudiSmsNotification, while raising PHP and Laravel constraints. The upgrade notes describe a manual composer remove and require sequence, and they tell you to update the published config. Re-check config references, env var names, queue and failure-handling overrides, and any transitive dependency still requiring the old package name.
- Do I need to change config or env variables after the Kudisms package rename?
- Yes, verify them. The release notes say to update the published config, which implies the config key or filename may have moved. Any config call, env variable name, or channel override in application code should be re-checked rather than assuming the rename was cosmetic. Also confirm whether the old package name remains installable alongside the new one.
- How can I test Kudisms SMS notifications without sending real messages?
- Use Laravel's Notification::fake to assert that your notification was sent and to inspect the channel and notifiable without hitting Kudisms. For channel-level tests, fake the package's API client or the underlying HTTP calls, and keep real credentials out of the test suite. Include a queued-notification test if you rely on background delivery.
- What are alternatives to the Kudisms notification channel for Laravel SMS?
- You can use another Laravel SMS notification package, build a small custom channel around the Kudisms API, or keep Kudisms behind a queued job if you do not need notification integration. Compare Laravel version support, PHP constraints, maintenance activity, queued delivery, and vendor history before switching. If you stay with this package, the main alternative risk is the recent vendor rename and its effect on supply-chain signals.