Skip to content

Commit

Permalink
DOC Document new parameter for DataObject::write() (#499)
Browse files Browse the repository at this point in the history
  • Loading branch information
GuySartorelli authored Apr 18, 2024
1 parent 2e2ab97 commit 77c3210
Showing 1 changed file with 16 additions and 2 deletions.
18 changes: 16 additions & 2 deletions en/08_Changelogs/6.0.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,16 @@ title: 6.0.0 (unreleased)

## Overview

- [Run `CanonicalURLMiddleware` in all environments by default](#url-middleware)
- [Features and enhancements](#features-and-enhancements)
- [Run `CanonicalURLMiddleware` in all environments by default](#url-middleware)
- [Other new features](#other-new-features)
- [Bug fixes](#bug-fixes)
- [API changes](#api-changes)
- [General changes](#api-general)

## Run `CanonicalURLMiddleware` in all environments by default {#url-middleware}
## Features and enhancements

### Run `CanonicalURLMiddleware` in all environments by default {#url-middleware}

In Silverstripe CMS 5 [`CanonicalURLMiddleware`](api:SilverStripe\Control\Middleware\CanonicalURLMiddleware) only runs in production by default. This lead to issues with `fetch` and APIs behaving differently in production environments to development. Silverstripe 6.0 changes this default to run the rules in `dev`, `test`, and `live` by default.

Expand All @@ -24,10 +30,18 @@ CanonicalURLMiddleware::singleton()->setEnabledEnvs([
]);
```

### Other new features

## Bug fixes

This release includes a number of bug fixes to improve a broad range of areas. Check the change logs for full details of these fixes split by module. Thank you to the community members that helped contribute these fixes as part of the release!

## API changes

### General changes {#api-general}

- [`DataObject::write()`](api:SilverStripe\ORM\DataObject::write()) has a new boolean `$skipValidation` parameter. This can be useful for scenarios where you want to automatically create a new record with no data initially without restricting how developers can set up their validation rules.

<!--- Changes below this line will be automatically regenerated -->

<!--- Changes above this line will be automatically regenerated -->

0 comments on commit 77c3210

Please sign in to comment.