New Features

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

  1. Separate classes for form fields and their holders.

    I feel confident that, in 2019, the status quo of CSS frameworks is that they expect different classes to be on "div" elements and "input" elements. In the case of SilverStripe, currently, the "FormField::addExtraClass()" method blindly inserts the classes on both the form field (an "input" element) and its holder (a "div" element). Wrong. The classes of the holder should be controlled by a new method, "FormField::addExtraHolderClass()" or something similar. And, before you ask, yes, I am aware that there is a method "FormField::setFieldHolderTemplate()." The problem with this method is that it requires separate templates for something as trivial as…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. HTTP 402 status code

    It would be useful to be able to respond to requests for payment using an HTTP 402 "Payment Required". It's part of HTTP 1.1 (https://tools.ietf.org/html/rfc7231) but "reserved for future use". This doesn't necessarily stop systems employing it, as the Wikipedia page illustrates: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Ability to move mutiple pages in the site tree.

    Currently can only drag and drop one page at a time in SS4, in-order to change it's location in the sitetree. SS4 should support the functionality to select multiple pages and move them together to a different location in the sitetree.

    Note - In SS2, a checkbox was available to select multiple pages in-order to move them.

    52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Template blocks/sections with inheritance

    We should implement block/section functionality seen in other templating languages so that we can reduce the instances of repeated code when there are variations of a template that cannot be shared due to the inherent limitations of includes.

    - Twig: https://twig.symfony.com/doc/2.x/tags/extends.html
    - Blade: https://laravel.com/docs/5.0/templates

    While the advantages of blocks are likely already known, I’ll explain my use case. There are many instances in my case where I could have HTML code that must be repeated around includes which could otherwise be inverted such that the typically included code is embedded into the template and the variable components would instead be…

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Keeping data safe

    What about blocking save/publish buttons while upload field processing files?

    If user will click on it before processing was finished it will make him upload files again. The worst thing when u have carefully selected bunch of files from long file listing to upload. The same UX issue with GridField editable rows.

    Also I guess it will be nice if CMS will store fields content into local storage and restore it after refreshing the page in case user accidentally closed browser window

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Stop using the base tag

    Hello,
    using the base tag should not be needed and it could create problems when using anchors, especially when they are used to refer to SVG image resources: https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/xlink:href

    At the moment we successfully managed to use SilverStripe without the base tag but that involved extending the Page class with a onBeforeWrite event that appended the absolute path to the src="assets/..." uri generated by tinymce.

    65 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Speeding up: Increase the use of caches and cache warmers

    Silverstripe by nature is very slow compared to other frameworks or CMS however this mostly boils down to the amount of queries a mid to large sized page needs and the level of complexity a template can have.

    The is already partially solved with partial caches and rendering most of the template in the silverstripe-cache folder however this can be further improved through the use of memcached / APC / any other caching solution.

    It would be really nice if a query result could be stored in APC for x amount of time so that when requested again Silverstripe can…

    44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. More user-friendly set-up of websites

    Right now, a non-developer has a hard time to create the desired website with Silverstripe.
    One needs to enter console-commands (composer) to install themes or even new page types.
    A web-interface should be created to provide the possibilities to extend the default installation with themes and add-ons.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Ability to submit user feedback from the CMS

    As part of this usability document (http://www.silverstripe.org/assets/2014/Reports/Usability-report-on-SilverStripe-CMS-Main-actions-and-page-states.pdf), it has become clear that users are keen to voice feedback about the CMS but are unsure how to do this, so I would love to see a feedback form inside the CMS which will allow users to submit their pain points and then have a hosted area for everyone to view and sort issues based on popularity etc. or other metrics. This could be used to create future uservoice issues especially for CMS users. Their email would be optional and would have to be hidden from the feedback but could…

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. iOS / Android App

    Would be a great selling point to have an iOS / Android app for using the CMS.

    It would pretty much be a wrapper to launch the web-based CMS as it would never be able to cater for the endless possibilities, but it would be nice to be able to store multiple websites with logins to make it feel like it was an actual app.

    Would tie in with the Responsive CMS suggestion here http://silverstripe.uservoice.com/forums/251266-new-features/suggestions/6196153-responsive-cms

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Deactivate user feature

    Right now, it's difficult to deactivate an account but not delete it. You can delete them from all user groups but this doesn't suppress log-in functionality.

    One use-case is where you want to remove someone's access but retain history of their edits, etc. At any rate, an activate/deactivate feature is pretty common in other user management systems.

    Group listings in the CMS might hide deactivated accounts by default, and/or they might be highlighted differently.

    Log-in attempts should say "Sorry, your account has been deactivated".

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. ability to choose redirect destination from treedropdownfield in the module silverstripe/silverstripe-redirectedurls

    adding a treedropdownfield to choose destination for redirect or replacing the textfield for redirection in this module would result in a better UX, but also keep it stable when for instance pagenames are changed afterwards.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. CMS UI optimised for mobile devices

    With the 4.0 release, we've made the CMS UI work well on smaller screen sizes ("responsive"). Some UX flows have been simplified with less available screen space (e.g. moving buttons into a "more options" group). But overall, it's still the same CMS as you'd use on the desktop. That's great for power users since they can access the full set of functionality. But it tends to get in the way if you just want to perform a quick action on the go. A few examples:

    - Receive a Slack notification about a blog post draft. Easily review the draft and…

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. SS4 - React-based SiteTree editor

    A much nicer, user friendlier, preferrably React-based SiteTree editor. Dragging&dropping, ability to easily nest multiple levels, immediate visual feedback if a drag-move is not permitted. Big one, not being able to drag a page that is "locked". Handled with callbacks/Graphql and in React it would sport way better UX, handling edge cases & permissions to disable/deactivate blocks and prevent certain actions etc. Something like http://webcloud.se/react-sortable/ or building upon the concept of the WordPress menu editor.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Use ReactJS/GraphQL for all CMS interfaces

    With the 4.0 release, we've redeveloped the "assets" section in ReactJS, and created a new "campaigns" section on the same foundations. We've previously blogged about why that's a good idea: https://www.silverstripe.org/blog/cutting-through-the-noise-why-silverstripe-4-will-use-reactjs/

    Major sections like "pages" or "security" are still based on jQuery/Entwine logic, with minor bits of ReactJS sprinkled in (e.g. the new TreeDropdownField ReactJS component). In order to provide a consistent developer experience in the CMS, we need to finish this transition.

    The CMS UI has often been heavily customised through jQuery/Entwine, so this transition will require many modules to rewrite view logic. It's important to ensure that the…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Help to pass on unmaintained modules

    I have built a lot of SilverStripe modules, however I'm not doing nearly as much SilverStripe development as I used to, so I'm not as inclined to maintain my add-ons. I still get a fair few pull requests and issues, which can often go ignored for a long time.

    https://github.com/burnbright

    It would be great if there was a place/person I could pass these to so that they can easily be picked up by people that are keen to maintain them.

    It would help if I can simply flag which modules I would like to open up for new maintainer(s) to…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Include SVG upload support.

    Nowdays it is important to use SVGs for logos and other assets. It would be awesome to have it , please check this https://github.com/restruct/silverstripe-svg-images, they did a pretty good job, but it kinda needs to hack the CMS to get it working for all the file upload fields.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow to resize images before storing them in assets

    gd2 is memory hungry and trying to manipulate an image big enough can easily crash a small webserver. I have seen that many times on different servers, and you can meet this issue by just calling getimagesize().

    At the end you will end up with a blob in your assets that cannot be manipulated. It will also crash the CMS whenever SilverStripe tries to make a thumbnail. And no matter what you say to the client: he will continue to upload his 4000x6000 raw JPEGs directly from the camera.

    My propose is to allow to customise the default behavior of…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Ability to "fully delete" Page from Archive

    Currently a page can only go through published, draft and archived states. Technically it always will exist in the database after initially being created with no real complete removal. This can eventually be quite cumbersome if you have a large website with situations where assets and other relations that need to be cleaned up after a while manually by the user.

    Here is a proposed full list of transitions that a page can go through :

    - Published
    - Draft
    - Archived (we are here)
    - Fully deleted (doesn't exist in the database in any form).

    Additionally, I think this…

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Module and Theme Marketplace

    I see a very long and bright future for Silverstripe. I wonder if there's a need for a module&theme marketplace, a combination of https://atmospherejs.com and the Shopify marketplace for modules & services.

    While the market may be small, I see this could be a cool way for talented SS developers to create modules as packages which small clients could rent e.g. on a monthly basis. An awesome gallery module or a special social data feed importer module, or whatever. You get the point. Users could maybe choose between renting and purchasing a module. Developers could have a free and a…

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

New Features

Feedback and Knowledge Base