Upgrade commands

  • The admin:upgrade command and its steps (admin:upgrade:config, :settings, :icons, :navigation, :dates) rewrite source files. The last step, admin:upgrade:cache, only reports closures in config files and env() outside them, which have to be changed by hand; it fails while any is left. Run them in a local working tree and commit the result; in the production environment they refuse to run unless --force is passed. admin:upgrade --force forwards the option to every step.

Modals and toasts moved to @crudadmin/helpers

Breaking change for every custom admin component that opens a modal or a toast. Calls to the removed APIs throw at runtime.
  • Removed useModalStore (also from window) and the component methods this.openModal(), this.successModal(), this.errorModal(), this.warningModal() and closeModal(). Use Modal and Toast from @crudadmin/helpers/modal, available as window.Modal and window.Toast in custom components.
  • openModal({ toast: true }) no longer exists. Modals do not open toasts; use Toast.success(), Toast.error(), Toast.warning() or Toast.open().
  • The close callback of a modal is now cancel. It runs from the close button, the X button and Escape. Returning false from success, cancel or an action still keeps the modal opened.
  • Modal objects changed shape: modal.title, modal.message and modal.type are in modal.message.title, modal.message.text and modal.message.type; modal.visible and modal.openedAt are in modal.state; modal.class and modal.key are in modal.options; component props are in modal.props. modal.id stays.
  • Components opened in a modal receive the modal in the modal prop, the separate actions prop is no longer passed; read modal.actions.
  • Modal options are read from one place: the options of the opening are merged with the options of the wrapper component, whose values win. Only the class of both is kept together.
  • Renamed modal options: escClose became dismissible (Escape closes a modal with no closing action) and hiding the footer is footer: false instead of actions: false. The old names keep working.
  • The form of a model opened in a modal (a row of the table, a relation opened from a select field) is no longer a Bootstrap modal. It is an entry of the same manager as every other modal, drawn in a .row-action-modal wrapper; the #modal-inline-… element, its Bootstrap instance and the .modal-backdrop are gone.
  • The RowActionModal component is not registered globally any more and is not placed in a template. The form of a model is opened on the model itself: model.modals.add(), edit(id), view(id), list(), form() and close(). A model which opens its own form in a modal (a relation, a sub model) turns it on with model.modals.enable(); form.modal in the settings still does it on its own.
  • Removed the setBootstrapModalZIndexes() helper. Modals are stacked in the order they were opened.
  • The listing button of a relation select is marked with data-list-relation-row instead of a second data-add-relation-row; update selectors of custom tests.
  • Rows requested before their table is drawn now use the default page size instead of asking for no rows. A relation listing opened from a select field used to open empty.
  • The page behind an opened modal no longer scrolls. The administration sets the --modal-open class on <html>; custom styles that scrolled the page while a modal was open have to account for it.

Model settings editor

  • UI settings can now be stored in the models section of bootstrap/admin.php, keyed by the model class basename; commit and deploy this file. Existing $settings, settings() and mutators remain supported, with its overrides applied last.
  • Use column snapshots instead of new columns.*.before / columns.*.after declarations on field columns. A virtual column still needs before / after, it has no field to anchor it. Run admin:upgrade:settings --dry-run, then admin:upgrade:settings to move supported literals and convert the ordering. Resolve reported dynamic expressions manually.
  • Explicit column visibility overrides can reveal hidden fields; snapshots retain shared visibility and order, while personal preferences remain above them. Password and inaccessible columns remain excluded.
  • The table heading title.rows is an editor setting too, next to title.create and title.update: admin:upgrade:settings moves it into the file and the heading of the table has its own pencil.
  • columns.*.name now takes precedence over a field’s column_name, so editor changes also apply to fields with a custom column label.
  • Editing requires full superadmin access, APP_DEBUG=true and a non-production environment. Production uses the deployed file without exposing the editor.
  • The editor mode is the separate development package crudadmin/admin-editor: run composer require --dev crudadmin/admin-editor. Without it the administration has no editor mode, no pencils and no settings endpoints; bootstrap/admin.php is still read. config('admin_editor.enabled') = false turns it off in a project that has it installed.
  • The endpoints GET|PUT /admin/api/models/{table}/settings (route names admin.models.settings.*) and Admin\Controllers\Dev\ModelSettingsController moved into the package, the controller is AdminEditor\Controllers\ModelSettingsController and its gate AdminEditor\Editor::available().
  • The frontend of the editor is built by the package itself (dist/admin-editor.js, published to public/vendor/crudadmin-admin-editor by php artisan admin:update); the resources build carries no editor code. The administration renders what the package registers into named places (EditorSlot, useEditorExtensions()), custom components read the switch with useEditorMode().isActive() instead of useEditorModeStore(). useModelApi().settings() and updateSettings() were removed.
  • Packages building their own scripts for the administration import its API as @crudadmin/admin, mapped onto window.crudadmin.admin (useSettingStore, useModelStore, useTableStore, useHeaderStore, useAuthStore, useAxios, useApiUrl, useGenerateUuid, useEditorExtensions, useEditorMode, Modal, Toast); vue, pinia, vuedraggable and lodash are the existing globals. crudadmin/skeleton carries the build setup.

Renamed and removed model settings

admin:upgrade:settings rewrites these in models under app/ and reports what it cannot convert. Settings of packages and of dynamic settings() methods have to be changed by hand. Renamed:
  • title.insert → title.create and title.edit → title.update. Both were aliases with their own precedence rules; declare one heading per form. A model declaring the alias next to its target is reported and left unchanged.
  • title.tab → tabs.name, form.tabs → tabs.enabled, tabs_autoload → tabs.autoload. Every tab setting lives under tabs.* now. Write 'tabs.enabled' => false, not 'tabs' => false, so the key stays usable next to tabs.default.
  • sortable → table.sortable. The $sortable model property (drag and drop of rows) is not affected, the setting only turns off sorting by clicking column headers.
  • Every setting now lives under the area it affects, and its name says what it controls instead of naming an action or a database term. The migrator moves all of them.
  • table.actions and layout.header are the counterparts of form.actions and form.header, which is what the old actions and header names hid. layout.* holds the settings of the area around the table and the form: layout.header is the bar with the grid switcher, search and add button, layout.split_view keeps the table next to the form in the full grid.
  • editable moved to form.editable and keeps its polarity, it is not inverted into a readonly key. It still only changes the browser; forbid updates with the $editable property.
  • A switch of a whole area is its enabled key: table → table.enabled, form → form.enabled, search → search.enabled, pagination → pagination.enabled, filter → filter.enabled, form.modal → form.modal.enabled. The bare boolean keeps working, the migrator only normalizes it; a declaration of the same name holding an array is the group itself and is left alone.
  • The settings payload of the Vue app is the nested form of these keys, so custom components read settings.table.increments where they read settings.increments, and settings.layout.split_view instead of settings.table.splitmode.
Removed:
  • orderBy. Use the $orderBy model property, which orders the query and the table at once.
  • rows.eachRequestInitial. Only the first rows request of a model is initial again, so field options and getAdminModelInitialData() are no longer rebuilt on every refresh of a model that declared it.
  • columns.*.invisible and columns.*.column_visible. Use columns.*.hidden; a virtual column declared with invisible was hidden and is now visible unless hidden is set.
Grid:
  • grids → grid.sizes, and grid as a list of sizes, grid.enabled, grid.disabled and grid.{size}.enabled / .disabled are all replaced by that one list. The switcher hides itself when one size is left, so 'grid.enabled' => false becomes 'grid.sizes' => ['<the size you keep>']. Declarations which only repeat the default ('grid.enabled' => true, 'grid.full.enabled' => true) are removed. Column widths of CrudAdmin 5 (4, 8, 6, 0) become small, big, half and full; any other number was ignored by CrudAdmin 5 and is removed.
  • The migrator computes the list from the old keys. It reports a dynamic grid value, a switcher turned off without grid.default, and old keys declared next to a size list.
  • grid.default stays and keeps its second effect: a form of 20 or more fields opens in the full grid unless the model declares grid.default or grid.sizes.

Rows response buttons

The rows endpoint (/admin/api/models/{table}/rows) and the insert response no longer repeat every button under each row. buttons_definitions carries each button once, keyed the same way as before, and buttons.{id} holds per row only the properties in which that row’s button differs (a name or class computed from the row). Custom JavaScript reading response.buttons has to merge the two; the admin app does it in setRowsData() and addCreatedRows(), so code working with model.getRowsData().buttons or getButtonsForRow() is unchanged.

Default module icons and form texts

  • Known table names supply many more default sidebar icons (warehouses, stock, prices, branches, workers, courses, questions, notifications and others). A module without an icon that showed none can now show one; declare the icon setting when the module has to keep its own.
  • Tables ending with forms, inquiries, submissions and applications used fa-wpforms, a brand icon the administration does not bundle, so nothing rendered. They now use far fa-list-alt.
  • Default titles and buttons are merged key by key. Models of the time, appointment, booking, lector and training table names that declared only some of title.create, title.update or buttons.create used to lose the remaining defaults; those are applied now. Declare the setting explicitly to keep a different text.

