New Features

Please add your suggestions for new SilverStripe CMS & Framework features (Note: bugs should be logged over in GitHub).

A new feature for SilverStripe should be ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Asset Abstraction

    (See https://github.com/silverstripe/silverstripe-framework/issues/3792 for full details).

    *Motivation*

    The driver for this change is solving the following problems we keep encountering in practice:

    * changing root path for asset storage
    * support Amazon S3 as a backend
    * support backends for sites residing on multiple servers (clustered sites)
    * have files versioned
    * have files with workflow
    * be able to model private files that do not appear in the Files & Images section

    *Proposal*

    To solve these problems we propose to:

    1. Create a backend-independent way of referring to files in the Framework.
    2. "Degrade" files from entities in their own…

    92 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
    • Have SilverStripe classes be in namespaces

      Right now all SilverStripe classes are just in the global namespace. We decided 5.3 would be a reasonable requirement too late in the 3.x cycle to change this.

      However it's holding us back, and we can't really wait for 4.x to fix it.

      We should move all cms & framework classes into appropriate namespaces (ideally PSR-0 compliant, although this wouldn't include making PSR-0 actually work, we'd still need the SilverStripe bootstrap, at least for now).

      We'd need to include a tool that scanned projects for class usages & automatically added the use statements to the top of all files for…

      77 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
      • Update TinyMCE to 4.x

        Update TinyMCE to 4.x. This will bring a far more modern user experience for content authors and general CMS users.

        111 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
        • 15 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
          • Themes should be more powerful

            They should be able to inherit from other themes, and define codeless page types

            42 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)
              You have left! (?) (thinking…)
            • Apply versioning and draft/published to files

              Right now, the draft/published system doesn't apply to files: any files that you upload are available straight-away, and file replacements can't be staged and tested.

              For many people, this is acceptable as the draft/published system is kind of an optional, bonus feature. Others don't realise this limitation is there and are shocked when they find out. And for some people it makes using SilverStripe a non-starter.

              Admittedly, this is generally only an issue to larger organisations, however, SilverStripe has always been designed to let web developers create more tailored systems, and so thinking about the needs of people who care…

              36 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)
                You have left! (?) (thinking…)
              • Don't see your idea?

              New Features

              Feedback and Knowledge Base