Key highlights
- The sitemap is built in the background by an hourly scheduled task.
- Record areas print their HTML: a form or other record chosen in a layout area renders when the area is printed.
What’s new in Core dna Platform 2026.1.3
Scheduled Sitemap Generation and Bug Fixes
Sitemaps are generated by a scheduled background worker, and record-type areas print their HTML directly in templates.
Changes in behaviour
- Sitemap:
/sitemap.xmlserves the file the task last built. When there is no recent file, it answers202 Acceptedwith no body and queues a build, and the sitemap is served on a later request.
The sitemap is built in the background
The sitemap is now built by a scheduled task, Generate static sitemap XML, which runs every hour, instead of being generated while a visitor or a crawler waits. /sitemap.xml serves the last file built. The task is listed with the other scheduled tasks, where it can also be run straight away.
Record areas print their HTML
When a layout area holds a record, such as a form chosen with a record picker, printing the area now outputs the record's rendered HTML, while its properties stay available. The area shorthand is enough to place the form on a page:
Template code
{* The form chosen in the page's form area *}
{$page->form}{# The form chosen in the page's form area #}
{{ page.form }}Other improvements and bug fixes
- Improved performance and reduced memory usage when creating or updating records with a large number of related records, such as product categories with many items.
- Fixed an issue where removing all selections from a multi-select field did not properly clear the saved values.
- The autosave status message is now displayed in the page header when the sidebar is collapsed, ensuring it remains visible at all times.
- Fixed an issue in the environments configuration where site filtering could behave incorrectly when no specific site was selected.
Go deeper
Was this page helpful?
Your answer goes to the docs team.