XperienCentral R44

We are proud to introduce XperienCentral release 44, which focuses on the GraphQL API. This release provides new opportunities for front-end developers and strengthens the headless integration with the CMS. GraphQL offers developers the flexibility to fetch exactly the data they need, resulting in efficient and robust applications.

New GraphQL features and extensions

Modular content types, metadata, and elements

The GraphQL API now supports fetching modular content types, elements, and page metadata. This combination makes output possibilities endless and offers great flexibility to designers and front-end developers. Content modules can be easily reused and extended, simplifying and speeding up the content management process.

Improved naming and structure

We have improved the naming and structure within the GraphQL API to make it more consistent and intuitive. This helps developers get started faster and reduces the learning curve.

Fetching the home page

The home page is often the most requested and linked page on a website. With the new feature, developers can now fetch this page directly via the GraphQL API without additional filtering.

Elements on the canvas

All elements that would normally be placed on a page can now also be fetched via the GraphQL API to be rendered elsewhere. This allows editors to determine which elements appear in which order on the page, while front-end developers receive this data structured via the GraphQL API.

Form fields and steps

The GraphQL API now supports form fields and steps, including custom fields and configurations. These can be fetched separately from a page to integrate seamlessly into content where needed. A method to handle submissions headlessly via the CMS is still under development.

Result caching

The API now supports caching of results, significantly improving performance by reducing server load and offering faster response times.

Fallback language support

With fallback language support, users can fetch content in an alternative language if the desired language is unavailable. This is essential for international applications and improves content accessibility.

Other bug fixes and improvements

• RSS feed elements become empty after saving an incorrect URL.
• Unable to edit RSS feed elements when the URL is invalid.
• Cannot paste all copied elements from the clipboard in IAF.
• Logs are spammed with messages about filtered IP addresses from the X-Forwarded-Host header.
• The CSP panel fails when validating a valid reporting URL.
• Discussions are not fully functional in the frontend.
• Disabling unused content may also disable currently used content.
• Image validation service sometimes incorrectly rejects SVG files.
• Removing and dumping dumped pages does not work properly.
• Unable to change presentation variants for plugin-based elements.
• The 'Used In' widget does not show more than 20 results.
• Content can contain empty <a> tags.
• Modular content elements do not display validation errors.
• Links to content items in modular content properties do not work.
• Support for sharing a single image among all versions of a media item.