Skip to content

Deprecate base tag and update changelog for 6.2.0 #876

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sminnee wants to merge 1 commit into
base: 6
Choose a base branch
from
Open

Deprecate base tag and update changelog for 6.2.0 #876

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions en/08_Changelogs/6.2.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,6 +205,22 @@ The "Campaigns" admin section which is added through [`silverstripe/campaign-adm

You can filter by the name and description of the campaign, its status, and the publish date. This is all powered by [`searchable_fields`](/developer_guides/model/scaffolding/#searchable-fields) configuration for the [`ChangeSet`](api:SilverStripe\Versioned\ChangeSet) class, so you can customise the search fields by changing that configuration if you want to.

### Good bye, base tag

The `<base>` tag that Silverstripe has long since used can cause issues, for example with server configuration, reverse proxies, and fragment links. It is not actually necessary for Silverstripe to function. In this release, we have fixed the remaining bugs in the admin UI that necessitated the base tag, and have deprecated it.

The admin UI still includes the base tag by default, and will do so until 7.0 is released. You can remove that with the following configuration:

```yml
SilverStripe\\View\\SSViewer:
enable_base_tag: false
rewrite_hash_links: false
```

We encourage everyone to remove the <% base_tag %> directive from their templates, and to make this configuration change.

**Note:** the AdminRootController::admin_url() function now returns URLs of the form "/admin/pages" (or "/mysite/admin/pages" if you site runs in a subfolder) instead of "admin/pages". This will not affect the behaviour of modules that make use of it, unless they are doing string-matching on the value.

### Other new features and enhancements {#other-new}

- A new [`ChildFieldManager`](api:SilverStripe\Forms\ChildFieldManager) interface has been added to allow a parent form field to strictly control its children, but still allow setting/getting values for those fields let them handle AJAX requests. See [`ChildFieldManager` docs](/developer_guides/forms/field_types/childfieldmanager/) for more details.
Expand Down Expand Up @@ -249,6 +265,7 @@ It's best practice to avoid using deprecated code where possible, but sometimes
- The [`UnsavedRelationList::getIDList()`](api:SilverStripe\ORM\UnsavedRelationList::getIDList()) method has been deprecated. Use `$list->column('ID')` instead.
- The `IconHOC` react component has been deprecated and will be removed in a future major release without a replacement. The `Button` component's `icon` prop will still remain.
- The [`FieldList::dataFields()`](api:SilverStripe\Forms\FieldList::dataFields()) method has been deprecated. Use[`FieldList::getDataFields()`](api:SilverStripe\Forms\FieldList::getDataFields()) instead.
- Use of the `<% base_tag %>` has been deprecated, as the base tag is not necessary for Silverstripe to work.

## Bug fixes

Expand Down
Loading