Removed field types

type:array

  • Removed type:array; replace it with type:json in field definitions.
  • Values are now automatically decoded into PHP arrays instead of returned as raw JSON strings. Review manual json_decode() / json_encode() calls and custom casts.
  • type:json is hidden from admin table rows by default, which may affect custom table components.
  • Invalid JSON strings in admin requests are decoded to null; review validation if malformed input must be rejected.
  • The database column remains JSON; existing data does not need conversion solely for this replacement.
  • The array validation rule and multiple parameter remain supported.

type:boolean

  • Removed type:boolean; replace it with type:checkbox in field definitions, including array notation.
  • The database column remains boolean (tinyint(1) on MySQL); existing 0/1 data does not need conversion solely for this replacement.
  • Model and API values are cast to false/true instead of integers. Review strict comparisons such as === 1 and consumers expecting numeric values.
  • Checkbox adds a form input and boolean validation. A missing checkbox in an admin request normally becomes false; review partial updates.
  • The boolean validation rule remains supported.

Removed commands

admin:queue

  • Removed admin:queue; remove its calls from cron and the Laravel scheduler.
  • Run Laravel’s php artisan queue:work with a process manager such as Supervisor instead. Otherwise jobs may remain unprocessed after the upgrade.
  • Move any custom queue.admin.cli, queue.admin.log_path, queue.admin.timeout, queue.admin.sleep and queue.admin.tries settings to the worker command and process manager configuration; CrudAdmin no longer reads them.

Configuration changes

Config keys grouped

Breaking change for every project. Outside production the administration throws on boot while config/admin.php still declares an old key, because a switch left on its old name is read as unset and turns its feature off silently. In production the old values are still applied and the rename is only logged.
  • Run php artisan admin:upgrade:config --dry-run and then php artisan admin:upgrade:config to rewrite config/admin.php. The command moves the declarations with their comments and reports what it cannot convert. Keys of packages and configs built at runtime have to be changed by hand.
  • Prefixed keys moved under the group they belong to, and switches which had companion keys became a group with an enabled key.
  • image_rewrite_missing_uploads and rewrite_missing_upload_images were two keys for one behaviour, as were admin_groups and admin_roles. Keep one of each pair; the migrator reports a project declaring both with different values and leaves them for you to resolve.
  • admin.frontend_editor was truthy whenever the crudadmin/website package was installed, because its default is an array. It is read as frontend_editor.enabled now, so images of a project with the editor disabled are no longer routed through the editor.
  • Deleted keys which no longer did anything: sitebuilder (the module was removed) and image_compression_quality (unread since v5, use images.lossy_quality). The migrator deletes them; their values are not moved, because a key that did nothing must not start applying.
  • groups moved into the navigation section of bootstrap/admin.php, see Menu in the navigation section.
  • name, locale, license_key, models, modules, components, app_namespace, resources_provider, custom_rules, global_rules, filemanager, api and sitetree are unchanged.
  • Packages merging their defaults into config('admin') merge them key by key inside a group now, so a project value no longer replaces the whole group of the package. Values of the project stay in front of the values a package appends, across any number of packages.
  • A package still merging an old key has it mapped onto the new one and logged as a warning instead of throwing, because the project can not migrate a package. Migrate the config of your own packages with admin:upgrade:config --path=src/Config/admin.php.

File browser configuration

  • Removed the ckfinder boolean and boolean filemanager settings; use filemanager.type (none, lfm or ckfinder). CKFinder itself remains supported.
  • Replace 'ckfinder' => true with 'filemanager' => ['type' => 'ckfinder']; keep license_name and license_key inside that array.
  • Replace 'filemanager' => true with 'filemanager' => ['type' => 'lfm']; use ['type' => 'none'] to disable the browser.
  • Old boolean settings no longer enable a file browser. Update project configuration before upgrading.

Legacy file configuration

  • Removed the unused file config section (exists_cache, exists_cache_days, redirect_after_resize). Remove it from project configuration if present.
  • These keys already had no effect in v5; file uploads and image resizing are unchanged.
  • Use images.resizer.storage_cache, images.resizer.storage_cache_days and images.resizer.redirect_after_resize to configure the corresponding behavior.

Config cache

  • php artisan optimize and config:cache are supported and belong at the end of the deploy script. Earlier versions were deployed without them.
  • Config files no longer support closures (function () {}, fn () =>), config:cache fails on them. Replace each with a [Class::class, 'method'] callable of a static method (appearance.logo, admin_helpers.auth.otp.user, groups merged by packages as [[Class::class, 'method']]).
  • env() can be called only in config files. Code which called env() anywhere else in the project (controllers, models, helpers, routes, blade views, bootstrap/) gets null with a cached config: move each value into a config file (config/services.php or a config file of the project) and read it with config().
  • php artisan admin:upgrade:cache lists every closure in the config files and every env(), getenv(), $_ENV and Env::get() call outside them, with files and lines.
  • route:cache caches also the routes of localizedRoutes(), see Localized routes. Routes marked with ->visible() are kept in the route action, so the frontend editor finds them also in cached routes.
  • Packages read their environment values through config keys, the variables stay the same: crudadmin/helpers (admin_helpers.auth.verificator, admin_helpers.bundle.*, admin_helpers.smartsms), crudadmin/payments (admin_payments.store_debug, admin_payments.paypal.webhook_id, admin_payments.gopay.*), crudadmin/socialite (admin_socialite.paypal_mode, admin_socialite.instagram_secret), crudadmin/invoices (invoices.xz_path, invoices.omega.*) and crudadmin/eshop (admin_eshop.nuxt.*, admin_eshop.store_debug, admin_eshop.delivery.shipping.*, admin_eshop.attributes.ids.*, admin_eshop.payment_methods.cash_on_delivery.*, admin_eshop.reports.archive; see its MIGRATION-5.0.md). The new keys are merged from the package also into a published config file of the project.
  • crudadmin/gutenberg publishes its assets with the admin.resources tag of admin:update; 'gutenberg' => true is no longer needed for that.
  • The file manager lfm.private_folder_name is a handler class instead of a closure; a project config which overrides it with a closure has to use a class with a userField() method.
  • New config keys read from the same environment variables as before: admin.storage.clean_items_limit (STORAGE_CLEAN_ITEMS_LIMIT), admin.sitetree_editor (ADMIN_SITETREE_EDITOR) and admin.frontend_editor.url (APP_NUXT_URL or WEB_URL) of crudadmin/website.

Cache of serialized models

  • Laravel 13 sets cache.serializable_classes to false in a new config/cache.php: objects come back from the cache store as __PHP_Incomplete_Class. CrudAdmin caches models and collections (runCached(), Admin::cache() with a store, bootstrap sections, invoice settings), every request reading one fails. Set 'serializable_classes' => true in config/cache.php (or a list of the cached model classes). Projects upgraded from Laravel 12 have no such key and keep the old behaviour.

Package service provider

  • Packages extend Admin\Providers\AdminPackageServiceProvider and declare their config, admin config, routes, models ($models or models()), listeners, commands, field mutations, views, assets and publishable files in properties, see Package service provider. The base provider skips config merging with a cached config and route files with cached routes.
  • Removed Admin\Providers\AdminHelperServiceProvider. Extend AdminPackageServiceProvider, it has the same helper methods (mergeAdminConfigs(), mergeConfigs(), pushComponentsPaths(), registerFacades(), registerProviders(), bootRouteMiddleware()), and move the work of register()/boot() into its properties. A subclass which keeps its own register() or boot() calls parent::register() / parent::boot().
  • All CrudAdmin packages have a single provider now. Their separate config, route and event providers were removed; they extended Laravel’s RouteServiceProvider and EventServiceProvider, which with the Laravel 11 skeleton loaded the routes of the application once more per package and added the email verification listener of Registered once per package. Projects which referenced such a provider of a package (e.g. AdminEshop\Providers\RouteServiceProvider) remove the reference.
  • Built assets of a package are declared in $assets (source => directory in public/). admin:update publishes them with the admin.resources tag and crudadmin adds their directories into the project .gitignore; the OnAdminUpdateListener classes of the packages were removed.
  • Package configs merged by $config keep the values of the project and add missing keys, a list of the project replaces the list of the package (e.g. admin_helpers.notifications.platforms, admin_eshop.cart.mutators). Before, some packages appended their list items to the project list.
  • The blade view namespaces of packages use the same name as their config: admin_payments:: instead of adminpayments:: (crudadmin/payments) and admin_eshop:: instead of admineshop:: (crudadmin/eshop). Projects which override the views move resources/views/vendor/adminpayments to resources/views/vendor/admin_payments and resources/views/vendor/admineshop to resources/views/vendor/admin_eshop, and rename the old namespaces in their views and code. The admin_eshop.views publish tag publishes into resources/views/vendor/admin_eshop.
  • crudadmin/socialite routes are named socialite.redirect, socialite.callback and socialite.token; they are no longer marked ->visible() for the frontend editor, which needed crudadmin/website. crudadmin/gutenberg routes are named gutenberg.oembed and gutenberg.image-upload and use the admin.panel middleware group.

