Skip to main content
Version: 2025.4

Upgrade Information

The following steps are necessary during updating to newer versions.

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 the documents permission alone:
    • The caller needs the save permission on the document (not required for the publish/unpublish tasks, which keep their own checks), otherwise the request returns 403 and nothing is changed.
    • Moving a document to a different parent (parentId) additionally requires the create permission on the destination document and returns 403 otherwise. A non-existent destination returns 404.

Upgrade to 2025.4.20​

  • [Users] Security (GHSA-x3pq-323g-f95v): a user who may manage users (users permission) 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}) returns 403 if 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 return 404.
    • Changing the password (PUT /user/{id}/password) or the email (PUT /user/{id}) of another user is admin-only and returns 403 otherwise. Users can still change their own password and email.
    • Login token links for another user (POST /user/token-link/{id}) are admin-only and return 403 otherwise. A link for the caller's own account still works.
  • [Users] Changed: the login token link is built on the server as <scheme>://<host><base url><pimcore_studio_ui.url_path>/login/?token=.... A tokenLink request body is ignored; TokenLinkRequestBody and TokenLink are deprecated and without effect. Scheme, host and port come from the request context, so behind a reverse proxy configure framework.trusted_proxies (and trusted_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 403 errors for these actions.

Upgrade to 2025.4.16​

  • [Documents] Added: pimcore_studio_backend.documents.default_controllers sets 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 using pimcore.documents.default_controller, so existing installations are unaffected.

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/list only 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 the admin and studio domains), 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 403 for list, export and import (previously an empty result).
  • All translationLike column filters of a request are applied (previously only the first one). A translationLike filter on a language that is not available to the user returns 422. 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-options failed with Call to a member function getDataFromEditmode() on null as soon as changedData contained unsaved localized fields. The endpoint decoded changedData with the classic editmode format (localized fields as language → attribute) while Studio sends its own data format (attribute → language). changedData is 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; use DataServiceInterface::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 a User-type class field), because the full, unbounded list of referencing objects was hydrated and embedded in every response. The objectDependencies.dependencies array on the User schema is now capped at 20 entries, and a new paginated GET /user/{id}/object-dependencies endpoint was added to browse the full list.

Note: the objectDependencies schema itself has no breaking change - dependencies and hasHidden keep their existing names, types, and meaning. The new totalItems field 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 an objectDependencies-shaped value without it. There is, however, a behavioral compatibility impact worth knowing about: dependencies previously contained the user's complete list of referencing objects, and now stops at 20. Any existing integration that assumed dependencies was exhaustive (rather than checking totalItems) will now silently see only the first 20 - such integrations must start reading totalItems and, if it exceeds dependencies.length, call the new paginated GET /user/{id}/object-dependencies?page=&pageSize= endpoint to get the rest. hasHidden is 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, totalItems counts 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, while totalItems stays 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/type pairs).

Upgrade to 2025.4.5​

  • [Grid Configuration] Fixed: Changed the length of classId column in bundle_studio_grid_configurations and bundle_studio_grid_configuration_favorites tables 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 classId value in the database and will not be recovered by this migration. These configurations need to be deleted and re-saved after upgrading.