Skip to content

CMS 6 regression: silverstripe/cms shouldn't be a dependency #230

Description

@3Dgoo

Module version(s) affected

6

Description

As of version 6 silverstripe/cms is a requirement of this package. This appears to be because the reports that lived in silverstripe/cms have been moved here to silverstripe/reports.

This has the consequence of, if there is a project that does not use silverstripe/cms, but does use silverstripe/reports, now silverstripe/cms is forced upon the project.

How to reproduce

Install a new Silverstripe project with just framework and reports. CMS will also be installed.

Possible Solution

Can we modify any reports that rely on silverstripe/cms being disabled when that module isn't installed, and then remove silverstripe/cms from the requirements.

Additional Context

No response

Validations

  • Check that there isn't already an issue that reports the same bug
  • Double check that your reproduction steps work in a fresh installation of silverstripe/installer (with any code examples you've provided)

Metadata

Metadata

Assignees

No one assigned

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions