Weave Code
Core Laravel Package
redaxo/core
REDAXO is an easy-to-learn, highly extendable PHP content management system and framework, trusted since 2004. Build content from custom modules with full control of any input and output, multilingual support, and workflows that adapt to you, backed by a friendly community.
REDAXO is a free, open-source content management system that has been under active development since 2004. Built on PHP, it provides an easy-to-learn website framework where you create content from custom modules with full control over any input and output.
REDAXO adapts to your workflow rather than forcing its own. It is multilingual, highly extendable, and backed by a friendly, helpful community.
- Custom modules – define inputs and outputs exactly how you need them
- Multilingual – interface available in English, Spanish, Italian, Swedish, and Portuguese
- Highly extendable – add-ons and a flexible architecture let you build your own workflows
- Full control – no imposed templates or rigid content structures
- MIT licensed – free to use, modify, and distribute
Frequently asked questions about Core
- Is redaxo/core a Laravel package?
- No. redaxo/core is the core of the REDAXO CMS, a standalone PHP content management system with its own bootstrap, autoloader, service locator, database layer, and request lifecycle. Composer require redaxo/core does not register a Laravel service provider, publish config, or expose facades. Treat it as platform adoption, not a library you drop into a Laravel app.
- How do I install redaxo/core with Composer?
- Run composer require redaxo/core, but expect a CMS runtime rather than a Laravel package. REDAXO uses its own bootstrap and lifecycle, so installation and upgrades follow REDAXO workflows, not Artisan commands. Version 5.21.5 is a patch release with no new features, deprecations, or breaking API changes.
- Can I use REDAXO as a headless CMS for Laravel?
- Yes, and the headless pattern is the cleanest architectural seam. Let REDAXO expose content over HTTP, have Laravel consume it with its HTTP client, and cache responses in Redis. This is straightforward, testable, and reversible. Avoid tight coupling through shared code or sessions.
- Does redaxo/core support Laravel 10 or Laravel 11?
- There is no Laravel version support in the usual package sense because redaxo/core does not integrate with Laravel's service container or lifecycle. If you co-locate REDAXO and Laravel, you maintain two PHP dependency trees and two PHP version constraints. Evaluate and upgrade each runtime independently.
- What are the risks of sharing a database between REDAXO and Laravel?
- Shared-database coupling is effectively a point of no return and is the riskiest of the three integration shapes. Version 5.21.5 shows the kind of drift you inherit: rex_sql_table now normalizes column types and defaults between MySQL and MariaDB and fixes cross-database foreign-key introspection when multiple databases share a server. A Laravel team is unlikely to anticipate these REDAXO-specific behaviors. Prefer API-mediated integration unless you accept that coupling.
- Is redaxo/core licensed for commercial or SaaS use?
- The README badge says MIT, but the technical assessment records the Composer license as NOASSERTION, so treat it as ambiguous until legal confirms terms. The ambiguity remains unresolved and is untouched by 5.21.5. That makes it a procurement blocker for commercial and SaaS deployment. Do not move past a spike without written clarification.
- How often is redaxo/core released and patched?
- Release cadence is now a concrete integration concern: roughly three patch releases and four published security advisories in about one quarter. That rhythm is normal, arguably healthy, for a CMS of REDAXO's vintage. Your integration must absorb it with a named owner and a tested patch runbook.
- What security issues were fixed in redaxo/core 5.21.5?
- The patch addresses a rex_api_package issue where admin status was not verified, session-ID and remember-me key rotation on password change, and CSRF on safe-mode toggling. These are patched in 5.21.5. They also show that REDAXO's defects cluster at authentication, permission, and session boundaries, which is exactly where any Laravel identity bridge sits.
- How should an SSO bridge handle revoked REDAXO permissions in Laravel?
- Define revocation propagation explicitly, not implicitly. Decide what the Laravel frontend does when an editor's REDAXO rights are pulled mid-session, including cache invalidation and token or session behavior. REDAXO's own guarantees in this area have historically been weaker than assumed, so test the seam.
- Is redaxo/core a good alternative to a Laravel CMS package?
- It is not a like-for-like alternative; REDAXO is a standalone CMS platform with its own module and extension-point model, not a Laravel package. Its procedural and global-function idioms are alien to many Laravel developers, so bus factor and team skill concentration are real risks. If you adopt it, use the headless API-mediated shape; otherwise stay with Laravel-native packages.
Weaver
How can I help you explore Laravel packages today?