Localized routes

  • Removed the unused routes config key; remove it from project configuration if present. Existing routing behavior is unchanged.
  • Register language-prefixed routes with localizedRoutes() of the crudadmin/website package.
  • localizedRoutes() registers the routes file once for every language instead of per request, so the routes work with route:cache and Laravel Octane. The languages are read when the routes are registered: run route:cache again (or reload the Octane workers) after a language is added or its slug changes.
  • Named routes of the other languages than the default one get the language slug as a prefix (en.front), the default language keeps the names. route('front') and action() still return the URL in the current language; for another language use AdminWebsite\Routing\LocalizedRoutes::withLocale('en', fn () => route('front')).
  • On pages of the other languages Route::currentRouteName() returns en.front, check routes with request()->routeIs('front', '*.front'). A project with its own URL::formatPathUsing() calls LocalizedRoutes::formatPath($path, $route) inside its formatter.
  • ?_locale with an unknown language redirects to the default language. The redirect of the default language slug is registered whenever localization.remove_default is on.
  • Deprecated: the addLocalizationAttributes() router macro, Localization::prefix(), addLocalizedRoutes(), getLocalizedRouter() and $localizedRouters.

Renamed framework namespaces

crudadmin/framework is grouped by area, the Helpers, Contracts, Utilities and Requests namespaces are gone. php artisan admin:upgrade:namespaces (the first step of admin:upgrade) rewrites the references in the project: imports, fully qualified names, class names in strings and Blade templates, use DataStore of classes. While crudadmin/upgrade is installed the old names keep working as aliases, so the project boots before the rewrite. The step reports references it can not rewrite. The moved classes: crudadmin/crudadmin is grouped the same way, Helpers, Contracts, Controllers, Middleware, Requests and Hashing are gone: Admin\Models\*, Admin\Admin\Buttons\*, Admin\Admin\Rules\*, Admin\Eloquent\* and Admin\Fields\* keep their names. admin:upgrade:namespaces rewrites these classes too, also real-time facades (Facades\Admin\Helpers\...). Facades (AdminCore, Fields, Image, ImageCompressor) and the global helper functions keep their names. Run composer update crudadmin/framework after the upgrade, the file with the global functions moved.

Laravel Octane and long running processes

CrudAdmin runs on Laravel Octane and in queue workers. Before every request, Octane task and tick and every queue job (except the sync connection) the state of CrudAdmin returns to the state after the boot.
  • Admin::cache(), Admin::get(), Admin::set(), Admin::push() and cache() of the DataStore trait keep values for one request or queue job, under PHP-FPM nothing changes. Code which relied on a value cached in a queue worker for all following jobs reads it again for every job. A new DataStore::persist() keeps values derived from the code and the config for the whole process.
  • Queue workers forget resolved facades before every job (except the sync connection), as Octane does before every request.
  • New Admin\Core\State\RequestScoped attribute: a static property marked with it gets its default value back before every request and job, with #[RequestScoped(boot: true)] its value after the boot. The flushers of the packages are replaced by it: Cart::flushState(), LocalizedRoutes::flushState(), ApiSchema::flushState(), CKFinderHelper::flushState(), LocalizationHelper::flushState(), AdminResourcesSyncer::flushState(), Benchmark::flushState() and the flushState() of the bank accounts of crudadmin/invoices are removed, as the RestoresBootState trait and restoreBootState() of crudadmin/eshop.
  • Octane and queue workers keep base fields and relations trees of the models for the whole worker, for every language, as admin:cache compiles them. Code in fields(), mutateFields(), mutateBootedFields() and field mutations which reads the logged administrator, the request or the database without being detected moves into a runtime mutation, getFields($row) or options.
  • Static properties which only held constants became class constants: HasAdminExportsGenerators::$tempDir is TEMP_DIRECTORY, AdminResourcesSyncer::$fieldsTranslatableKeys is FIELDS_TRANSLATABLE_KEYS. The deprecated FileMutator::$requiredAttributes is removed, use RequiredRules::RULES. SeoModule::$metaKeys of crudadmin/website is SeoModule::META_KEYS, SocialAuth::$errorMessageKey and $photoColumn of crudadmin/socialite are ERROR_MESSAGE_KEY and PHOTO_COLUMN.
  • The booted model properties (fillable, casts, dates, hidden) and the boot() of model modules run once per worker, language and variant (web, console) instead of once per request. A module boot() or a cachableFieldsProperties() callback which reads the request beyond the administration, the website and the console overrides getCachablePropertiesVariant() of the model.
  • New Admin\Core\State\RequestShared attribute for static properties kept for the whole process (registries, caches derived from the code). Mark every static property of the project with #[RequestScoped] or #[RequestShared], php artisan admin:upgrade:statics lists the ones without them and the static variables of functions.
  • New Admin\Core\State\RequestState: flushUsing() registers a reset of other state, bootRequestUsing() runs request-dependent code of a service provider for every Octane request (right away under PHP-FPM), iniSet() changes a php.ini option until the end of the request.
  • AdminPackageServiceProvider has $flush (classes with a static flushState(), or callables) and 'shared' => true for $facades entries of registries. The admin.fields registry (Fields facade) is a singleton.
  • Localization::fire() runs through bootRequestUsing(). Localization instances no longer register an own LocaleUpdated listener, one listener registered at boot passes the locale to the instances of the request. LocalizationHelper::$skipChangeEvent is removed.
  • autoAjax()->throw(), throwValidation() and render() throw AutoAjax\AutoAjaxResponseException (a HttpResponseException) instead of sending the response and calling exit. The status and body are the same and code after the call still does not run, but a surrounding catch (Exception|Throwable $e) now catches it: rethrow it, or pass $e to autoAjax()->error($e), which rethrows it. The response goes through the middleware now (session, queued cookies, CORS).
  • autoAjax()->setMessage() changes only its response, use AutoAjax::setGlobalMessage() or AutoAjax::$messages at boot for defaults; values can be closures (fn () => _('...')) resolved in the language of the request. onResponse events always get the AutoAjax instance as the second argument, a callback which returns nothing no longer empties the response. AutoAjax::setEvent() ignores the same callback twice and accepts a key which replaces the previous registration.
  • crudadmin/payments: PaymentService::setPaymentUrl(), setOnPaymentSuccess() and setOnPaymentError() called in a service provider boot() apply to every request, called later they apply to the current request only. The protected $onPaymentUrl defaults to null. Removed the unused PaypalWebhookVerificator::$initialized. A failed payment initialization is tried again by the next call in the same request. Stripe and PayPal webhooks read the body and the signature from the Laravel request.
  • crudadmin/socialite: SocialAuth::onSuccess() affects only that instance, use SocialAuth::setEvent('SUCCESS_DATA_RESPONSE', ...) in a provider for a global handler. addDriver() registers its extension once.
  • crudadmin/eshop: settings of the eshop services called in a provider boot() are kept for every request (Discounts::addDiscount(), addDiscountableAttributes(), OrderService::setMutators(), setStockSync(), setDefaultResetIfNotPresent(), Store::setRounding(), CartDriver::setInitialData()), called during a request they apply to that request only; setInitialData() from boot() runs for every new cart driver. Cart::setCartToken(), Mutator::setForceCartResponse(), the setGlobalFilterOptions() scope and the DPD/Packeta set*Builder() calls made during a request are reset before the next one. Store, OrderService and CartDriver have constructors, a subclass with its own constructor calls parent::__construct(). Validation messages of the eshop rules are translated when a rule fails. The bootstrap response cache key has a .b2b suffix for B2B carts.
  • crudadmin/resources: removed CKFinderHelper::$booted, the connector is bound by the service provider as Admin\Resources\Helpers\Filemanagers\CKFinder\Connector (a project binding of ckfinder.connector is kept) and ckfinder_config_mutator() runs once per request.
  • Import, export, invoice and feed time and memory limits apply to the current request or job only.

Removed field parameters

component_data

  • Removed the unused component_data field parameter; remove it from field definitions.
  • It never populated component props automatically. Read values from the field or row props instead, and review custom code that accessed field.component_data.
  • Leaving it in field definitions may cause validation errors because it is no longer a registered field attribute.
  • Button component() data arguments remain supported.

