Every Core dna product, release by release, newest first. Each product ships on its own schedule.
Books, Custom Field Search and Bug Fixes
Books, units and book pages now work wherever pages do: in templates, site search, menus and the sitemap. The API can find records by a custom field's value, and the HTTP Request job action only calls public addresses.
$_query in templates, the criteria of Retrieve Records and Merge Files actions and filter fields in a site's .settings.json can return fewer records than before. Review jobs whose criteria combine filters on the same relation: a narrower result shows up as missing output, not as an error.is empty is now true for a layout area with no content, so a theme that relied on such an area counting as not empty takes its empty branch.Books, units and book pages now work in the same places as pages:
$_query.{* Every book, in the order set in the admin *}
{foreach $_query->findBy('Books\Entities\Book', [], ['position' => 'ASC']) as $book}
<a href="{$book->getFullPath()}">{$book->getName()|escape}</a>
{/foreach}{# Every book, in the order set in the admin #}
{% for book in _query.findBy('Books\\Entities\\Book', [], {'position': 'ASC'}) %}
<a href="{{ book.getFullPath() }}">{{ book.getName()|e }}</a>
{% endfor %}The API can now find records by the value of a named custom field: customFieldValues_customField_name names the field and customFieldValues_content_text gives the value. These are the elements of menu 1 whose icon field is coffee:
GET /cdna-api/menus/elements/1?customFieldValues_customField_name=icon&customFieldValues_content_text=coffee HTTP/1.1
Host: hub.coredna.com
Authorization: Bearer YOUR_ACCESS_TOKEN
Accept: application/jsonWhen several filters go through the same related records, they now all apply to the same related record. Before, each filter could match a different one, so a result could include records that did not meet the combined condition.
The HTTP Request action of a job now sends requests to public internet addresses only. Requests to localhost, private networks and internal hosting services are blocked, and every redirect is checked the same way. A blocked request fails the step at once, without retrying, and the step's output names the blocked host. Authorization and cookie headers are no longer passed on when a redirect leads to another host, and the timeout covers the whole redirect chain.
Textarea and Code areas now keep links and images exactly as entered; only Richtext areas convert them. In Richtext areas every link is tracked, not only the first, so each one keeps following the page it points at.
customFields now updates only the fields named in the request, and null empties a field. Image and file custom fields can now be written with an image or file id instead of returning a server error, and two validation errors that showed a raw translation key now show readable text.is empty test now returns true for layout areas with no content, such as an image area whose image was cleared or a text area saved blank. Themes that relied on these areas counting as not empty will now take their empty branch. Templates can also call the new isAreaBlank('areaName') method on pages, records and global components, and a site can set Globals.template.twig.blankObjects to false in its .settings.json to receive empty areas as null. The response cache should be flushed after changing this setting.Was this page helpful?
Your answer goes to the docs team.