> For the complete documentation index, see [llms.txt](https://docs.fylr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fylr.io/releases/2026/v6.35.1.md).

# Release v6.35.1 (2026-10-27)

Published 2026-10-27 12:12:47Z

* [fylr\_checksums.txt](https://s3.eu-central-1.wasabisys.com/fylr-releases/v6.35.1/fylr_checksums.txt)
* [fylr\_v6.35.1\_darwin\_amd64.tar.gz](https://s3.eu-central-1.wasabisys.com/fylr-releases/v6.35.1/fylr_v6.35.1_darwin_amd64.tar.gz)
* [fylr\_v6.35.1\_darwin\_arm64.tar.gz](https://s3.eu-central-1.wasabisys.com/fylr-releases/v6.35.1/fylr_v6.35.1_darwin_arm64.tar.gz)
* [fylr\_v6.35.1\_linux\_amd64.tar.gz](https://s3.eu-central-1.wasabisys.com/fylr-releases/v6.35.1/fylr_v6.35.1_linux_amd64.tar.gz)
* [fylr\_v6.35.1\_windows\_amd64.zip](https://s3.eu-central-1.wasabisys.com/fylr-releases/v6.35.1/fylr_v6.35.1_windows_amd64.zip)

## Important

* **Storage locations no longer redirect downloads.** The `allow_redirect` option is removed: fylr delivers every file itself, from S3 as well, as it did up to 6.34. In 6.35.0 the redirect cost the web frontend its thumbnails when the bucket had no CORS rule for the instance. A `fylr.yml` that still sets `allow_redirect` loads; the key only produces an unknown-key warning. The update removes the option from the database, so an instance on 6.35.1 cannot go back to 6.35.0. There is no re-index. → [Location Manager](https://docs.fylr.io/for-administrators/location-manager) \[bf725ba6e]
* **Where execservers call back is set with `callbackBackendOwnURL` and `callbackApiOwnURL`.** fylr works out the addresses on which an execserver and its plugins reach it. Where it cannot, with fylr in a container or behind NAT and the execserver on another machine, `fylr.execserver.callbackBackendOwnURL` sets the backend address and the new `fylr.execserver.callbackApiOwnURL` the API address handed to plugins, each as written. `callbackBackendInternalURL` and `callbackApiInternalURL` are ignored; when one of them names another address than the one in use, the startup log names the key and the value to set instead. In 6.35.0 an installation that named its host only in the `InternalURL` keys handed the execserver the container's address. → [Execserver on another Linux](https://docs.fylr.io/for-system-administrators/installation/linux-docker-compose/execserver-on-another-linux) \[ce3de82c8]
* **Versions with a watermark or a color profile from fylr's resources are produced once more.** Once after the update, each such version is produced again at the next sync of its file; from then on it keeps its file when the address execservers reach fylr on changes. See "Versions with a watermark or a color profile are no longer produced again without a change" under **Fixed**. \[b61c155ca]
* **The re-index 202 of `POST /api/v1/objecttype` and `POST /api/v1/pool` is answered with `confirm_reindex`.** The query parameter was called `confirmReindex`, which is no longer read. A script that sends a fixed `confirmReindex=yes` sends `confirm_reindex=yes` now; a client that repeats the button of the 202, like the web frontend, needs no change. See "Backup and restore with mask filters and standard masks" under **Fixed**. \[b58dc5594]

## fylr core

### Improved

#### OpenSearch: a user limited to the instance's own indices

fylr runs with an OpenSearch user whose rights cover only the instance's own indices, `<fylr.name>-<uuid>-…`, so several instances can share one OpenSearch without reaching each other's indices. Changing the database languages no longer needs the right to create an index outside these. When OpenSearch does not let fylr read the cluster settings, fylr keeps `fylr.elastic.maxMem` as configured and logs a warning at startup. → [OpenSearch user per instance](https://docs.fylr.io/for-system-administrators/installation#opensearch-user-per-instance) \[14975bd20]

### Fixed

#### Many files re-produced at once no longer stop the instance

`produce_versions` in `/inspect/files/` on a few hundred originals at once runs through; it could stop every database operation of the instance, file jobs, indexing and requests alike, until fylr was restarted. A request whose client went away no longer leaves a broken database connection behind, on which another request failed with "driver: bad connection". \[720b12365]

#### Re-index: a failed run no longer blocks the instance

A blocking re-index that fails, for example because OpenSearch refuses to create the new index, lifts the block again; the web frontend and the API no longer answer `503` until fylr is restarted. The `REINDEX_ERROR` event and the answer of `POST /api/v1/system/reindex` name the reason. With OpenSearch 3 the most common one is a missing `-Dopensearch.xcontent.depth.max=10000` in `OPENSEARCH_JAVA_OPTS`. While a blocking re-index runs, file downloads keep working, so the maintenance page shows the logo and pages that embed fylr images keep them. → [Re-index](https://docs.fylr.io/for-system-administrators/inspect/system#re-index) \[dc2ddf9d4]

#### Re-index: a second re-index keeps the indexes of the first

A second `POST /api/v1/system/reindex` that starts after the first one has switched to its new indexes no longer purges these indexes, which searches were already reading, and no longer writes the old index versions back. The switch of a re-index that a newer one has stopped no longer switches to the newer one's indexes before they are filled. \[e28a638ab]

#### Memory: the server cache no longer grows with each datamodel commit

A reload of the server cache inside a request, at a datamodel commit, a purge or a base config save that re-indexes, kept the previous cache reachable, so memory grew with each of them. A reload starts from a clean cache now. \[a3e301ad8]

#### Schedules keep their local hour across summer and winter time

A schedule with days of the month or weekdays runs at its hour in its time zone also when a change between summer and winter time lies between the calculation and the day; it ran an hour off. This covers `next_run_at` of tasks and exports and the user's mail schedule; schedules with hours only were not affected. \[2853e3a31]

#### Backup and restore with mask filters and standard masks

A restore of a backup whose object types or pools have mask filters or standard masks no longer stops with `Error received: 202 Accepted:` at `basetype_objecttype` or `basetype_pool`, also into an instance that already holds records; the restore re-indexes at its end. A backup holds the mask filters of the object types again: since 6.11.0 it left them out, so a restore brought the object types back without them, and a backup made before 6.35.1 still lacks them. `POST /api/v1/objecttype` and `POST /api/v1/pool` save a mask change that affects no record without the re-index 202, and `confirm_reindex=skip` (with `system.root`) saves without queuing the re-index, for a client that re-indexes afterwards. \[b58dc5594]

#### Backup and restore: file names with `#`, `?` or `%`

A restore of a backup made with `--include-files` no longer aborts on a packed file whose name contains `#`, `?` or `%`, and existing backups restore as they are. A new backup names its packed files like export filenames, with `#`, `%` and the characters Windows forbids replaced by `_`, and keeps each filename within 100 bytes by cutting out the middle of a long name, so the backup also works on Windows; the restore uploads every file under its original name. Export and download filenames now replace `#` and `%` with `_` as well. → [Backup](https://docs.fylr.io/for-system-administrators/migration/backup#include-files) \[bfc6585f3]

#### Backup and restore: file names with folders

A restore with `--file-api put`, which every packed file of an `--include-files` backup takes, keeps a file name with folders, such as `Plakate/2026/final.jpg`, as it is. Since 6.15.0 it kept only the part after the last `/` (run on Windows, also after the last `\`), so `original_filepath` lost its folders; the file itself and `original_filename` were not affected. A restore with `rput` always kept the full name. Files restored before keep the shortened name. \[04d720631]

#### Base config: secrets kept when one value is set by path

Setting or removing a single value of a base config section through the API by its path (`POST` / `DELETE /api/v1/config/…/<section>/<parameter>`) keeps the passwords and keys stored in that section; they were replaced by their mask and had to be entered again. This covers plugin sections as well as e.g. the e-mail server and LDAP passwords. → [Secrets](https://docs.fylr.io/for-developers/plugin/manifest/base-config#secrets) \[93062baa2]

#### Base config: secrets stay with their table rows

Moving or removing rows of a table in a plugin's base config keeps each row's passwords and keys in its own row; the rows after a moved or removed row used to get the secrets of other rows. `GET /api/v1/config` gives each row of a table with a secret field its stored position in `_row`; a row posted back with its `_row` keeps the secrets of that row, a row without it is new, and a table posted without any `_row` pairs its rows by position as before. → [Secrets](https://docs.fylr.io/for-developers/plugin/manifest/base-config#secrets) \[2ce58bf25]

#### Workflow e-mail recipients

Saving workflows no longer fails with "sqlpro.ExecTX: panic caught" when an e-mail action has an empty recipient row; the message names the workflow and the row instead. An e-mail address that is not yet a user can be added as a recipient ("… anlegen"): saving the workflow creates the e-mail user, in the tag manager as well as in pool and object type workflows. → [Tags & Workflows](https://docs.fylr.io/for-administrators/permissions/tags-and-workflows) \[2f1e7493b]

#### Plugins: one plugin that fails to load no longer stops the others

A plugin whose JavaScript fails to load in the web frontend, because of a syntax error or an error while it starts, stops only itself; the browser console names it, and the plugins after it load as before. It used to stop every plugin loaded after it, so an instance with one such plugin could end up without any custom data types: the data model offered none, and their fields showed "plugin not loaded". Plugins without a dependency between them load in the order of their names; they loaded in reverse order. → [webfrontend](https://docs.fylr.io/for-developers/plugin/manifest#webfrontend) \[c3adc8e05]

#### Versions with a watermark or a color profile are no longer produced again without a change

A version with a watermark, or with a color profile from fylr's resources, keeps its file when the address execservers reach fylr on changes: after a restart with a new IP, between replicas with their own `callbackBackendOwnURL`, and when fylr corrects that address after its first execserver connection. A version with a color profile uploaded to the base config is no longer produced again at every sync of its file. → [File worker](https://docs.fylr.io/for-developers/file-worker) \[b61c155ca] \[b62c0e24c]

#### Watermarks: a file used by several records

A file used by several records gets its watermark or caption version for each record whose pool, or object type without pools, has a watermark or caption, also when another of these records has none. Such a file used to get none of these versions, and an existing one was deleted once a record without a watermark started using the file. A file that is missing the version gets it the next time it is synced, for example when one of its records is saved. → [Watermarks](https://docs.fylr.io/for-administrators/permissions/pools#watermarks) \[3ec5f0ea5]

#### Preview versions: transparent CMYK images get the right background

A CMYK image with a transparent background, such as a TIFF or PSD saved for print, is filled with the background color its version asks for. White and black were swapped: a JPG version, and a PNG or WebP version with `background`, came out dark gray where it should be white and white where it should be black, with and without `clip` and also with a CMYK color profile. RGB images were not affected. Existing versions change when they are produced again. → [Preview configuration](https://docs.fylr.io/for-administrators/readme/file-worker/preview-configuration#recipe-configuration) \[2b7a72649]

#### Export and download: a file that is not ready no longer fails the run

A download or export of a record whose file failed to upload or to be produced, or is still being processed, leaves that file out and ends as `done_with_warnings`; the warning in the run's `EXPORT_FINISH` event names the file, the record it belongs to by its System Object ID, and the file's status as the file API reports it, such as `failed`. The run used to fail as a whole, also when the file belonged to a linked record and was not part of the export at all; such a file is no longer checked. The web frontend shows these warnings, see **Web frontend**. → [EXPORT\_FINISH](https://docs.fylr.io/for-administrators/events/event-type-reference#export_finish) \[67c8a508d] \[d9adbb398]

#### Export and search: files in nested tables of reverse linked records

Files in a nested table of a reverse linked record are exported again, also when that record is itself the reverse linked record of another one, and a search with `include_fields` for such a file field returns the files instead of empty entries. → [Exporting](https://docs.fylr.io/for-users/download-and-export/exporting) \[c3a9ec170]

#### Export: running an export no longer changes its saved search

An export whose search uses a subsearch no longer gets another copy of the not-deleted filter written into its saved search on every save and run, so the saved search no longer grows. A subsearch saved without `limit` keeps having none, and an export saved without objecttypes keeps searching all of them, also those added to the datamodel later. \[fa28bbf9f]

#### Polyhierarchy: records below the virtual top level in the filter

A record of a polyhierarchical list that also hangs from the virtual top level is listed on the top level of the filter as well as below its other parent, and selecting it there finds the same records. In the API, a `linked_object` aggregation with `filter_parent` `null` or `0` returns such records on the top level. \[089eb4676] \[622e0f07b]

## Web frontend

### Fixed

* A guest no longer gets *Self update of "company" is not allowed* when the web frontend saves its settings, for example on opening a mask panel or switching the result view. Since 6.35.0 fylr lets a guest save only its frontend settings on its own user, and the web frontend sent the profile fields along wherever a group gave the guest the right to edit them. \[8aaf10042]
* A workflow e-mail action with an empty recipient row marks the row and is not saved, and copying such a workflow works. \[c0de2de9d]
* The location manager no longer offers *Allow Redirect*, see **Important**. \[fec06fc82]
* In the detail of a polyhierarchical record, *Virtual Top Level* among the parents reads like the other parents and no longer opens a quick view that calls it deleted, and a record with several parent paths shows one row per path. \[a011cf5ea] \[651a17b32]
* The download dialog counts a picked version only for the files that have it: the file count in its footer and the default of *Download as ZIP* counted every file once per picked version. \[2e8dab437]
* A download or export that left out files shows which ones: the warning popup of a download lists the warnings, and the `EXPORT_FINISH` row of the export list has the protocol button. \[e8d614268]
* Cropping uses the measured size of the original. An original without width and height took the size of a large version, so the crop cut the wrong area; without the original's size the rendition editor says it cannot crop and points to *Resync with metadata*, and the editor and the download dialog warn when an image cannot be cropped. \[d6afbbc4a] \[9095c4712] \[85818be87]
* The button of the 360° view shows a panorama icon. \[32f3a8267]
* Menus, tooltips and dialogs opened in fullscreen, such as the settings menu of the 3D viewer, show inside the fullscreen; they opened outside it, where they could not be seen. \[32f3a8267]
* Menus and selects drop the hover highlight when the mouse leaves the list. \[32f3a8267]
* The 3D viewer shows a glb model whose meshes share a texture without black patches. \[ad47494c1]

### Docker images

```
docker.fylr.io/fylr/fylr:v6.35.1
docker.fylr.io/fylr/fylr-server:v6.35.1
```
