Weave Code
Phplist4 Core Laravel Package
phplist/phplist4-core
Core library for phpList 4, the open-source newsletter and email marketing platform. Provides foundational PHP components for managing subscribers, mailing lists, campaigns, and queue processing, enabling developers to build and extend self-hosted email marketing systems.
This module is the core of phpList 4. Join discussion at the community forum: https://discuss.phplist.org/
Frequently asked questions about Phplist4 Core
- Is phplist/phplist4-core a Laravel package?
- No. phplist/phplist4-core is the core module of phpList 4 and is framework-agnostic PHP domain/application code, not a Laravel package. It does not provide Laravel service providers, facades, config publishing, or Eloquent integration. Treat it as a Composer dependency behind application-owned adapters rather than a drop-in Laravel component.
- What is phplist/phplist4-core used for?
- It provides foundational PHP components for phpList 4, the open-source newsletter and email marketing platform. The core domain covers subscribers, mailing lists, campaigns, and queue processing for self-hosted email marketing systems. It is most relevant if you need phpList-style list and campaign behavior and are willing to own integration glue.
- How do I install phplist/phplist4-core in a Laravel app?
- Composer installation may be possible, but expect manual wiring rather than Laravel auto-discovery or package conventions. First verify PHP version compatibility, transitive dependency conflicts, and database assumptions against your target Laravel app. A time-boxed spike in a branch or standalone Laravel test app is safer than adding it directly to production.
- Does phplist/phplist4-core support Laravel 10 or Laravel 11?
- There is no declared Laravel version support because this is not a Laravel package. Compatibility depends on PHP, Symfony/Doctrine, PSR versions, database drivers, and other transitive dependencies. Given the last release date of 2021-03-02, newer Laravel versions are unlikely to work without patching or isolation.
- What license does phplist/phplist4-core use and can I use it commercially?
- The package uses AGPL-3.0, which is a product-level constraint rather than a simple permissive license. It is especially risky for hosted or distributed commercial offerings and requires legal review before adoption. Do not assume MIT-style commercial flexibility without confirming your deployment model with legal counsel.
- Is phplist/phplist4-core actively maintained?
- The last release date is 2021-03-02, and community signal is low, with only about 89 stars in the assessment context. The adopting team should expect to own dependency patching, PHP compatibility checks, and possibly a fork. There is no Laravel vendor support path, so internal documentation and a named owner are required.
- Can I use phplist/phplist4-core for subscriber management and campaign orchestration in Laravel?
- It may be reusable behind adapters for subscribers, lists, campaigns, queues, and delivery status, but only inside an isolated bounded context. Keep Eloquent models and phpList domain models separated through data mappers or anti-corruption layers. Start with the smallest workflow, such as importing subscribers and creating a draft campaign, before committing to broader integration.
- How should I test a phplist/phplist4-core integration in Laravel?
- Run a time-boxed technical spike in a branch or standalone Laravel test app. Verify Composer resolution, schema assumptions, database coexistence, and the core workflows your product needs. Add integration tests around your own adapter interfaces rather than relying on native Laravel testing helpers for phpList behavior.
- What are alternatives to phplist/phplist4-core for Laravel email marketing?
- For transactional email, use Laravel's mailer and maintained transport packages. For campaign and list management, evaluate maintained Laravel-friendly packages, internal domain code, or a hosted email marketing service. If phpList core integration fails, use it as a reference implementation rather than a runtime dependency.
- What production risks should I plan for with phplist/phplist4-core?
- Key risks include AGPL-3.0 licensing, a stale 2021 release, PHP and dependency deprecation, unclear maintainership, and database schema ownership conflicts. Queue integration, observability, security patching, and migration coexistence all need explicit design. Keep interfaces package-agnostic and maintain an exit plan so the core can be replaced without rewriting product workflows.
Weaver
How can I help you explore Laravel packages today?