innoweb / silverstripe-dms
Adds a Document Management System to SilverStripe
Installs: 82
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 2
Forks: 52
Type:silverstripe-vendormodule
Requires
- bummzack/sortablefile: ^2.2
- silverstripe/cms: ^4.1 || ^5
- symbiote/silverstripe-gridfieldextensions: ^3 || ^4
- unclecheese/display-logic: ^2 || ^3
- dev-master
- 3.3.0
- 3.2.3
- 3.2.2
- 3.2.1
- 3.2.0
- 3.1.0
- 3.0.4
- 3.0.3
- 3.0.2
- 3.0.1
- 3.0.0
- 2.3.0
- 2.2.x-dev
- 2.2.0
- 2.1.x-dev
- 2.1.4
- 2.1.3
- 2.1.2
- 2.1.1
- 2.1.0
- 2.0.x-dev
- 2.0.6
- 2.0.5
- 2.0.4
- 2.0.3
- 2.0.2
- 2.0.1
- 2.0.0
- 2.0.0-beta1
- 1.x-dev
- 1.4.x-dev
- 1.4.3
- 1.4.2
- 1.4.1
- 1.4.0
- 1.3.x-dev
- v1.3.0
- 1.2.x-dev
- v1.2.0
- 1.1.x-dev
- v1.1.1
- v1.1.0
- v1.0.0
This package is auto-updated.
Last update: 2024-11-11 01:52:35 UTC
README
Overview
This is a very simplified version of the Silverstripe 3 DMS module for Silverstripe 4 and 5.
It uses the standard Silverstripe File objects instead fo the custom storage management of the SS3 version.
Taxonomy has been removed as a dependency. This can be implemented on a project basis if needed.
Features
- Relation of documents to pages
- Management and upload of documents within a page context in the CMS
- Based on standard Silverstripe files
- Legacy download controller for SS3 document links
Requirements
SilverStripe CMS ^4.1 or ^5, see composer.json
Installation
Install the module using composer:
composer require innoweb/silverstripe-dms dev-master
Then run dev/build.
Upgrading
A first dev/build will move all old DMS tables to _obsolete_.
There is an upgrade task dev/tasks/dms-upgrade available that will migrate the old documents to the new structures.
Issues
Document versions are not being migrated over at the moment. The default versioning of files doesn't keep the physical versions of the files. That can be enabled with:
SilverStripe\Assets\File:
keep_archived_assets: true
But then this would not only be for DMS documents but for all files. PRs welcome.