# September 24th

**Changelog released on 2025-09-24**

Welcome, this release adds support for asset references in Publications, fixes hidden values in complex attributes on resize, prevents global list cutoff, resolves Elastic response failures, stops dimension clipping with headers, enlarges the ‘Total amount in search result’ text and fixes NgOptimizedImage warnings.

## Enhancement

1. **Support asset references in Publications:** Asset references are now supported in publications. (SP-1768)

## Bug

1. **NgOptimizedImage warnings due to different image size:** Fixed an issue causing NgOtimizedImage warnings. (SP-1689)
2. **Import preview header displayed above quick function overlay in the z-index:** Fixed an issue causing the header shown on import preview to be displayed in front of quick function sidebars. (SP-1709)
3. **Dimensions sometimes clash/clip with field headers:** Dimension headers and input headers no longer clash. (SP-1748)
4. **Global list value rendering cuts off characters:** When rendering global list values sometimes parts would be cut off due to padding. e.g. an Å could have its top cut off making it resemble an A. (SP-1755)
5. **Complex attribute hides its values when changing window size:** Changing window size could cause complex attribute values to render incorrectly making them seem invisible or cut off. (SP-1757)

## Task

1. **Reading elastic response can fail:** Fixed an internal issue in the system when reading elastic responses. (SP-1754)

## Feature request

1. **Enlarge the 'Total amount in search result' text :** The text showing the total amount of results in a search has been enlarged, making it easier to read. (SP-1713)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.struct.com/changelog/september-2025/september-24th.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.