Skip to content

Updated to CMS 6 / 6.2#75

Open
StevenPaw wants to merge 8 commits into
Rhym:masterfrom
StevenPaw:master
Open

Updated to CMS 6 / 6.2#75
StevenPaw wants to merge 8 commits into
Rhym:masterfrom
StevenPaw:master

Conversation

@StevenPaw

Copy link
Copy Markdown

Updated Classnames, changed init to OnInit and cleaned up the code a bit for usage in Silverstripe CMS 6.0

@thats4shaw

Copy link
Copy Markdown
Contributor

This works great apart from the grouped menu functionality no longer working.

Some inspiration can probably be gleaned from https://github.com/bigfork/silverstripe-grouped-cms-menu-fork in regards to the restoration of the javascript removed from core.

@rosis-sharma-trainor

Copy link
Copy Markdown

I’ve opened a pull request on the forked repository that addresses the grouped menu issue. @StevenPaw Please take a look: StevenPaw#1.

@StevenPaw

Copy link
Copy Markdown
Author

The pull request of @rosis-sharma-trainor was approved and now the grouped menus also work properly again.

@ntd

ntd commented Apr 20, 2026

Copy link
Copy Markdown

Thank your for your work!

Using Silverstripe 6.2.0 without CMS and your master branch (ac9a5ed), I'm experiencing padding issues. The two main problems are:

  1. the login link is padded differently than the rest
  2. .cms-menu__list li.opened a has a different padding-left (5px vs 26px)

In my YAML I'm just customizing colors, i.e.:

SilverStripe\Admin\LeftAndMain:
  cms_background: '#008a00'
  cms_border_color: '#368b39'
  cms_color: '#fff'
  cms_hover_background: '#007a00'
  cms_hover_color: currentColor
  cms_active_background: '#006a00'
  cms_active_color: currentColor
  cms_drawer_background: '#1a883e'
  cms_drawer_color: currentColor
  cms_icon_color: currentColor

Here are the unbranded vs branded screenshots:
paddings

I'm just wondering if I'm the only one with those issues.

@thats4shaw

Copy link
Copy Markdown
Contributor

@ntd there were some changes that came through in 6.2.0 in regards to CMS menu.

The below will work around it:

// The SS admin CSS sets padding-left: 5px on all .opened a descendants
// (specificity 0,2,2), overriding the cms-theme's padding (0,1,1).
// This collapses text into icons. Restore proper padding for both
// the parent group link and the child items inside.
.cms-menu__list .branded-menu__list-item.opened > a {
  padding-left: 2rem !important;
}

.cms-menu__list .branded-menu__list-item.opened .branded-menu--child a {
  padding-left: 2.5rem !important;
}

// Remove the default left border on opened/current menu items.
.cms-menu__list .opened {
  border-left: none !important;
}

@ntd

ntd commented Apr 21, 2026

Copy link
Copy Markdown

The below will work around it:
...

Yes, that fixes the second problem (the wrong left padding of the selected item).

@StevenPaw

Copy link
Copy Markdown
Author

I added some changes today because the pull request haven't been answered yet and there were some requests from other people for a switch to display or not display the cms info menu on the bottom left. While at it, i also fixed the wrong spacing and made the login info a bit smaller than the other menu items to make it visible different from modeladmins. This version now works with Silverstripe 6.2.
I hope this helps ^^

@StevenPaw StevenPaw changed the title Updated to CMS 6 Updated to CMS 6 / 6.2 Apr 27, 2026
@StevenPaw

Copy link
Copy Markdown
Author

A small headsup, because this module seems to be abandoned and I can't get a hold of Rhym. I created my own fork of this module with some new features and small design changes, that work with Silverstripe CMS 6.2:
https://github.com/StevenPaw/silverstripe-cms-backend-theme

Feel free to use that and give Feedback on there if you need anything else

@stevie-mayhew

Copy link
Copy Markdown
Collaborator

Hey @StevenPaw - I have access to be able to merge things here if you want me to do that to keep it all in this repo? I can try reach out to @Rhym and see if he is able to add you as a maintainer?

@StevenPaw

Copy link
Copy Markdown
Author

Hi @stevie-mayhew , thanks for the offering but I think I will continue to also add new features to the new branch and support that myself because it will drift a bit in another direction as the original module I think

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants