2025.04.17 - Release Notes
Release | |
Date | Apr 17, 2025 |
Version | 2025.04.17 |
Description |
|
Contributors | @Alexander Demeshchik@Vadzim Bura@Maksim Hladki@Nastassia Kaupayeva@Alexey Patsovsky@Aliaksandr Baravikou@Jack Canavan-Gosselin@Dzmitry Shyrai (Unlicensed)@Anastasiya Kruglaya@Nick Krivitsky (Unlicensed)@Yaroslav Kustenko@Hardzei Stakhavets |
Issue | Public Description |
|---|---|
Events using images previously set as Newsletter title images now load correctly on Yale Medicine pages without triggering errors. | |
Fixed a problem where an error was frequently returned while activating users from IDR, even if the user was added successfully. | |
Disabled caching for Digital Signage content previews to ensure the preview reflects the latest edits. | |
Fixed a problem where publication details pages were appearing as search engine results on random YSM sub-sites. | |
Logs for the request body are now captured to support better diagnostics and analytics. | |
The "AssociateDanglingUsers" call now updates users in batches of 500 to prevent exceeding argument limits and ensure reliable syncing between modules. | |
We are optimizing the database performance for the Feeds feature by ensuring that all relevant data entities using page names are indexed. This will help speed up the process of retrieving data based on page names, improving the overall responsiveness and efficiency of the system. | |
Update project dependencies to resolve security concerns and implement modern authentication system for Feed clients. This update ensures better security compliance and improved client authentication flows. | |
Update project dependencies to resolve security concerns and implement modern authentication system for Feed clients. This update ensures better security compliance and improved client authentication flows. | |
Update project dependencies to resolve security concerns and implement modern authentication system for Feed clients. This update ensures better security compliance and improved client authentication flows. | |
Fixed a problem where organization usage in particular sections of the Yale Medicine website is not reflected in Beatrix. | |
Upgraded YM applications, tools, and hosting platforms to Node.js 22 to ensure improved security, better performance, and ongoing support. | |
Update all NuGet packages in the BTX Sync project to the latest stable versions to improve security, performance, and compatibility. Ensure the application builds successfully and passes all tests after the updates. | |
Added a date filter to the "Your Articles" page in Beatrix. | |
Fixed a problem with a specific profile being suppressed from search engine results. | |
Fixed a problem where privacy policy pages could not be published | |
Inactive user data is no longer included in publication listings. | |
Added the ability to copy, move, publish, unpublish, or delete a subset of pages from one directory to another in Beatrix CMS. | |
Added the ability to copy, move, or delete a subset of content items from one folder to another in Beatrix CMS. | |
A preview button is now available to review the appearance of a publication summary before publishing it to the live website. | |
Clinical Trial Highlights now display a "Closed to Accrual" status when applicable, directing users to a details page that indicates the trial is no longer accepting volunteers. The details page removes volunteering content and includes a clear "Not Accepting Volunteers" notice in the side column for better transparency. | |
Updated code framework to latest version for security and stability. | |
In the scope of this ticket, internal server error appearing on Profile Publication filtering by specific concepts with special symbols should be fixed. | |
We should make changes on the http://yalemedicine.org site to prevent serving profiles for people who are not Yale Medicine employees. | |
An issue has been identified on the publication search page where a Solr exception occurs when ordering by the featured publication index. Although the data is returned correctly, the error affects system logs and monitoring, making it more challenging to detect other issues. The root cause is being investigated to improve functionality and system reliability. | |
Users now see a warning message before removing themselves from a news article, ensuring they are aware of the action's impact. This helps prevent accidental removals and preserves their association with the article when needed. | |
Users will now be prevented from adding the same PubMed publication to a mentoring item multiple times, ensuring data accuracy and avoiding duplication in mentoring profiles. |