- Does graham-campbell/cms-contact work with Laravel 8, 9, 10, 11, or 12?
- No. The package is declared for Laravel 4.1 only, so it is not compatible with modern Laravel releases. Its illuminate/* constraints are likely to conflict with Laravel 8 through 12 in Composer. Do not try to shim it into a modern application; the service provider contracts have diverged too far.
- How do I install graham-campbell/cms-contact?
- Install it with Composer using composer require graham-campbell/cms-contact in a Laravel 4.1 application. Because the latest release is 0.2.0-alpha, you may need to allow alpha stability in your Composer configuration. Check the repository for the exact service provider registration and configuration steps, since the release notes do not describe them. This package should only be installed where Laravel 4.1 is already the platform.
- What does graham-campbell/cms-contact actually do?
- It is a CMS Core plugin that adds a contact form backend to Laravel CMS applications. It provides models, migrations, and routes for receiving enquiries and storing contact submissions. It is not a full CMS itself; it integrates contact functionality into an existing CMS-backed site. The available release notes do not describe the public API or configuration in detail.
- Is graham-campbell/cms-contact still maintained?
- The repository now lives under GrahamDeprecated, and the latest release is 0.2.0-alpha. The changelog contains only housekeeping entries such as documentation updates, minor tweaks, and unit test adjustments. There is no stated policy for tracking supported Laravel versions. Treat it as legacy software rather than an actively maintained package.
- Can I use cms-contact in a new Laravel project?
- No, not realistically. The package requires Laravel 4.1, which is end-of-life and receives no security patches. A new project should use a maintained contact form implementation built on current Laravel mail, validation, and database features. Pulling this package into a modern app is likely to create unresolvable dependency conflicts.
- What Laravel and PHP versions does cms-contact require?
- The package declares support for Laravel 4.1 only. That implies a PHP 5.x-era runtime, typically PHP 5.4 to 5.6, rather than PHP 8.1 or newer. It is not tested against Laravel 8 through 12 according to the available information. Confirm the exact composer.json constraints before planning any integration.
- Why does Composer conflict when I require cms-contact with a modern Laravel app?
- The package pins Laravel 4.1, which usually means narrow illuminate/* version constraints. Modern Laravel applications require much newer illuminate/* components, so Composer cannot resolve both sets at once. This is the classic dependency-graph conflict caused by mixing a legacy package with a current framework. Wrapper code will not fix the underlying constraint mismatch.
- Is upgrading to cms-contact 0.2.0-alpha a breaking change?
- It may be. The 0.2.0 release changed the autoloading strategy to PSR-4, and alpha releases carry no backward-compatibility guarantee. Existing 0.1.x consumers should check that previously referenced class names still resolve. Review the docs diff and composer autoload block before upgrading.
- Does cms-contact have tests and documentation?
- The changelog mentions tweaked unit tests, so some tests exist, but no test count or coverage figure is published in the available information. There is no functional documentation in the release notes describing features, configuration, or the public API. You would need to inspect the repository directly to assess test quality and usage.
- What should I use instead of cms-contact for a Laravel contact form?
- Use Laravel's built-in validation, mail, notifications, and Eloquent models to build a contact form appropriate to your Laravel version. Alternatively, choose a maintained package that explicitly supports your Laravel release. The key requirement is a package with current illuminate/* constraints and active security maintenance. Do not adopt a Laravel 4.1-only package for greenfield work.