Upgrade Information
The following steps are necessary during updating to newer versions.
Upgrade to 2026.4.0
- [Elements] Deprecated:
coauthorTypeandcoauthorin the bodies of the element patch and update endpoints and ofPUT /pimcore-studio/api/versions/{id}. They still work, are markeddeprecatedin the OpenAPI schema and raise a deprecation notice. They are removed in 2027.1 (https://github.com/pimcore/platform-version/issues/814). The coauthor is set by the server. - [Authentication] Deprecated: static MCP personal access tokens (
pimcore_studio_backend.mcp.authentication.tokens, handled byPatAuthenticator). They keep working on 2026.x; configuring them and each request they authenticate raise a deprecation. They are removed in 2027.1. Migrate integrations to MCP access tokens issued for a dedicated Pimcore user (McpAccessTokenServiceInterface::issue()), and people to OAuthauthorization_code. See MCP Server. - [Service Users] Added: machine identities, a Pimcore user of type
serviceuser(aPimcore\Model\UserwhoseisServiceUser()is true), managed through the new "Service User Management" endpoints and the console commandstudio-backend-bundle:service-user:mcp-token. Everything is additive: no existing endpoint, schema or user type changes. The service-user endpoints need a core release that providesUser::newServiceUser()(pimcore/pimcore#19692). See Service Users. - [Service Users] Semantic notes, for code that works with users:
- A service user never logs in with a password. Setting one or setting it as an administrator is refused on the
core class; every save stores an unusable random value that no password verifies against (as users created
through OpenID Connect have), so
Authentication::isValidUser()treats it like any user. It is never an administrator, has no two-factor authentication and cannot log in to Studio. Itsemailis an optional contact address for the team responsible. Logging in and password recovery do not use it. - Identity kinds never mix.
User::getByName(),User\Listingand the user endpoints return humans only: the user tree and lists leave service users out, and the endpoints that read or change one user by id (detail, update, password, delete, login link, two-factor reset, object dependencies) answer404for a service-user id. Only the user image is served for any id, as authors are shown by id. A service user is reached through the service-user endpoints, and its name is unique across humans and service users. Nothing converts one kind into the other: creating a service user from a human copies permissions, roles and workspaces and leaves the human unchanged. User::getById()returns theUserfor a service-user id as for any user id, withisServiceUser()true. Code that assumes an id always names a human must callisServiceUser()first.
- A service user never logs in with a password. Setting one or setting it as an administrator is refused on the
core class; every save stores an unusable random value that no password verifies against (as users created
through OpenID Connect have), so
- [Service Users] MCP server sharing: a service user's entry in
access.shared_usersis stored withcanReadandcanEditfalse, whatever the client sent;canAccessis kept as sent. See MCP Server Management. - [Service Users] Added: the service-user schema carries
responsibleUsersandresponsibleRoles(lists of ids, the people and the roles who answer for the service user), andPOST /service-userandPUT /service-user/{id}accept both as optional lists. On create a missing list means none; on update a missing (ornull) list keeps the stored values and an empty list clears them. An unknown user or role id answers404; a service-user id inresponsibleUsersanswers422. Needspimcore/pimcorewithUser::getResponsibleUsers()andgetResponsibleRoles(). Additive; no endpoint or permission changes. - [Service Users] Added: the service-user schema (
GET /pimcore-studio/api/service-usersand/service-user/{id}, and the responses that return it) carriesclientCredentialsEnabled(whether the OAuthclient_credentialsgrant is on) andmcpTokens(active,latestExpiresAt; a summary of the MCP access tokens, read with one grouped query for the whole collection, as are the client ids). Additive; no endpoint, permission or token lifetime changes. - [Service Users] Changed:
clientSecretis nullable in the service-user credentials response (create, create from a user, rotate secret). It isnullwhilepimcore_studio_backend.oauth.client_credentials.enabledis off; the key is still present. See Service Users. - [OAuth] Added: the Client Credentials grant for clients bound to a service user, behind
pimcore_studio_backend.oauth.client_credentials.enabled(defaultfalse). Its tokens lastoauth.client_credentials.access_token_ttlseconds (default 900, minimum 60) and carry no refresh token. Nothing changes until the switch is turned on. The guarantee that every token acts for a logged-in human no longer holds once it is on. See OAuth Server. - [Elements] Changed: the
422response of a failed element validation (PUT /pimcore-studio/api/assets/{id},.../data-objects/{id},.../documents/{id}and the synchronousPOST .../assets/add/{parentId}andPOST .../assets/{id}/replace) now carriesvalidationErrorsnext tomessageanderrorKey, one entry per failed field withfield,fieldTitle,path,message,messageKeyandparameters.messageanderrorKeyare unchanged. A client that translates the errors needspimcore/pimcore^2026.4(StructuredValidationException). The synchronous asset upload and replace answer422instead of500when the validation of the asset fails. An error of a data object in a language the user may not view is reduced to the generic messageThe value is not valid., itsmessageKeyand emptyparameters; the top-levelmessageis thenValidation failed.messageis untrusted text and must be escaped before it is rendered. - [Authorization] Added:
GET /pimcore-studio/api/sessiontells whether the request carries a Studio session ({"authenticated": true|false}, plus the two-factor step of a login that waits for its code). It always answers 200 and reveals only the state of the caller's own session. With the matching Studio UI the login page no longer shows a faileduser/current-user-informationrequest. The bundle opens the route itself with aPUBLIC_ACCESSrule for<url_prefix>/session, put in front of the application'ssecurity.access_controlrules when the container is compiled:config/packages/security.yamlneeds no change, and this works with a customurl_prefixas well. The rule has noips,hostorchannelrestriction, so an IP or https restriction of the application does not apply to this one route.user/current-user-informationkeeps answering 401 without a session. - [Assets] Added: the maximum size of a text asset that Studio loads for preview and editing (2 MB, HTTP 413 above)
is configurable with
pimcore_studio_backend.asset_text_settings.max_file_size. The default is unchanged. TheTextEncodergot the optional constructor argument$maxFileSize. - [Data Objects] Changed: the version detail (
GET /pimcore-studio/api/versions/{id}) of a data object shows the values of calculated fields the version stores whenpimcore.objects.versions.calculated_value_snapshotis enabled in Pimcore 2026.4+; the edit view keeps showing freshly computed values.FieldContextData(@internal) got the constructor argumenthistoricalVersionandisHistoricalVersion();DataService::setObjectDetailData()passes it for aDataObjectVersion, and the localized fields adapter forwards it for the localized fields of the object itself. A customDetailDataInterfaceadapter that computes values can use it the same way. A version that stores no value for a field (created before the option, auto-save, field of an object brick or field collection) is shown the way the edit view shows it, as before. The new@internalCalculatedValueSnapshotServiceInterfacereads the stored values; the bundle now requirespimcore/pimcore^2026.4. - [Grid] Changed:
twigOperatortemplates render in a dedicated Twig environment with the sandbox always enabled and without Pimcore's Twig extensions or the application's Twig configuration. Method calls and property access on objects are denied. Values are converted to plain data first: dates become ISO 8601 strings, consent values,JsonSerializableobjects and enums become their data, other objects render as empty.range()returns at most 1000 elements (best effort). Seedoc/01_Architecture_Overview/01_Grid.md.
Note:
SandboxExtensionInitializerimplements the newTwigOperatorEnvironmentProviderInterface. A customSandboxExtensionInitializerInterfaceimplementation or decorator should implement it too: without it, templates keep rendering through the sharedtwigservice with a deprecation, and fail if the returned sandbox is not registered there.SandboxExtensionInitializer::initialize()returns the isolated environment's sandbox, which is not registered on the sharedtwigservice; render throughTemplateGeneratorInterfaceinstead. The initializer's$blockedClasses,$allowedClassesand$hardBlockedMethodsarguments no longer apply, since all object access is denied. To add a filter, function or tag, tag a Twig extension withpimcore_studio_backend.twig_operator_extensionand add its name tosandbox_security_policy.
-
[Grid] Added: asset and data object grid rows carry an optional
score(the search engine score of the hit,nullwithout a scored query). TheAssetandDataObjectresponse schemas implement the new publicScoreAwareInterface(getScore()/setScore()); subclasses that already declare these methods must match the new signatures. -
[Grid] Changed: the data object
available-columnsresponse (GET /pimcore-studio/api/data-object/grid/available-columns) now reports relation (manyToOneRelation,manyToManyRelation,manyToManyObjectRelation,advancedManyToManyRelation,advancedManyToManyObjectRelation),image,imageGallery,geopointandquantityValuecolumns asfilterable: true; they werefalse. These fields can now be added in the listing's filter panel. Relations and quantity values show a value filter that already existed but was never reachable; image, image gallery and geo point fields can only be searched for "no value" or "any value" with the newoperatorof a column filter (seedoc/01_Architecture_Overview/01_Grid.md). This is additive and intended, but an API client that treatedfilterable: falseas "never filterable" will see a difference for these fields. -
[OpenAPI] Improved:
zircote/swagger-php6.x is now supported (^5.0 || ^6.0); the previous>=5.6conflict was removed. The generated Studio OpenAPI document is unchanged.
Note: since swagger-php 5.6 an explicit
type:orref:on a#[Property]attribute no longer inherits the nullability of the PHP parameter it annotates. A property such as#[Property(type: 'string')] private ?string $titleis emitted as"type": "string"instead of"type": ["string", "null"]once an installation resolves swagger-php >= 5.6. All Studio schemas now declarenullable: trueexplicitly. Bundles that register their ownopen_api_scan_pathsmust do the same for every PHP-nullable (ormixed) parameter whose attribute setstype:orref:, otherwise their schemas silently losenullin the generated document and in clients generated from it. Properties without an explicittype:are not affected. The staticOpenApi\Generator::scan()was removed in swagger-php 6.0;OpenApiServicenow uses(new Generator())->generate().
- [Recycle Bin] Changed: restoring an element whose parent no longer exists puts it into a
/__restoredfolder of its element type at the root, created on demand, instead of failing. A taken key gets a number (_1,_2, ...). - [Security] Added: two-factor authentication for the Studio login (authenticator app codes). See
Two-Factor Authentication.
- New configuration:
pimcore_studio_backend.two_factor_authentication.issuer(defaultPimcore) andserver_name(default: the main domainpimcore.general.domainif set, otherwise no host). - New rate limiter
studio_two_factor_code(5 wrong codes per user in 5 minutes). - New endpoints:
POST /login/2fa,POST /user/two-factor/setup,POST /user/two-factor/confirm,DELETE /user/two-factor,DELETE /user/{id}/two-factor. No change toaccess_controlis needed.
- New configuration:
Note:
POST /loginchanges for users with two-factor authentication required: it answers200with{"twoFactorRequired": true, "twoFactorStep": "verify"|"setup", "digits": 6}instead of an empty body, and the user is not logged in until the code is sent toPOST /login/2fa. Clients that treat any200fromPOST /loginas logged in break for these users only; users without two-factor authentication get the same empty200as before. Users who haverequiredset but no authenticator app yet can no longer use Studio with the password alone: they set it up during the login. The login token (POST /login/token) still skips the code. While a code is pending, other endpoints answer401with the sametwoFactorRequired,twoFactorStepanddigits, e.g. for a client returning from an OpenID Connect (SSO) login.
Upgrade to 2026.3.5
- [Data Objects] Fixed:
POST /data-objects/select-optionsresolves the keys of a classification store, so select and multiselect keys with an options provider load their options. They are addressed as<storeFieldName>.<groupId>.<keyId>, or<storeFieldName>.<groupId>.<language>.<keyId>in the language comparison view. The provider receives the same owner context as on the initial layout load (ownerType,ownerName,keyId,groupId,keyDefinition). This needspimcore/studio-ui-bundle2026.3.5 or later, which sends the new field name.
Note: a field name this endpoint cannot resolve now returns
422with the parse error instead of404"Class with ID: ... not found". This applies to every field type, not only classification store keys. The context of the request stays in the nestedcontextkey of the options provider context and does not overwrite the keys above.
- [Data Objects] Fixed: the auto-save of a data object draft no longer writes the owner objects of a reverse object relation. These edits are applied only on an explicit save (and on updates without a task). The same applies to
PATCHrequests carrying an auto-save task.
Note: edits of such a field that were skipped by an auto-save are not part of the stored draft, so reopening the draft cannot recover them; the client has to send them again with the explicit save. This also applies to custom data adapters that implement the public marker
RemoteStorageDataInterface: they are skipped while an auto-save stores a draft, and inPOST /data-objects/select-options. The marker is only checked on the adapter of a top-level field; adapters nested in localized fields, object bricks or field collections are not checked.DataServiceInterface::updateEditableData()gained an optionalbool $applyRemoteChanges = trueparameter; the default keeps the previous behavior.
- [Users] Security (GHSA-x3pq-323g-f95v): a user who may manage users (
userspermission) can no longer hand out more privilege than they hold themselves. This changes the behavior of the following endpoints for non-admin user managers (admins are not affected):- Saving a user or role (
PUT /user/{id},PUT /role/{id}) returns403if the submitted permissions contain one the caller does not hold (directly or through a role). The full submitted set is checked, so re-saving a user or role that carries a permission the caller lacks fails until it is reduced first. - Assigning a role the caller does not hold returns
403. Clearing roles stays allowed. Role ids that are unknown or not integers return404. - Changing the password (
PUT /user/{id}/password) or the email (PUT /user/{id}) of another user is admin-only and returns403otherwise. Users can still change their own password and email. - Login token links for another user (
POST /user/token-link/{id}) are admin-only and return403otherwise. A link for the caller's own account still works.
- Saving a user or role (
- [Users] Changed: the login token link is built on the server as
<scheme>://<host><base url><pimcore_studio_ui.url_path>/login/?token=.... AtokenLinkrequest body is ignored;TokenLinkRequestBodyandTokenLinkare deprecated and without effect. Scheme, host and port come from the request context, so behind a reverse proxy configureframework.trusted_proxies(andtrusted_headers), otherwise the link may point to a different origin than the one the browser uses. - [Studio UI] The "login as different user" action and the role options in the user form should be limited to what the
backend now allows (admins only for login links, the caller's own roles for non-admins). Until then, non-admin user
managers see
403errors for these actions.
Upgrade to 2025.4.21
- [Documents] Security (GHSA): updating a document (
PUT /documents/{id}) now checks the per-element workspace permissions. This changes the behavior for users who relied on thedocumentspermission alone:- The caller needs the
savepermission on the document (not required for thepublish/unpublishtasks, which keep their own checks), otherwise the request returns403and nothing is changed. - Moving a document to a different parent (
parentId) additionally requires thecreatepermission on the destination document and returns403otherwise. A non-existent destination returns404.
- The caller needs the
Upgrade to 2025.4.20
- [Users] Security (GHSA-x3pq-323g-f95v): a user who may manage users (
userspermission) can no longer hand out more privilege than they hold themselves. This changes the behavior of the following endpoints for non-admin user managers (admins are not affected):- Saving a user or role (
PUT /user/{id},PUT /role/{id}) returns403if the submitted permissions contain one the caller does not hold (directly or through a role). The full submitted set is checked, so re-saving a user or role that carries a permission the caller lacks fails until it is reduced first. - Assigning a role the caller does not hold returns
403. Clearing roles stays allowed. Role ids that are unknown or not integers return404. - Changing the password (
PUT /user/{id}/password) or the email (PUT /user/{id}) of another user is admin-only and returns403otherwise. Users can still change their own password and email. - Login token links for another user (
POST /user/token-link/{id}) are admin-only and return403otherwise. A link for the caller's own account still works.
- Saving a user or role (
- [Users] Changed: the login token link is built on the server as
<scheme>://<host><base url><pimcore_studio_ui.url_path>/login/?token=.... AtokenLinkrequest body is ignored;TokenLinkRequestBodyandTokenLinkare deprecated and without effect. Scheme, host and port come from the request context, so behind a reverse proxy configureframework.trusted_proxies(andtrusted_headers), otherwise the link may point to a different origin than the one the browser uses. - [Studio UI] The "login as different user" action and the role options in the user form should be limited to what the
backend now allows (admins only for login links, the caller's own roles for non-admins). Until then, non-admin user
managers see
403errors for these actions.
Upgrade to 2026.3.4
- [Translations] Fixed: the
admintranslation domain is maintained in Studio with the website languages, but the backend still used the admin UI languages for it. Columns of website languages that are no admin UI language (e.g.fr_BE) stayed empty and sorting by them failed.POST /translations/list,POST /translations/exportand the CSV import now use the website translation languages the user is allowed to view for theadmindomain, and the list only returns the values of these languages. Only thestudiodomain uses the admin UI languages.
Note: this replaces the
admindomain part of the 2025.4.15 entry below. As for the other website domains, a user without any valid website translation language receives403for list, export and import of theadmindomain.
Upgrade to 2026.3.3
- [Data Objects] Changed: the data object detail loads
manyToManyObjectRelationandmanyToManyRelationvalues of fields withoptimizedAdminLoadingwithout instantiating the related elements. Requirespimcore/pimcore2026.3.3 or later, which providesLightweightRelationLoadingInterface. - [Documents] Added:
pimcore_studio_backend.documents.default_controllerssets the controller of new page, snippet and email documents per document type (for documents created without a predefined document type). Types without an entry keep usingpimcore.documents.default_controller, so existing installations are unaffected. - [Grid] Fixed: block fields were silently dropped from the data object grid column configuration because no grid
column definition existed for them. Block fields with
visibleGridViewenabled are now offered as grid columns and render through the existing block cell. Like field collections they are not sortable, filterable or exportable. A field type without a grid column definition is now logged atwarninglevel instead ofinfo.
Upgrade to 2026.3.2
- [Permissions] Fixed: grids, advanced search, quick search and the element detail endpoints now require the
viewpermission instead oflist. Requirespimcore/generic-data-index-bundle2026.3.2 or later, which limits the parent paths of a workspace to thelistpermission, andpimcore/asset-metadata-class-definitions2026.3.2 or later, if installed.- Grids (data objects, assets, documents), advanced search, quick search and relation search dialogs only return
elements the workspaces of the user allow to view. This also applies to grid export, folder batch patch and asset
folder zip. Workspaces with
listbut withoutviewtherefore no longer show up there. The trees still show the parent folders of a workspace. The folders a tree PQL filter reveals only depend on elements the workspaces of the user allow to view. GET /data-objects/{id},GET /documents/{id}andGET /assets/{id}return403for elements the user may list but not view, and404for elements the user may not list. This check uses the core permissions, including workflow place permissions. Grids and search use the workspace permissions of the search index only.GET /dependencies/{elementType}/{id}requiresviewon the element in the same way.- Update endpoints (
PUT) return the updated element, so for users with save or publish permission but withoutviewthe response is403or404. The update itself is applied as before. - Grids and advanced search return
404for a folder the user may not list. In the grid, the asset metadata columns of type asset, document and object stay empty for a related element withoutview. The export still contains the path of that element.
- Grids (data objects, assets, documents), advanced search, quick search and relation search dialogs only return
elements the workspaces of the user allow to view. This also applies to grid export, folder batch patch and asset
folder zip. Workspaces with
- [Grid] Fixed: exporting an advanced column with a transformer filled empty localized source fields with the system
default language, ignoring the configured fallback languages. The export now uses only the configured fallback
languages, with or without a transformer. The interactive grid is unchanged. A missing source value now exports as
an empty string instead of
"null". - [Elements] Fixed: asynchronous batch edits, replacing usages and updating references after a copy removed unpublished related elements from the saved relations. Grid exports left them out. All of them now keep unpublished related elements, as the grid and the element editors do. Batch edits, replacing usages and updating references also no longer save localized fallback values into empty languages.
Upgrade to 2026.3.0
- [Data Objects] Improved: every
inheritanceData.metaDataentry of the data object detail response (and theinheritanceof a grid column) now carries two additional properties next toobjectIdandinherited:inheritable(bool): whether the field type can take part in inheritance at all. It isfalsefor field types whosesupportsInheritance()returnsfalse(e.g.urlSlug,calculatedValue,fieldcollections) and for field types without a Studio data adapter, so a client can tell an overridden value (inherited: false, inheritable: true) apart from a field that can never inherit (inheritable: false).inheritedValue(mixed): the value the field inherits — or would inherit if its own value were removed — from the nearest ancestor that holds a non-empty value, normalized to the same shape asobjectData. It isnullwhen no ancestor holds a value, when the field is not inheritable, or when it was not requested: resolving it costs a walk up the tree for every field holding an own value, so it is opt-in. The data object detail response requests it; grid columns do not and always reportnull.
Note: both properties are additive;
objectIdandinheritedkeep their meaning.InheritanceServiceInterface::getInheritanceData()gained abool $resolveInheritedValues = falseparameter andgetFieldInheritanceData(), which returns the completeInheritanceDatafor a single field. The opt-in travels through the recursion asFieldContextData::shouldResolveInheritedValue()(constructor argumentresolveInheritedValue). CustomDataInheritanceInterfaceadapters that buildInheritanceDatathemselves should switch togetFieldInheritanceData()and passresolveInheritedValueon to theFieldContextDatathey create for their child fields; instances they construct directly keep working and default toinheritable: true,inheritedValue: null.
Upgrade to 2025.4.15
- [Translations] Fixed: website translations for locales that are not admin UI languages (e.g.
fr_BE,nl_BE) could not be maintained.POST /translations/listonly returned values for the available admin UI languages, so these columns stayed empty, and sorting by such a locale failed. The list now returns the languages the user is allowed to view for the requested domain (admin UI languages for theadminandstudiodomains), as in the classic admin UI.
Note: this comes with the following behavioral changes for the translation list (
POST /translations/list) and, where noted, the CSV export (POST /translations/export) and import:
- Users with restricted website translation languages only receive values for their allowed languages, also for requests without
filters.- Website translation languages configured on a user or role that are not valid system languages are ignored. A user without any valid website translation language left receives
403for list, export and import (previously an empty result).- All
translationLikecolumn filters of a request are applied (previously only the first one). AtranslationLikefilter on a language that is not available to the user returns422. The filter only applies to translation listings.- Additional sort filters on a locale are supported (previously failed with a database error).
- The translation list no longer uses the core translation listing cache for the list of keys, as that cache does not take the requested languages into account. Translation values are still cached per key and language.
Upgrade to 2025.4.13
- [Data Objects] Fixed:
POST /data-objects/select-optionsfailed withCall to a member function getDataFromEditmode() on nullas soon aschangedDatacontained unsaved localized fields. The endpoint decodedchangedDatawith the classic editmode format (localized fields as language → attribute) while Studio sends its own data format (attribute → language).changedDatais now applied through the same data adapters as a regular save, so it expects the Studio data format for every field type. Language edit permissions of non-admin users are now respected per language as well, instead of being matched against attribute names.
Note: the internal
ApplyChangesHelper(DataObject\Legacy) and its interface are deprecated and will be removed in 2027.1.0, since the select-options endpoint was their only consumer. They still expect the classic editmode data format; useDataServiceInterface::updateEditableData()with the Studio data format instead.
Upgrade to 2025.4.7
- [User Management] Fixed:
GET /user/{id}could time out or run out of memory when the user was referenced by a very large number of DataObjects (e.g. via aUser-type class field), because the full, unbounded list of referencing objects was hydrated and embedded in every response. TheobjectDependencies.dependenciesarray on theUserschema is now capped at 20 entries, and a new paginatedGET /user/{id}/object-dependenciesendpoint was added to browse the full list.
Note: the
objectDependenciesschema itself has no breaking change -dependenciesandhasHiddenkeep their existing names, types, and meaning. The newtotalItemsfield is marked optional in the OpenAPI schema (even though it is always present in the actual response) specifically so that generated SDK types remain source-compatible with any existing code that constructs or mocks anobjectDependencies-shaped value without it. There is, however, a behavioral compatibility impact worth knowing about:dependenciespreviously contained the user's complete list of referencing objects, and now stops at 20. Any existing integration that assumeddependencieswas exhaustive (rather than checkingtotalItems) will now silently see only the first 20 - such integrations must start readingtotalItemsand, if it exceedsdependencies.length, call the new paginatedGET /user/{id}/object-dependencies?page=&pageSize=endpoint to get the rest.hasHiddenis affected the same way: it now only reflects permission-denied objects within that 20-item window, not across the full list as before. In both the preview and the new paginated endpoint,totalItemscounts every referencing object regardless of the caller's view permission on it - it does not shrink to match what the caller can actually see, so a page (or the preview) can legitimately come back shorter than requested, or empty, whiletotalItemsstays the same.
Upgrade to 2025.4.6
- [GDPR Objects Export] Fixed: the data object export now includes inherited values (including inherited localized fields).
Note: the structure of the exported data changed slightly to align with the Studio API data structure (e.g., relations are now exported as structured element data instead of plain
id/typepairs).
Upgrade to 2025.4.5
- [Grid Configuration] Fixed: Changed the length of
classIdcolumn inbundle_studio_grid_configurationsandbundle_studio_grid_configuration_favoritestables from 10 to 50 characters to support longer class IDs.
Migration execution required
After upgrading, please execute the migration to apply the necessary database changes.
Note: Grid configurations that were previously saved with a class ID longer than 10 characters have a truncated
classIdvalue in the database and will not be recovered by this migration. These configurations need to be deleted and re-saved after upgrading.