A useful way to understand these Laravel concepts is by the role they play in the application, because several belong to MVC, several belong to Laravel's infrastructure, and others are architectural patterns that Laravel does not prescribe.
Version scope: This revision targets Laravel 13.x and Livewire 4.x conventions as of August 2026. Ecosystem packages such as Filament, Flux, and Blaze evolve independently, so check their
| <?php | |
| /** | |
| * Full-Page Livewire Component: Craft Search Demo | |
| * | |
| * In Livewire v4, you can define a component's PHP class and its Blade template | |
| * in a single file — this is called a "Single-File Component" (or "Volt" style). | |
| * | |
| * The anonymous class below IS the Livewire component. Livewire reads this class, | |
| * keeps it alive on the server between requests, and automatically syncs its |
In the context of a long-term project, considering moving a complex Laravel application to Craft 6, benefitting from stuff like multi-site, draft workflows for parts of content (the public facing website), while other content will continue to live in custom database tables.
The project has a significant amount of existing blade templates and relies heavily on Livewire/FLux for interactivity. The goal is to evaluate the feasibility of this migration and identify any potential challenges or benefits.
This is just a first look, just evaluating whether this path is still valid. Based on alpha 2 release, not yet stable.
| {# | |
| displayAll — Entry point for recursive element inspection. | |
| Renders the element itself, then walks its field layout to discover | |
| child elements (Matrix/relation fields, ContentBlock fields, rich-text | |
| fields) and recurses into each one, avoiding infinite loops via a | |
| global "handled" set. | |
| @param element Any Craft element (Entry, Asset, Product, Order, …) | |
| @param config Optional overrides: type, heading, level, include | |
| #} |
In Craft CMS 5, the elements table serves as the foundational registry for every piece of content and content-like object in the system. Rather than storing the actual content itself, it provides a unified identity layer that all element types—such as entries, assets, categories, users, and nested entries—inherit from.
Each row in the elements table represents a single element instance and contains core, globally relevant metadata that is independent of site, field layout, or element-specific attributes. This includes the element’s unique ID, its fully qualified class type (which determines behavior and capabilities), and system-level state flags such as whether the element is enabled, archived, or soft-deleted. It also tracks lifecycle timestamps like creation and last update dates.
The key architectural role of this table is to decouple identity and lifecycle management from both localization and content storage. Site-specific da
| <?php | |
| namespace modules\temp\console\controllers; | |
| use Craft; | |
| use craft\console\Controller; | |
| use craft\elements\Entry; | |
| use yii\console\ExitCode; | |
| /** |
This documentation explains how to use the @extras/_actions.twig component in Craft CMS to call web controller actions via JavaScript and display success or error notices.
The Actions component allows you to make asynchronous requests to Craft CMS web controller actions and handle responses within your JavaScript code. Additionally, the component can display success or error notifications to users based on the outcome of the requests.
| <?php | |
| namespace modules\art\services; | |
| use Craft; | |
| use craft\base\Component; | |
| use craft\elements\Asset; | |
| use craft\fs\Local; | |
| use craft\helpers\Console; | |
| use Exception; |
| <?php | |
| namespace modules\main\controllers; | |
| use craft\elements\Entry; | |
| use craft\web\Controller; | |
| use yii\web\Response; | |
| /** | |
| * Content controller |