silverstripe-framework/docs/en/changelogs/3.1.0.md
Ingo Schommer a3295e2a37 API File->canEdit() returns TRUE by default (not checking CMS perms)
This is a measure to support form fields and controllers
interacting with files in different contexts,
for example an UploadField used in a ModelAdmin,
or a website frontend. The check for 'CMS_ACCESS_AssetAdmin'
was too restricting. This wasn't a problem in 2.x simply because
the old FileField/Upload classes didn't respect File->can*()
permissions.
2012-10-12 15:42:06 +02:00

917 B

3.1.0 (unreleased)

Overview

Upgrading

  • Removed SiteTree.MetaTitle and SiteTree.MetaKeywords since they are irrelevant in terms of SEO (1, 2) and general page informancy
  • Deprecated Profiler class, use third-party solutions like xhprof
  • Removed defunct or unnecessary debug GET parameters: debug_profile, debug_memory, profile_trace, debug_javascript, debug_behaviour
  • Removed Member_ProfileForm, use CMSProfileController instead
  • SiteTree::$nested_urls enabled by default. To disable, call SiteTree::disable_nested_urls().
  • Removed CMS permission checks from File->canEdit() and File->canDelete(). If you have unsecured controllers relying on these permissions, please override them through a DataExtension.