Skip to content
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

Jump to bottom

DOC Update preview docs with correct information #98

Merged
merged 1 commit into from
Mar 13, 2023
Merged

DOC Update preview docs with correct information #98

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
7 changes: 1 addition & 6 deletions en/02_Developer_Guides/15_Customising_the_Admin_Interface/04_Preview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,14 +57,9 @@ The format for that situation is always the same, with increasing complexity if
nesting `GridField`s. For the below examples it is assumed you aren't using nested
`GridField`s.

If your object belongs to a page, you can safely get away with returning `null` or an empty
string, as it won't be used. You can choose to return a valid edit link, but because of the
complexity of the way these links are generated it would be difficult to do so in a general,
reusable way.

[hint]
As of Silverstripe CMS 4.12.0, you can
[use CMSEditLinkExtension](/developer_guides/model/data_model_and_orm/managing_records#getting-an-edit-link).
[use CMSEditLinkExtension](/developer_guides/model/managing_records#getting-an-edit-link).

```php
namespace MyProject\Model;
Expand Down