hasOne

  • Removed the hasOne field parameter. Remove |hasOne (or the hasOne entry in array notation) and keep belongsTo.
  • The column and foreign key remain unchanged. The relation now returns Laravel BelongsTo instead of HasOne; review custom code that calls relation-specific methods or checks its class.
  • Leaving hasOne in field definitions may cause validation errors because it is no longer a registered field attribute.
  • Laravel hasOne() and automatic relations to single child models (maximum = 1) remain supported.

ifExists

  • Removed the ifExists field parameter; replace it with hideOnCreate in field definitions.
  • Without the replacement, the field is no longer hidden when creating a record. The replacement keeps the same form visibility behavior; backend validation and saving still apply.

inBackend

  • Removed the inBackend alias; replace it with inAdmin in field definitions, including array notation.
  • The replacement keeps the same admin-only behavior. Leaving inBackend in field definitions may cause validation errors because it is no longer a registered field attribute.

Removed helpers

isActiveController()

  • Removed isActiveController() from resources helpers. Existing calls will fail with an undefined-function error.
  • Replace calls with Laravel’s request()->routeIs() or Route::currentRouteAction().

Admin\Helpers\Helper

  • Removed Admin\Helpers\Helper (isActive(), currentRoute(), controllerName(), link(), error(), priceFormat(), invoiceFormat()). Use request()->routeIs() / Route::currentRouteAction() for the route checks, $errors->first() in Blade and number_format() / str_pad() for the formatting helpers.

laravel/helpers

  • crudadmin/framework no longer requires laravel/helpers, so global helpers like array_wrap(), array_get(), str_slug(), str_random(), str_singular() or studly_case() are gone unless the project requires the package itself. Replace them with Arr:: / Str:: methods, or run composer require laravel/helpers.

Removed Site builder

  • Removed the entire Site builder module: SiteBuilder, block types, Group::builder(), getSitebuilderBlocksArray(), renderBuilder(), the block selector and its styles. Replace block editing and rendering with your own implementation.
  • Remove Admin::isEnabledSitebuilder() calls and the admin:sitebuilder:block command from your project; admin:upgrade:config deletes the sitebuilder config key, remove sitebuilder_types by hand. Custom blocks extending SBType and published Site builder views need replacing too.
  • Existing block data is not deleted automatically, but CrudAdmin no longer edits or renders it. Migrate any content you still need before upgrading.

Public website features moved to crudadmin/website

  • The frontend editor, gettext scripts of Blade pages, language prefixes in urls, SEO and the site tree moved from crudadmin/crudadmin to the new crudadmin/website package. Projects using any of them run composer require crudadmin/website. Config keys (frontend_editor, seo, sitetree, localization.remove_default, storage.allowed_extensions, gettext.json), route names and urls stay the same; their defaults are provided by the package.
  • The $seo model property is part of the package too. Without it, models with $seo (and eshop products and categories) have no meta fields tab and the slug of sluggable models is not editable in the form. admin:migrate then reports the meta_* and slug_dynamic columns as unknown; keep them when you are going to install the package.
  • Moved classes: Admin\Models\RoutesSeo, SiteTree and StaticContent are AdminWebsite\Models\…; Admin\Eloquent\Modules\SeoModule is AdminWebsite\Eloquent\Modules\SeoModule; Admin\Helpers\SEO, SEOService, FrontendEditor, Admin\Helpers\SiteTree\SiteTree, Admin\Helpers\Localization\EditorMode and LocalizationRedirecter are AdminWebsite\Helpers\…; Admin\Core\Casts\EditorCast is AdminWebsite\Casts\EditorCast; Admin\Middleware\LocalizationMiddleware is AdminWebsite\Middleware\LocalizationMiddleware. The EditorMode, FrontendEditor, SEO and SiteTree facade aliases are unchanged. Update project classes extending them, e.g. an own RoutesSeo model.
  • Moved helpers uploadable(), linkable(), localeUrl(), localizedRoutes(), switchLocale() and encryptText(); Blade directives @translates, @gettext, @editor, @uploadable, @seo, @metatags, @title, @description, @keywords, @image, @author and @seogroup; route macros ->seo() and ->visible(), the router macro addLocalizationAttributes() and the localized middleware. Without the package, calls fail and directives are printed as text.
  • Removed Admin::isEnabledFrontendEditor(), Admin::isSeoEnabled() and Admin::isEnabledSitetree(); use AdminWebsite\Features::frontendEditor(), seo() and sitetree().
  • Without the package, website localization no longer reads the language from the first url segment or the session: Localization::get() returns the default language until the application calls Localization::setLocale(). isValidSegment(), segment(), prefix(), saveIntoSession(), getFromSession(), refreshOnSession() and crossDomainSupport() exist only in the package localization. getLocaleSegmentIdentifier() and gettextJsResourcesMethod() were removed from LocalizationInterface; custom localization classes may drop them.
  • editor and longeditor values are wrapped in <div data-crudadmin-editor> on non-admin requests only with the package and an enabled frontend editor (frontend_editor.enabled). Otherwise, also in API responses, the value is returned as it is stored.
  • Slugs in the language the visitor switched from (_previous_locale) are found only with the package. Packages set the resolver with AdminModel::resolvePreviousLocaleUsing(); editor field casts are added with AdminModel::addFieldTypeCast().
  • Clear compiled Blade views after the upgrade (php artisan view:clear); views compiled with the old @gettext directive call the removed Gettext::getJSPlugin().
  • Frontend scripts are built in the package and published to public/vendor/crudadmin-website (FrontendEditor.js, Gettextable.js, frontend.css) by php artisan admin:update or the admin_website.assets tag; admin:update also adds the directory into the project .gitignore, so the built files are not committed. /vendor/crudadmin/build/assets/FrontendEditor.js, Gettextable.js and frontend.css no longer exist; update custom script tags. The administration no longer installs window.action() and window.decryptText().
  • JSTranslations::getJavascript() moved to the package, Gettext::getJSPlugin() became JSTranslations::getScriptUrl() of the package. GET /admin/api/bootstrap no longer accepts context=editor; the editor uses GET /admin/api/frontend-editor/bootstrap.
  • Models no longer receive siteTreeColumns(), scopeOnSiteTreeLoad() and getTreeAction(). Models with $sitetree load their key, the $sitetree column and the slug; declare these methods on the model or use the AdminWebsite\Eloquent\Concerns\HasSiteTree trait. parent::siteTreeColumns() calls fail without the trait.
  • Removed turnOfCacheForAdmin() of the package service provider. It only set admin.cache_time, which nothing read; remove its calls from packages.

Removed admin preview state

  • Removed $publishableState, withTemporaryPublished() and isAdminPublished(). Remove these declarations and calls from project models and code.
  • Publishing now toggles directly between hidden and published, including SiteTree. Former preview rows with published_at = null stay hidden on the website, even for logged administrators; publish them explicitly when ready.
  • published_state is no longer created, cast or read. Review existing preview rows before dropping this obsolete column during migration.
  • For publication checks, use published_at (set and not in the future). For a custom preview, use withUnpublished() in a controller with your own access checks.

Removed $seoVisible

  • Removed $seoVisible and automatic hiding of SEO attributes on frontend requests; remove the property from your models.
  • meta_title, meta_keywords, meta_description, meta_canonical_url, meta_image and slug_dynamic now follow normal model serialization. Use $hidden or makeHidden() if these fields must stay out of array and JSON responses.

Removed columns.*.title

  • Removed translation support for columns.*.title; replace it with columns.*.name in model settings (for example, columns.price.name).
  • title did not change table headers. name sets the column header and remains translatable; a field’s column_name takes precedence.

Removed grid.header

  • Removed grid.header from the feature reference; remove it from model settings if present.
  • The administration never read this key, so removing it does not change the layout or headers.

Removed header.visiblePermanently

  • Removed header.visiblePermanently; remove it from model settings. Single-record forms can no longer force the header to remain visible through this setting, so review any custom header components or actions.
  • The header still appears automatically for localized fields, the gettext editor or an opened record with history. form.header = false still hides it.

Validation rules are built once

  • One Model::validator() instance builds its rules and mutated data once, until only(), merge() or replace() change it. Repeated get(), getData() and fill() calls no longer run the request mutators again, so a file of a validated field is uploaded once and a request changed in the meantime is not read again.
  • Fields are resolved for the validated row only when the model or its modules read it. Models building fields dynamically without the fields($row) parameter should override hasRowDependentFields() and return true.

Renamed keepInRequest to allowInput

  • Replace keepInRequest with allowInput in field definitions, including array notation. The old name is no longer supported.
  • Behavior is unchanged: allowInput accepts submitted values for removeFromForm, invisible and disabled fields on create and update. Validation still applies.
  • Without the replacement, these values are ignored; the obsolete parameter may also cause validation errors.

