> 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/2024/improvements-and-fixes-may-2024.md). # Improvements and fixes, May 2024 Improvements and bug fixes released in May 2024. *31 May 2024* ## Improved * **Portal:** Improved how Page Segments are shown in the dropdown when adding them to a Guide (now sorted alphabetically). * **Portal:** Improved the analytics filters to make it possible to search for User Segments and make it clearer when no filter has been applied. * **Portal:** Implemented a stack upgrade to ensure optimal performance of the Userlane Portal. * **Editor:** Users can now publish more Tags per page without impacting the performance of the underlying app. ## Fixed * **Portal:** Fixed an issue where expanding the results of a Survey displayed the incorrect Survey title. * **Portal:** Fixed an issue where the response rate metric for Surveys was not showing the correct calculation. * **Portal:** Fixed an issue where the email invitation option was not being triggered in the user invite modal. * **Portal:** Fixed an issue where the "draft" status for Guides was not disappearing from the Portal after a Guide had been published. * **Portal:** Fixed an issue where the count of imported users who had not received an invitation email was not updated after invitations were sent. * **Portal:** Fixed an issue where the publish toggle on Guides when accessed via search did not change when clicked. * **Portal:** Fixed an issue where a URL was not being displayed in the URL table on the Engagement page of HEART. * **Portal:** Fixed an issue where the date picker for Messages and User Segments was not saving the date selected. * **Editor:** Fixed an issue that prevented an image from being applied to all languages if "Apply to all languages" was enabled. * **Editor:** Fixed an issue causing the Userlane Editor not to load on an underlying application. * **Editor:** Guides are now shown in the correct language if linked to a Tooltip. --- # 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/2024/improvements-and-fixes-may-2024.md?ask=&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.