silverstripe / sitewidecontent-report
Report of all pages and files across all subsites
Installs: 213 344
Dependents: 2
Suggesters: 1
Security: 0
Stars: 3
Watchers: 12
Forks: 13
Open Issues: 2
Type:silverstripe-vendormodule
Requires
- php: ^8.1
- silverstripe/cms: ^5
- silverstripe/reports: ^5
Requires (Dev)
Suggests
- silverstripe/subsites: In order to report across subsites, the subsites module must be installed
Conflicts
- silverstripe/reports: <4.11.0
- 5.x-dev
- 4.x-dev
- 4.3.x-dev
- 4.3.0
- 4.3.0-rc1
- 4.3.0-beta1
- 4.2.x-dev
- 4.2.1
- 4.2.0
- 4.2.0-rc1
- 4.2.0-beta1
- 4.1.x-dev
- 4.1.1
- 4.1.0
- 4.1.0-rc1
- 4.1.0-beta1
- 4.0.x-dev
- 4.0.1
- 4.0.0
- 4.0.0-rc1
- 4.0.0-beta1
- 3.x-dev
- 3.4.x-dev
- 3.4.2
- 3.4.1
- 3.4.0
- 3.4.0-rc1
- 3.4.0-beta1
- 3.3.x-dev
- 3.3.0
- 3.3.0-rc1
- 3.3.0-beta1
- 3.2.x-dev
- 3.2.0
- 3.2.0-rc1
- 3.2.0-beta1
- 3.1.x-dev
- 3.1.0
- 3.1.0-rc1
- 3.1.0-beta1
- 3.0.x-dev
- 3.0.4
- 3.0.3
- 3.0.2
- 3.0.1
- 3.0.0
- 3.0.0-beta1
- 2.0.x-dev
- 2.0.4
- 2.0.3
- 2.0.2
- 2.0.1
- 2.0.0
- 1.x-dev
- 1.0.0
This package is auto-updated.
Last update: 2024-11-04 00:31:37 UTC
README
Introduction
This module adds an "All content, page and files from across all subsites" report in the CMS, so that an administrator can get a quick overview of content across subsites in the parent site.
Installation
composer require silverstripe/sitewidecontent-report
Subsites Support
If the Subsites module is installed then an additional column will be added, allowing you to see which subsites this user can edit pages on.
To edit the permission to check for when filtering these subsites, you can update the
SilverStripe\Security\Member.subsite_description_permission
config to any other permission. By default this
is set to SITETREE_EDIT_ALL
.
Documentation
See the docs/en folder.
Versioning
This library follows Semver. According to Semver, you will be able to upgrade to any minor or patch version of this library without any breaking changes to the public API. Semver also requires that we clearly define the public API for this library.
All methods, with public
visibility, are part of the public API. All other methods are not part of the public API. Where possible, we'll try to keep protected
methods backwards-compatible in minor/patch versions, but if you're overriding methods then please test your work before upgrading.
Reporting Issues
Please create an issue for any bugs you've found, or features you're missing.