Replaced settings.keyName with $primaryKey

  • Remove keyName from $settings. The administration now reads the model’s actual key through Eloquent getKeyName(); configure Laravel’s $primaryKey property if your database key is not id.
  • The old setting only changed frontend behavior. Do not move a display-only column into $primaryKey: it changes how Eloquent identifies, updates and deletes records.
  • The model tree now includes primaryKey. Update custom frontend code that read settings.keyName; the frontend getKeyName() method remains available.

Removed $bus

  • Removed the global $bus and useEventHub() APIs. Replace custom listeners with window.addEventListener() and emit CustomEvent events; payloads are available as event.detail. Remove listeners when components unmount.
  • Gutenberg editor switching uses native browser events. Update resources together with the Gutenberg integration; custom code using the old closeMenu or disableGutenbergEditors events must be updated. The sidebar keeps the state of its opened groups itself.

Replaced settings.xls with TableExportXls

  • Remove xls from model settings and add \Admin\Exports\TableExportXls::class to $exports. Install phpoffice/phpspreadsheet if needed.
  • The rows endpoint no longer accepts download to create files. Use the standard export endpoint and its download_url response; replace custom uses of the removed SheetDownloader helper.
  • Table formatting, filters and the setSheet{Column}Attribute() / setExcelSheet() hooks are preserved. Files now use the normal private export storage; empty results produce a valid workbook.

Gettext-only administration translations

  • Removed the resources trans() mixin method, window.trans, useTrans() and layout.localization dictionary. Use literal __('Source message') calls in JavaScript/Vue and _('Source message') in PHP/Blade.
  • Custom admin components and extension packages (including eshop and invoices integrations) must not call trans(), this.trans(), window.trans() or useTrans() in JavaScript/Vue; these APIs no longer exist. Replace keys with literal gettext source messages.
  • Laravel’s PHP trans() helper still exists: calls such as trans('validation.required') use Laravel validation translations and are unaffected by removal of the admin frontend helpers. Use gettext for your own administration UI messages.
  • Removed resources admin::admin.* PHP catalogs. Administration uses the admin gettext catalog. Guest authentication screens use only an allowlist of bundled authentication messages. Move custom private translations into the admin gettext catalog; they are loaded after verification.
  • Field name, title, placeholder and model labels already use gettext. Replace legacy keys such as name:admin::admin.key with literal source text, for example name:Názov. Without migration the old key is displayed as text.

Model and field texts are translated in the administration only

AdminResourcesSyncer::translate() returns the source string outside the administration and the console. Model names, field labels, permission titles and model settings reach the website through relations, components and exports, and translating them there loaded the whole administration catalog for a request that never showed them.
  • A website which displayed a translated $name, a field name or a model setting has to translate it itself. _('text') in the model or the view keeps working, it is the native gettext of the request language.
  • The catalog is read as a plain map of source strings, generated once per .po revision into the crudadmin storage. Deploys which ship a prebuilt storage directory keep working; a read only storage rebuilds the map per request.

Built-in admin components use script setup

  • All built-in administration Vue components now use <script setup> and are closed by default. Custom components can no longer read their state or call their methods through $parent, $refs or $root (for example $parent.isField(), $parent.getGroupModel(), $root.flattenModelsWithChilds(), opened on sidebar rows or runModalCloser on modals). Pass the data through props or read it from the model and the Pinia stores instead.
  • Components rendered through model components still receive model, row and rows as props, and $parent.model, $parent.row and $parent.rows keep working there.
  • The form group component is registered as FormGroup instead of form-group; update custom code that resolved it by that name.
  • License server callbacks no longer run with the component instance as this. They get an object with the same state and methods, but without $-prefixed instance properties.
  • Custom components loaded from resources/views/admin/components keep using the Options API (export default { ... }); <script setup> is not supported there.

Removed $localization

  • Removed the $localization model property (rows stored per language in language_id), the localization() query scope, isEnabledLanguageForeign(), the --localization option of admin:model and the localization key of the model tree. Remove the property from your models. For translated content of one record use locale fields.
  • The administration no longer has the language switch above the table, does not send language_id with row, export or save requests and does not filter relation select options by language. Rows of all languages are listed together, and new rows are stored without language_id.
  • language_id is no longer created by migrations nor fillable. Existing columns and data are kept: admin:migrate reports the column as unknown and asks before dropping it, --auto-drop does not drop it. While it exists, its foreign key still blocks deleting a language used by those rows. Keep it through the replacement below, or merge or delete the per-language rows and drop the column yourself.
  • Replacement: declare language_id as a regular field bound to the languages model and add one filter button per language. Existing language_id columns and data keep working, the column type and foreign key match. Replace Model::localization() calls with where('language_id', ...). Models using HasEntryLocales need the field too.

