Gentics CMP Changelog
The Velocity rendering engine has been removed from the CMS. Constructs using one of the part types
must be migrated to using Handlebars before updating the CMS.
If the migration from Velocity to Handlebars cannot be completed in advance, Velocity can be added back as a custom component.
Please contact our Sales team at sales@gentics.com to discuss this option.
REST API: Now Enterprise CMS has its own version of OpenAPI specification, containing the enterprise features, such as content staging, automatic translation, license management, etc
Gentics CMS is now tested against MariaDB 12.3 automatically
The CMS Kubernetes Helm Chart has been improved:
The new Groovy Part Type allows to add business logic for rendering in constructs.
See Implementation of Groovy Scripts for details.
Auth: It is now possible to create API Tokens with name and optional expiry date for the current user.
A new content field type, `JSON`, has been introduced, offering support for storing and navigation on a JSON object/array content.
Formgen: Pass formDataUuid cookie value as query parameter in validation requests when using CMS Forms.
Editor User Interface: In some occurrences of referencing a master node item from a channel page, the repository browser pointing to the item fails to resolve its environment. This has been fixed.
Administrator User Interface: Added back the missing “create user” button in the user module.
Administrator User Interface: Resolved date picker not showing the calendar
Administrator User Interface: The Elasticsearch field of Mesh schemas now opens with multiple lines and scrolls instead of clipping large JSON values.
FormGen: Fixed the full-screen loading overlay shown while a form is initializing displaying the raw translation key instead of the translated loading text.
When a handlebars or velocity part of a tag was rendered directly, cms.tag could not be
resolved in the scope of the part. This has been fixed.
The REST API Endpoints /diff/html and /diff/source will now use Handlebars instead of
Velocity to render the diff. If requests are made using custom templates, they must be converted to Handlebars templates.
The CMS Kubernetes Helm-Chart has been changed to better match the overall structure of Gentics Charts:
Auth: The authentication mechanism for the REST API has been modified to no longer
require the sid as query parameter. Client implementations that use the sid should be
updated accordingly.
REST API: Along with existing RAML API definition, it is now possible to generate an OpenAPI (aka Swagger) specification for the Mesh REST API. For that, an endpoint `/openapi.yaml` has been provided.
Core: Now it is possible to purge empty (micro)schema versions automatically, via new background jobs. This will save storage and runtime resources of the database.
The purge process is triggered via REST API `POST /utilities/purge/schemas/versions` and `POST /utilities/purge/microschemas/versions` respectively, and can be parameterized by schema name/UUID filters.
Core: A new field type, `JSON`, has been added. Having a string in its base, it provides such additional functionality, as JSON structure / schema verification, and extended JsonPath filtering in GraphQL requests.
Core: The `Hibernate` ORM dependency has been updated to the version `7.4.4.Final`.
The `Vert.x` framework dependency has been updated to the version `5.1.5`.
MCP Server: A new Model Context Protocol (MCP) server is now available as an optional, separately deployed component of Gentics Mesh Enterprise. It exposes published Gentics Mesh content to AI agents and LLM-based tools through a small set of well-defined MCP tools (listing projects and schemas, loading nodes by UUID or webroot path, searching nodes and running GraphQL queries), so language models never talk to the Gentics Mesh API directly. Access is restricted by a policy layer (project and language allowlists), protected by rate limiting, bulkheads and a circuit breaker, and authenticated with a Bearer token in HTTP mode. The server is shipped as its own container image.
See MCP Server in the documentation for details.
Search: Added Content RAG semantic search and source-referenced answer generation over Mesh content (enterprise feature, disabled by default). Content is chunked and stored in dedicated `-ragchunk-` indices as part of the standard search sync; vectorization is handled by an Elasticsearch ingest pipeline. Included schemas and fields are controlled via the existing `elasticsearch` settings (`rag: true|false`, `rag.fields`) and `noIndex`. Permissions are derived from the requesting user‘s Mesh token.
See Content RAG in the documentation for details.
Auth: The management of API Tokens for users has been enhanced to support multiple tokens per user.
New tokens must now be created with a `name` and optionally can have an `expires` date.
See the Mesh Restful API documentation
for details.
Database: Now Mesh is tested against MariaDB 12.3.
Some Dependencies have been updated:
REST API: Along with existing RAML API definition, it is now possible to generate an OpenAPI (aka Swagger) specification for the Mesh REST API, which can optionally include the API for all the currently running Mesh Plugins.
For that, two new endpoints are provided, `/openapi`, which can be configured with `format` (`yaml or `json`) and/or `version` (`3.0` or `3.1`) query parameters, and a shortcut, `/openapi.yaml` or `/openapi.json`, depending on the default values, configurable in the options.
REST API: Along with existing RAML API definition, it is now possible to generate an OpenAPI (aka Swagger) specification for the Mesh REST API. For that, an endpoint `/openapi.yaml` has been provided.
Core: Now it is possible to purge empty (micro)schema versions automatically, via new background jobs. This will save storage and runtime resources of the database.
The purge process is triggered via REST API `POST /utilities/purge/schemas/versions` and `POST /utilities/purge/microschemas/versions` respectively, and can be parameterized by schema name/UUID filters.
The Mesh Kubernetes Helm Chart has been improved:
MCP Server: A new Model Context Protocol (MCP) server is now available as an optional, separately deployed component of Gentics Mesh Enterprise. It exposes published Gentics Mesh content to AI agents and LLM-based tools through a small set of well-defined MCP tools (listing projects and schemas, loading nodes by UUID or webroot path, searching nodes and running GraphQL queries), so language models never talk to the Gentics Mesh API directly. Access is restricted by a policy layer (project and language allowlists), protected by rate limiting, bulkheads and a circuit breaker, and authenticated with a Bearer token in HTTP mode. The server is shipped as its own container image.
See MCP Server in the documentation for details.
Search: Added Content RAG semantic search and source-referenced answer generation over Mesh content (enterprise feature, disabled by default). Content is chunked and stored in dedicated `-ragchunk-` indices as part of the standard search sync; vectorization is handled by an Elasticsearch ingest pipeline. Included schemas and fields are controlled via the existing `elasticsearch` settings (`rag: true|false`, `rag.fields`) and `noIndex`. Permissions are derived from the requesting user‘s Mesh token.
See Content RAG in the documentation for details.
Core: A new field type, `JSON`, has been added. Having a string in its base, it provides such additional functionality, as JSON structure / schema verification, and extended JsonPath filtering in GraphQL requests.
Core: The `Hibernate` ORM dependency has been updated to the version `7.4.4.Final`.
The `Vert.x` framework dependency has been updated to the version `5.1.5`.
The Mesh Kubernetes Helm-Chart has been changed to better match the overall structure of Gentics Charts:
Auth: The management of API Tokens for users has been enhanced to support multiple tokens per user.
New tokens must now be created with a `name` and optionally can have an `expires` date.
See the Mesh Restful API documentation
for details.
Database: Now Mesh is tested against MariaDB 12.3.
Some Dependencies have been updated:
REST API: The endpoint definitions of all REST plugins have been extended to provide the most possible fullfilling information to the OpenAPI specification, available per plugin via `/openapi.yaml` (or `/openapi.json` for Mesh Enterprise) endpoint.
Forms-Plugin: Fixed the issue that the validate endpoint reported a mandatory file upload field as empty, although the file had already been uploaded and saved.
The `Vert.x` framework dependency has been updated to the version `5.1.5`.
The Gentics Portal | java Kubernetes Helm Chart has been improved:
The Portal | java has been updated to allow previews of forms in Gentics CMS using the FormGen app.
For this to work, the Handlebars template used to render a page must render a base element
when rendering previews. See the documentation for details.
When requests are processed the correct context is maintained now even if other threads (like HTTP clients) are used for external requests.
Some Dependencies have been updated:
The Gentics Portal | java Kubernetes Helm-Chart has been changed to better match the overall structure of Gentics Charts:
The default directory and serve path in the portal configuration for the FormGen app have changed:
forms.formgenStaticFileDirectory: /portal/data/static/cpa/ -> data/static/cpa/formgenforms.formgenStaticServePath: /static/cpa/ -> /formgen/In case the default configuration was used, the path for the built FormGen app either has to be adapted, or the custom path must be set in the forms configuration.
An OpenAPI v3.0 YAML specification can now be generated under /api/openapi.yaml. This feature can be disabled in the config.
The Gentics Portal | php Kubernetes Helm Chart has been improved:
The Portal | php has been updated to allow previews of forms in Gentics CMS using the FormGen app. For this to work, the Handlebars template used to render a page must render a
The Gentics Portal | php Kubernetes Helm-Chart has been changed to better match the overall structure of Gentics Charts:
The default directory and serve path in the portal configuration for the FormGen app have changed:
forms.staticFileDirectory: public_path('public/static/cpa/') -> public_path()forms.staticServePath: /static/cpa/ -> /This means the built FormGen app has to reside in public/formgen now. In case the default configuration was used, the path for the built FormGen app either has to be adapted, or the custom path must be set in the forms configuration.
The following dependencies have been updated, to make Portal | PHP ready for Laravel 13: