silverstripe-dms/docs/en/configuration.md
Robbie Averill e4bc553521 API Add document sets, remove *Page methods from DMSDocument
* Add 2.0.0 changelog
* Update DMSInterface and DMSDocumentInterface removing *page and adding getDocumentSetsByPage to DMSInterface
* Update use documentation and update unit tests

This commit changes the relationship from Pages has_many Documents to Pages has_many DocumentSets which are many_many to Documents. The upload field has been upated to attach documents to a set instead of a page, the tests updated and the DMSInterface and DMSDocumentInterface updated to be less relevant to pages and more relevant to document sets.
2017-05-09 13:04:29 +12:00

1.1 KiB

Configuration

The file location is set via the DMS::$dmsFolder static, and points to a location in the webroot.

Enable/disable documents/sets for a specific page type

If you don't need documents/document sets for a specific page type you can disable this with YAML configuration:

MyPageType:
  documents_enabled: false

Likewise, you could override a previously set configuration value by setting this back to true in a configuration file with a higher precedence.

Allowed extensions for DMS documents

By default the allowed extensions for DMS documents will come from the UploadField's allowed extesions list, and will have a customised list of extensions for DMS merged in. The base allowed_extensions is a site-wide configuration setting. See here for information on changing this.

To add extra allowed file extensions purely for DMS documents, you can update the YAML configuration property:

DMSDocumentAddController:
  allowed_extensions:
    - php
    - php5