Admin routes

  • All admin endpoints moved to one url scheme and got route names (admin.*). There are no redirects from the old urls; update custom code which calls them directly.
  • Internal endpoints of the administration live under /admin/api/models/{table}/…: rows, rows/{id}, order, fields/{field}/options, buttons/{button}, exports/{export}, settings and history. Creating a row is POST /admin/api/models/{table}, updating PUT /admin/api/models/{table}/rows/{id}. The model and row are taken from the url, _model and _id in the request body are ignored.
  • Authentication endpoints called by the login form moved to /admin/api/auth/… (login, password/email, password/reset, verification). Browser pages such as /admin/login and /admin/logout are unchanged.
  • Downloads moved to /admin/files/…: /admin/download/file is now /admin/files/{table}/{field}/{file}, /admin/user/download/{hash} is /admin/files/secured/{hash} and /admin/download/signed/{hash} is /admin/files/signed/{hash}/{table}/{field}/{file}. Signed links already sent by e-mail stop working; generate them again with $file->download().
  • The gettext editor moved to /admin/api/translations/{language}/{table?}, the stateless editor link to /admin/translations/editor and admin translations to /admin/translations/admin.js. Switching the admin language is PUT /admin/api/user/language/{id}. /vendor/js/ca-translates.js is unchanged.
  • Frontend editor endpoints moved from /frontend-editor/* and /translates/* to /admin/api/frontend-editor/*. FrontendEditor::routes() was removed; the routes are registered automatically.
  • Statistics are POST /admin/api/statistics/{key}, the site tree is saved by PUT /admin/api/sitetree, the development benchmark is /admin/api/dev/benchmark.
  • The REST API moved to /admin/api/v1/…: /admin/api/model/{table} is now /admin/api/v1/models/{table}, rows are updated by PUT or PATCH instead of POST, /admin/api/models_scheme/{table?} is /admin/api/v1/models/{table}/scheme or /admin/api/v1/scheme, and the helpers auth routes (auth/login, user) moved under the same prefix. Swagger moved from /admin/swagger to /admin/api/v1/docs. Update external API clients.
  • The hasAdminRole middleware reads the model from the {model} route parameter, then from the model input. The _model input is no longer read.

Removed window.crudadmin.layout.requests

  • Removed the requests url map from window.crudadmin.layout and the useRequest() helper. Custom Vue components calling useRequest() fail with an undefined function error.
  • Use the api composables instead: useModelApi(table) (rows(), show(), options(), button(), export(), formUrl(), downloadUrl(), …), useAuthApi(), useTranslationsApi(languageId) and usePanelApi(). Requests made with useAxios() are relative to /admin, so useAxios().$get('/api/…') keeps working for custom endpoints.

Removed model slug alias

  • Removed the slug key from the model tree; it was an alias of table with the same value. Replace model.slug, row.slug and models[key].slug with .table in custom Vue components and JavaScript. getModelBuilder() compares with model.table.
  • Sidebar items now use the data-model attribute instead of data-slug, with the same value (table name, or the group key for menu groups). Update custom CSS, scripts and browser tests that select li[data-slug="…"]. The data-slug attribute of the form language switch is unchanged.

Model loading states

  • Model loading flags are grouped under one loading data key: loading.row (row opening in the form), loading.button (running button action) and loading.gettext (translations loading before the gettext editor opens). Replace model.getData('loadingRow') with model.getData('loading').row and model.getData('button_loading') with model.getData('loading').button in custom Vue components. The old keys are removed without aliases.

JSON bootstrap and PHP helpers 2.0

  • The admin now loads initial data from GET /admin/api/bootstrap. Remove overrides of admin::partials.crudadmin-props; that view no longer exists. Custom admin shells must include an admin-bootstrap meta tag containing route('admin.bootstrap') and initialize window.crudadmin.components.
  • Removed window.crudadmin.layout, window.crudadmin.filemanager, window.crudadmin.logged and window.crudadmin.verified; there are no compatibility getters. Read private configuration through useSettingStore() and session state through useAuthStore() after bootstrap (boot.ready === true). Replace layout.models with useSettingStore().tree (or .models for the flattened map), layout.user with useAuthStore().user, and layout.auth with useAuthStore().config. Component registration through window.crudadmin.components remains supported.
  • The public-page editor fetches its own restricted bootstrap configuration. Publish matching resources assets together with the PHP changes. Login and successful verification now return bootstrap data and navigate without an admin document reload.
  • PHP crudadmin/helpers 2.0 requires CrudAdmin 6 and framework 6.0.1 or the matching 6.0-dev branch. Its BootstrapRequest inherits section composition and cache from the framework; existing project subclasses retain their namespace, client and token handling. Replace pinned 1.4.0 constraints with ^2.0 when upgrading.
  • App store startup flags now live in boot (ready, loading, error, componentsLoaded); replace booted checks with boot.ready === true and isLoaded with boot.componentsLoaded. Read locale and content languages from useLocaleStore() (@crudadmin/helpers/store). Replace admin_languages with useSettingStore().languages, read the selected interface language from the locally extended useLocaleStore().current getter, and read gettext from settingStore.editor.gettext. The temporary appStore.localization group is removed, and model_settings is now settingStore.editor.available, set by crudadmin/admin-editor. Update custom components reading the old top-level fields.
  • Admin\Core\Bootstrap\BootstrapRequest (framework): a cache array of a section reads duration as an alias of minutage. Projects which used duration got the default 60 minutes until now and get their configured minutes now. Cache keys of a section get a .v{n} suffix after the first forgetCache($section); nothing changes before it.
  • A guest requesting authenticated through only() gets nothing (it was computed before). A guest requesting directly a section which only an overridden authenticated() composes (not get() or guest()) gets a 403, like a section of the $authenticated property; before it was computed without a client. Sections composed by get(), guest() or another loaded section are not affected.
  • The framework BootstrapRequest declares protected $baseSections and protected $sections (opt-in whitelist, null by default). A subclass declaring a private property of the same name must rename it.
  • The admin-specific bootstrap request and controller live in crudadmin/crudadmin (Admin\Bootstrap\AdminBootstrapRequest, Admin\Http\Controllers\BootstrapController). The reusable Admin\Core\Bootstrap\BootstrapRequest remains in crudadmin/framework.
  • CKEditor receives filebrowser URLs directly in its instance configuration. Custom editor initializers must supply those options from useSettingStore().filemanager inside the admin or CAEditor.config.filemanager after public-page editor bootstrap. Republish the matching CKEditor config.js; the window.crudadmin.ckeditorConfig(config) customization hook remains supported.
  • Authentication form configuration is grouped under useAuthStore().config.form: column, input_type, title, placeholder, password_reset and flashed errors. Update custom login/reset views; provider selection remains under config.
  • app now contains public startup/CSRF state and logo. Move reads of models/tree, versions, environment, author/copyright, paths, filemanager, statistics, dashboard, license and editor settings to useSettingStore(). The setting bootstrap section is forbidden until authentication and 2FA are complete; session loss resets private stores.
  • Pinia now persists private settings, the last verified identity, locale and logo per bootstrap URL, including in development. A complete cache renders before background session verification; stale permissions or a previous session can remain visible until the response arrives. Every request remains authorized by the server. Logout/session loss clears the cache; CSRF tokens and boot flags are never persisted. Custom shells should add admin-app-hash with Admin::getAppHash() only when (new Admin\Bootstrap\AdminBootstrapRequest)->isAuthorized(); the cache is used only when it was stored for that hash, so a shell without it, or with a changed hash, always waits for a fresh bootstrap.
  • Login and verification responses now contain store; custom auth flows must await useBootstrap().applyBootstrap(response) before entering private routes. The fresh CSRF token is in store.app.csrf_token. JSON logout returns the public bootstrap. Redirects outside the admin still leave the document.
  • Project scripts/styles and meta/scripts slots now load after private bootstrap. Register components immediately when a script executes instead of relying solely on window.load; make session initialization idempotent. The guest shell uses a generic title; the login logo remains public through app.logo. Other project assets load only after verification.
  • Admin translations now arrive as store.locale.translations with bootstrap/login/logout responses. Read useLocaleStore().translations instead of window.CATranslates; remove custom loading of the admin translation script. Guest and pending-2FA catalogs contain only bundled authentication messages. The public-page editor keeps its separate translation script.
  • The admin installs the shared CrudadminVue translation plugin from @crudadmin/helpers; use matching helpers with reactive catalog replacement. window.CATranslator and window.GettextTranslates are no longer installed inside the admin. Import Translator from @crudadmin/helpers for a separate catalog; use its getTranslator() for gettext methods. Vue translation methods and the global __/n__ helpers remain available.

SmartSMS moved to crudadmin/helpers

  • Admin\Helpers\SmartSms moved to AdminHelpers\Sms\SmartSms in the crudadmin/helpers package. Update imports in your code. The smartsms config and the SMARTSMS_* environment variables are unchanged.
  • Admin\Notifications\SmartSMSChannel is removed. crudadmin/helpers registers the notification channel sms (AdminHelpers\Sms\SmartSmsChannel), which sends toSms() of a notification to the phone of the notifiable, or to routeNotificationForSms().
  • The SMS login verification sends its code through the sms channel. Without crudadmin/helpers, register your own sms channel with Notification::extend('sms', ...), otherwise the code is not sent.

Removed MAIL_DEV_WHITELIST

  • Removed the CheckDevEmailWhitelist mail listener and the MAIL_DEV_WHITELIST environment variable. Since Laravel 9 it stopped every e-mail once the variable was set. Use Mail::alwaysTo() in a service provider of your development environment, or a local mail catcher.
  • admin:encrypt-existing writes encrypted values straight into the table and no longer saves the rows through the model, so model events, rules and history are not triggered and updated_at is kept. New --dry-run, --model and --chunk options.

REST API moved to crudadmin/api

  • The REST API (/admin/api/v1/…), its OpenAPI description and the Swagger UI moved to the optional crudadmin/api package. Projects using them run composer require crudadmin/api. URLs and route names of the token endpoints are unchanged; the api.logging config default comes from the package.
  • Moved classes: Admin\Controllers\Api\ApiController is AdminApi\Controllers\ApiController. The HasAdminApi trait is removed from AdminModel: getAdminApiColumns(), getAdminApiRelations(), getAdminApiFieldType() and getAdminApiFieldName() are AdminApi\Schema\ApiSchema::columns(), relations(), fieldType() and fieldName() with the model as the first argument; the bootAdminApiResponse() scope is app(AdminApi\Formats\Format::class)->query($model, $query, $request); setFullAdminApiResponse() is AdminApi\Response\ApiResponse::row($row). The model hooks scopeWithAdminApiResponse() and setAdminApiResponse() keep working.
  • The API now reads and writes through the same code as the administration (Admin\Crud\RowReader, Admin\Crud\RowWriter). scopeAdminRows() is applied, so rows hidden in the administration are not listed, shown, updated or deleted through the API. Validation, request mutators, uploads, belongsToMany sync, history, onCreate/onUpdate and admin rules run as in the administration; create no longer uses $model->validator(). Update validates and saves only the sent fillable fields, a request without them returns the row unchanged.
  • Responses follow Laravel API Resources: lists are { data, links, meta } instead of { error, data: { pagination } }, one row is { data } instead of { data: { row } }, create answers 201, delete answers 204 without body, /admin/api/v1/models returns { data: [{ table, name, relations, operations }] }, and login and /user return { data: { user, token } }. Errors are { message } (validation { message, errors }) with 400, 401, 403, 404 or 422 instead of the type, title and error keys of autoAjax.
  • Query parameters follow spatie/laravel-query-builder: _with/with is include=author,comments.author (relation:columns is fields[table]=columns), _columns/columns is fields[table]=columns, _where[column,operator] is filter[column]=>=10, _where[column,in] is filter[column]=a,b, _where[column,notnull] is filter[column]=!null, _scope[name]=value is filter[name]=value, _selector is selector. limit is per_page (up to admin.api.max_per_page, 100); limit=-1 for all rows is removed, iterate the pages. New: sort, filter[column]=~text, include=relationCount. Unknown filters, sorts, includes and fields answer 400 instead of 422.
  • Relation names in include and in ApiSchema::relations() are camelCase (schemaApiComments instead of SchemaApiComments). Included relations are limited by scopeAdminRows() of the related model and need its read permission. Relation methods which are not fields, child or parent models (accepted by with before) have to be listed in the $apiRelations property of the model.
  • Only API columns and the existing timestamps are returned. Password fields, inaccessible fields, $hidden attributes and table columns which are not fields (e.g. remember_token, logout_date, deleted_at) are no longer returned, selected, sorted or filtered.
  • Tokens issued by POST /admin/api/v1/auth/login (also OTP and socialite login) are read only (api, api:read); clients which write rows have to send access=write on login (adds api:write). They are valid only for the REST API; the administration answers 403 to them. Clients which used a REST API token for admin endpoints need a token with the admin (or *) ability. Existing * tokens keep working everywhere.
  • /admin/api/v1/models lists only models with the read permission. The login credentials are documented in the request body of the OpenAPI description instead of query parameters.
  • The stateless frontend editor token (/admin/translations/editor) has only the frontend-editor ability, it is refused by the administration and the REST API.
  • Passwords, tokens and secrets are left out of the REST API request log.
  • The crudadmin driver of crudadmin/socialite reads the signed in administrator from /admin/api/v1/user instead of /admin/api/user, so the CrudAdmin which acts as the OAuth server needs crudadmin/api. Servers which serve the user elsewhere set user_path in services.crudadmin.
  • The session Swagger scheme moved from /admin/api/v1/openapi.json|yaml to /admin/api/v1/docs/openapi.json|yaml; /admin/api/v1/openapi.json|yaml is now a token route for API clients. The scheme is generated in PHP: /admin/api/v1/scheme returns valid YAML with quoted values, and the description now includes the DELETE operation.
  • Renamed Admin\Controllers\Crud\Concerns\CRUDRelations to Admin\Crud\Concerns\SyncsBelongsToMany; admin rules reading pivot data of a belongsToMany field (getPivotData()) use the new trait. Removed the validation and insert methods of CRUDController, InsertController and UpdateController; they live in Admin\Crud\RowWriter. UpdateController no longer extends InsertController. getModel() of the CRUD controllers comes from Admin\Crud\Concerns\ResolvesAdminModels.

Login security

  • The login verification code (sms / e-mail) is invalidated after 5 wrong attempts (verificatorMaxAttempts() of the auth model); a new code is sent when the verification state is requested again. Codes are generated with random_int(). GET /admin/verificator is throttled like the json verification endpoint.
  • The admin hasher respects the hashing.bcrypt config.
  • Frontend editor writes of the session editor (/admin/api/frontend-editor/*) require a verified login and respect remote logout, as the admin panel.

Minimum requirements

  • CrudAdmin 6 requires PHP 8.3 or newer, Laravel 12 or 13 and MySQL 8.0 or newer. It is tested on PHP 8.5. Laravel 11 and older are no longer supported; the Doctrine DBAL fallback and the MySQL 5.7 check of the migrations are removed.
  • crudadmin/crudadmin requires laravel/sanctum 4.
  • published_at is always cast to datetime, also on models that still declare the $dates property, which Laravel ignores since version 10.
  • laravel/ui is required by crudadmin/resources for the administration login and password reset. Its auth scaffolding (php artisan ui) is not used by CrudAdmin.

PHP 8.5

  • PHP 8.5 deprecates the driver-specific PDO::MYSQL_ATTR_* constants. Every project with the default Laravel config/database.php reports Constant PDO::MYSQL_ATTR_SSL_CA is deprecated on each request. Replace the key in the options of the mysql and mariadb connections:
config/database.php
  • The condition keeps the config working on PHP 8.3 and 8.4, where Pdo\Mysql does not exist. Replace other PDO::MYSQL_ATTR_* constants the same way.

Model configuration properties

PHP 8.5 lets a class read a protected property redeclared in a sibling class. Every admin model redeclares $name, $title, $icon, $active and more, so in a model method, model trait or closure inside a model, $city->name of another model returned the module name (Cities) instead of the column. PHP 8.3 and 8.4 returned the column. CrudAdmin 6 moves configuration properties that share a name with a value of the row (a field, an accessor or a relation, and always $name and $title) out of the model once it is constructed. $row->name returns the column on every PHP version, also inside the model itself.
  • Read the model configuration only with $this->getProperty('name') and change it with $this->setProperty('name', $value). $this->name in a model now returns the column, before it returned the property.
  • An assignment $this->name = ... after the model is constructed sets the attribute and is saved into the database. Assignments in the constructor before parent::__construct() still set the configuration.
  • Eloquent properties ($table, $hidden, $visible, $fillable, $casts, $with, $connection…) stay regular properties. A column with such name is read as the property inside models. Rename the column, or read it with getAttribute().

Fields and the logged administrator

  • Fields are cached the same for everybody, in the process and in php artisan admin:cache. Permission parameters (hasAccess, hasNotAccess) and inAdmin are applied on top of them only in the administration and the REST API, once per request after the administrator is authenticated. Previously they were applied everywhere and the compiled cache stored them resolved as for a guest.
  • Outside the administration (frontend, console, migrations) permission parameters and inAdmin are ignored. hasNotAccess no longer applies its parameters on the frontend, e.g. hasNotAccess:update,invisible does not remove the field from Model::validator() anymore.
  • Administration requests no longer rebuild fields of all models. Rebuild them with $model->getFields(null, true) only if they depend on something else than the administrator, e.g. the session.
  • Removed field parameters inFrontend and inConsole. Add frontend rules directly into the validation of your frontend request, and console only parameters into the field definition. inAdmin stays.
  • Avoid admin() and admin()->hasAdminAccess() in model definitions (fields(), groups, mutateFields()). Use the rules hasFullAccess, hasNotFullAccess, hasAccess and hasNotAccess on fields and on group attributes (Group::attributes(), Group::add()) instead, e.g. (admin()?->hasAdminAccess() ? '' : '|hideFromForm') becomes |hasNotFullAccess:hideFromForm and ->attributes($isAdmin ? '' : 'removeField') becomes ->attributes('hasNotFullAccess:removeField'). New rules hasFullAccess and hasNotFullAccess apply parameters for super administrators or for everybody else.
  • Rules only add parameters. A parameter which was turned off for super administrators ('hidden' => $isAdmin ? false : true inside a hidden group) is replaced by an opposite parameter, e.g. hasFullAccess:column_visible.
  • Models whose fields() still call admin() are detected and built again for the authenticated administrator in every administration request; the compiled cache holds them as without the administrator. The administrator read by auth()->user(), request()->user() or own helpers is not detected, use admin() or permission parameters.
  • admin() returns null while fields are cached: when the relations tree and the compiled cache are built and while a model boots.
  • Permission parameters must not add relations (belongsTo, belongsToMany). Relations are built from fields without the administrator.
  • The compiled cache format changed, run php artisan admin:cache after the upgrade. Caches of the previous format are ignored.
  • Custom field mutations depending on the administrator implement Admin\Core\Fields\Mutations\RuntimeMutation (runtime($field, $key, $model)). They are skipped when fields are built and applied in the administration to fields with one of their $attributes.

Removed legacy classes and methods

  • Removed Admin\Helpers\Ajax and its Ajax alias (CrudAdmin 3). Use autoAjax()->success(), ->error(), ->message() and ->throw().
  • Removed Admin\Models\Model (CrudAdmin 1). Extend Admin\Eloquent\AdminModel.
  • Removed Admin\Helpers\File and Admin\Core\Helpers\File. Use Admin\Core\Storage\AdminFile, which has the same methods.
  • Removed Admin\Eloquent\Casts\DecimalCast. CrudAdmin never applied it to any field; copy it into the project if a model uses it in $casts.
  • Removed unused model methods: filePath() (use getStorageFilePath() and getFieldStorage()->path()), scopeFilterByParentField() and checkForChildrenModels() (the HasChildrens trait).
  • Removed hasAccessByTable($table, $permission) of the admin user. Use hasAccess(Admin::getModelByTable($table), $permission).
  • Removed Button::errorToast($message). Use toast($message, 'error').
  • Role permissions are read only from the JSON cast. Permissions saved as plain strings by CrudAdmin 3 and 4.1 are no longer decoded; resave the roles in the administration.
  • date values stored in the d.m.Y format are no longer read; the value is null. Convert such columns to Y-m-d. Writing d.m.Y strings from your code still works.
  • With a symlinked cache folder, old /uploads/cache/… image URLs no longer redirect to /cache/…. Update hardcoded image URLs.

Renamed upload properties

  • $delete_files is renamed to $deleteFiles.
  • $imageLossyCompression, $imageMaximumProportions and $imageLosslessCompression are replaced by one property $imageProcessing with the keys lossy, resize and lossless. Declare only the keys you change, the others keep their defaults:

Internal model methods are private

Methods of AdminModel used only by CrudAdmin itself are private or protected. Calling them from outside the model ends with BadMethodCallException from the query builder, because Eloquent forwards unknown calls there.
  • Now protected, override them in the model as before: hasRowHistory(), hasGettextSupport(), defaultModelPermissions(), getUserPermissions(), addModule(), addSkipDroppingColumn(), cachableFieldsProperties(), withMultiCast(), getFieldsGeneration(), newInstanceWithoutConstructor(), canPermanentlyDeleteFiles(), isAllowedHistorySlugs(), generateEncryptedHash(), getComponentPaths(), hasAutoLogoutSupport(), getLogoutSessionKey(), getFullAccessMessage(), the login verificator sendVerificatorCode(), generateVerificationCode() and verificatorMaxAttempts(), and AdminRule::isFieldDirty().
  • Now private, no longer available in models: initTrait(), flattenGroups(), makeFillable(), makeDateable(), makeSingle(), removeHidden(), removeVisible(), removeAppends(), buildBaseFields(), bootAdminModules(), bootCachableProperties(), bootRelationships(), getModules(), getModulesWithMethod(), getFieldsByRow(), refreshFields(), withoutOptions(), getCachedRelationsTree(), toAdminArray(), getHistoryRows(), castHistoryData(), removeWithRelations(), isRuleSilent() and the internal helpers of casts, slugs, rules and the replicator.
  • Removed unused methods: getFieldsWithOptions(), getBaseModelTable(), returnRelationItems() and the old relation resolver (returnAdminRelationship(), relationResponse(), isAdminRelationLoaded(), getRelationFromCache()). Relations are resolved by bootRelationships() since CrudAdmin 5.
  • Removed AdminModel::$adminBooted. $globalPublishable and $globalModelPublishable are private, use setGlobalPublishable() and setGlobalModelPublishable(). $callableProperties and $localizedResponseLocalArray are private. AdminModelModule::$model is protected, use getModel().

Reserved column names

admin:migrate reports fields named like a property of the model, for example table, visible, hidden, casts or attributes. Eloquent returns the property instead of the value of the row, so such a column is unreadable inside the model and, since PHP 8.5, also in other admin models.
  • A new field with such a name stops the migration. Rename the column.
  • A column of an already migrated table is only reported, projects keep working.
  • Keep the name with protected $ignoredReservedColumns = ['table']; on the model and read the value with getAttribute('table').

Models without a migration date

An AdminModel descendant without $migration_date was skipped silently. Every instantiable descendant is registered now, so a class which is not meant to be a module has to say so.
  • A shared parent of admin models must be abstract. Non instantiable classes are never registered.
  • A class which is not a menu item by its nature implements Admin\Core\Eloquent\Concerns\NotAdminModule. The interface is inherited, so it covers the whole subtree. AdminPivot implements it already, its descendants need no change.
  • A class of such a subtree which is a module anyway, for example a pivot with its own fields or menu item, implements Admin\Core\Eloquent\Concerns\AdminModule. A remaining $migration_date still keeps it registered until the upgrade replaces it.
  • Any other class without a date is an ordinary module. It is placed in the menu by its $group until the navigation section lists it.
  • A model extending a registered admin model over the same table replaces it, also under another class name (a project Notification extending AppNotification of crudadmin/helpers). v5 did the same through the shared $migration_date; the parent is not a module of its own then. A child with its own table (a log extending the model it logs) and a model implementing Admin\Core\Eloquent\Concerns\AdminModelReplica (another page over the table of its parent) do not replace the parent, both stay registered.
The menu is declared by the navigation section of bootstrap/admin.php, a tree of model basenames and #groups with their name and icon. The groups config key and the $migration_date ordering are replaced by it.
bootstrap/admin.php
  • php artisan admin:upgrade:navigation captures the menu CrudAdmin 5 renders, before admin:upgrade:dates removes the dates which order it. It moves every group of groups into the section with its name in the source language and its icon, including groups without a model, removes the groups key from config/admin.php, removes a literal protected $group from the app/ models the section places (a group() method stays) and writes the order of child models into their parent’s childs setting. Models switched off with $active = false are not captured. A model whose group() needs the logged administrator is reported and keeps being placed at runtime. Run it once and commit the files; --recapture captures again over an existing section.
  • admin.groups is reported by the config check like the other changed keys; its value keeps working until the step moves it. Packages still merge their groups into config('admin.groups'), they are used for groups the section does not name.
  • A model the section does not list is placed by $group at the end of that group, so $group stays the default placement of new models and of package models. A project without the section renders the CrudAdmin 5 menu.
  • The order of the models set follows the section; models_order of the development line is no longer read and is dropped by the next write of the file. Children of a model are ordered by its childs setting, then by the models set.
  • getModelGroupsTree() was removed from admin models. Read the menu from AdminTree::get() or Admin\Navigation\Navigation.
  • The sidebar was rewritten: SidebarRow.vue is replaced by SidebarMenu, SidebarItem, SidebarGroup and SidebarModel, and the crudadmin:close-sidebar-menu browser event no longer exists. Classes (sidebar-menu, treeview, treeview-list, treeview-menu, active) and the data-model attribute are unchanged.
  • With crudadmin/admin-editor, Upraviť menu in the Editor mode dropdown (or the pencil of the sidebar) edits the section in a modal: drag models and groups, create groups, rename groups and models, change their icons. Renaming a model rewrites protected $name in its source file.

$icon replaced by the icon setting

  • $icon and an icon() method are no longer read. The icon of a model is the icon setting: declare it in $settings or return it from settings(), bootstrap/admin.php overrides it like any other setting. The model tree still sends it to the Vue app as icon.
  • models.<Basename>.name in bootstrap/admin.php still overrides $name, e.g. a renamed model of a package; a name() method is not overridden. It is a property of the model, not a setting.
  • php artisan admin:upgrade:icons moves a literal protected $icon of the models of app/ into models.<Basename>.icon of the file and removes it from the model; an empty $icon (null, '') is only removed. An icon() method and a computed $icon are reported, move them into settings() by hand. Models of packages declare icon in their own settings. admin:upgrade runs the step after admin:upgrade:settings.
  • getProperty('icon') returns nothing any more, read getModelIcon() of the model.

$migration_date is gone

The models set is keyed by class name and ordered by the administration, not by a date declared on every model.
  • php artisan admin:upgrade:dates removes the property. Run it as the last upgrade step, after admin:upgrade:navigation, which captures the order first; it refuses to run without the navigation section. The section names models by their class basename, so moving a model to another namespace keeps its position.
  • php artisan admin:model no longer writes $migration_date into new models.
  • Two models with the same date are no longer a conflict, and a model without one is an ordinary module.
  • A NotAdminModule model was registered only by its date. The command adds implements AdminModule with its import before it removes the date, so the model stays registered. A model outside app/ or with an inherited date keeps the date and is reported.
  • Migration order no longer depends on the date: foreign keys are added after every table exists.

Table sorting runs in the database

  • A click on a column header, the field orderBy parameter and columns.*.sort_by now sort all records in the database and load the first page again. Before, only the loaded page was sorted in the browser, and the pages kept the order of $orderBy.
  • belongsTo, select and radio columns are sorted by their labels, empty values come last. Rows mutated by setAdminRowsAttributes are sorted by their stored value, not by the displayed one; sort such a column with set{Column}AdminSort or columns.*.sortable => false.
  • Virtual columns, belongsToMany, multiple, encrypted and json fields are still sorted in the browser within the loaded page, the header says so.
  • scopeAdminRows() orders follow the chosen column. AdminRows::getRowsDataQuery() applies the order request parameter, exports of the table follow it too. A column named like a value the query selects (withCount, withSum, an alias) is sorted by that alias; code calling count() on that query has to drop the order first (reorder()).
  • The chosen sorting is remembered in the browser per table. Frontend code reading getRowsSorted() gets the rows of the database order unchanged when the database sorted them.

Editing in the table

  • A column_editable cell is no longer an input all the time. Cells show their values, a cell switches to its field by the pencil shown on its hover and the whole column by the pencil of its header, so long tables render without a form input in every row.
  • Every column of a field editable in the form can be switched now, not only column_editable ones. column_editable keeps the pencil of the header visible; turn a column off with column_editable:false or the columns.{key}.editable => false setting. Columns of readonly, disabled, removeFromForm, inaccessible and invisible fields, columns with a column component, editors, json, file and radio fields, fields with a form component or sub_component and multiple dates are never switched.
  • A click on a cell of a column_editable column opens the record like any other cell, unless the cell is switched to its field.

Indexes of columns turning into JSON

  • admin:migrate drops every index (plain, unique, fulltext) containing a column whose type changes to JSON, before the column is changed. This happens when a field becomes locale, multiple or type:json, and for CrudAdmin 5 locale fields still stored as varchar/text columns with JSON values (e.g. products.name with a name index and the full fulltext index). MySQL can not index a JSON column, the migration failed on modify ... json before.
  • The dropped indexes are not recreated. A fulltext index whose other columns stay non JSON is rebuilt by the fulltext step from the fields which still have fulltext. Search on a localized column has to use another way (e.g. a generated column of one language).

Installation and migration output

  • admin:install runs migrate before admin:migrate: a fresh Laravel 11+ project stores the cache and sessions in the database (cache table) and failed. The Laravel users migration is removed only for an administrator model stored in users (2014_10_12_000000_create_users_table.php); 0001_01_01_000000_create_users_table.php (also password_reset_tokens and sessions) stays.
  • admin:migrate lists a table as updated only when something is reported for it (added, unknown or dropped column…), -v lists every table. Scripts parsing “Updated table:” lines need -v.
  • Localization::getJson() returns '{}' without gettext (admin.gettext.enabled not true) or for an unknown locale; it failed on a missing language model before.