- What Laravel versions does yab/quarx support?
- Quarx targets legacy Laravel versions, with v2.3.0 explicitly adding Laravel 5.4 support and effectively capping compatibility there. The package installs only where Composer constraints resolve to Laravel 5.x and PHP 5.6 through 7.1. It is not compatible with Laravel 6 or newer without forking or modernizing the codebase.
- Can I install Quarx CMS on Laravel 10 or Laravel 11?
- No, Quarx will not install cleanly on Laravel 10 or 11 because its illuminate package constraints conflict with modern Laravel dependencies. You will also encounter missing helpers, deprecated facade behavior, and a legacy Elixir/Gulp-era asset pipeline that no longer builds on current Node. The realistic options are pinning to a legacy stack, forking and modernizing the package, or running it as a separate legacy service behind an API.
- How do I install yab/quarx in a Laravel application?
- Install it with Composer only inside a compatible Laravel 5.x application running PHP 5.6 to 7.1. Quarx does not use package auto-discovery, so you must register its service provider manually and publish its configuration, migrations, and assets before running migrations. Because the schema is not well documented, review the published migrations and test the admin panel in a disposable environment first.
- Is Quarx CMS still maintained?
- The repository is archived and has effectively a bus factor of one historical maintainer, with no active downstream community exercising the code. There is no security patching cadence, so you should treat Quarx as unmaintained legacy software. If you adopt it, plan to own a fork indefinitely or isolate it behind a service boundary.
- What features does Quarx include?
- Quarx provides a built-in admin dashboard plus Eloquent-backed modules for pages, menus, blog posts, media, galleries, events, and custom modules. It also includes user, role, and permission management, along with a CRUD generator and module composer packager. Version 2.3.0 adds internal analytics and history/revert actions, which increase the privileged surface area you must maintain and audit.
- Is Quarx safe for production use?
- Quarx carries high technical risk in production because it is legacy, archived software with unpatched dependencies, no auto-discovery, and an undocumented schema. Its admin CMS is a privileged authenticated attack surface that handles file uploads, rich text, and user management, so it needs strict access controls and isolation. Review the new telemetry and module generation features carefully, and disable anything you do not explicitly need.
- How does Quarx handle users, roles, and permissions?
- Quarx ships with built-in user, role, and permission management inside its admin dashboard. That gives you a ready-made access-control layer for the CMS modules, but it does not remove the need to audit permissions for your own application code. Treat the admin area as a high-privilege surface and verify that roles cannot be escalated through module or file-management features.
- What is the Quarx module composer packager and should I disable it?
- The module composer packager is a v2.3.0 code-generation surface that scaffolds custom modules and therefore widens Quarx's integration footprint. It should be treated as a supply-chain concern because code generation can become a code-execution path if misused. Disable it or heavily constrain it in production unless a workflow explicitly depends on it.
- Does Quarx collect analytics or telemetry?
- Version 2.3.0 adds an internal analytics component, so you should confirm what it collects, where that data is stored, and whether any of it leaves your host network. This is a privacy and data-residency review item rather than just a feature toggle. If the collection behavior is unacceptable, disable or remove the component before deployment.
- What are good alternatives to Quarx for a modern Laravel CMS?
- For modern Laravel applications, evaluate actively maintained admin and CMS tools such as Filament, Backpack, Laravel Nova, or a headless CMS with a separate front end. Quarx is only a reasonable fit for a legacy Laravel 5.x application that needs a content back office quickly. If you must keep Quarx, isolate it as a legacy service and avoid importing its models directly into your main application.