> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/changelog/2023-and-older/2023/improvements-and-fixes-october-2023.md).

# Improvements and fixes, October 2023

Improvements and bug fixes released in October 2023.

*31 October 2023*

## Improved

* **Portal:** New design for registration and magic link pages, optimized for password managers. Merged User segments and Page segments into one page.
* **Portal:** Added missing help documentation to several pages.
* **Editor:** Improved cross-origin iFrame recording support. Improved auto-translate stability for long Guides. Updated Editor buttons to follow Design System.
* **Other:** Removed flickering when Tags or Tooltips are deleted in Editor list view. Unified Page Segmentation and URL Exceptions List logic.

## Fixed

* **Portal:** Fixed wrong usage number for user segments in NPS builder. Fixed several UI issues.
* **Editor:** Fixed RegEx generation errors, dropdown close behavior, search icon positioning, and Welcome Slide close edge case.
* **Other:** Fixed Indonesian translation upload, German umlaut lowercasing, and Browser Extension loading under specific circumstances.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.userlane.com/changelog/2023-and-older/2023/improvements-and-fixes-october-2023.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.