I have the same problem. Tried to hide fields for "Full content" display mode. After saving I get the message "Status message
Your settings have been saved." but the fields are still listed in the "Content" section instead of the "Disabled" section.
I use/run Drupal 11.1.5, once based/built on a Drupal CMS RC2 installation. Then always updated through Composer.
I also use Display Suite with the "1 col layout" and Gin as a admin theme.
I tried I with using a different admin theme (Claro, but the the saving still would not work) and switched Display Suite layouts but no difference here too.
Whats holding this back? It's quite frustrating to see no progress here since a long time. In general, if Drupal "finally" wants to attract Frontend people the frontend topics should also be addressed like any other issue. Since my D6 days, the frontend has always been the stepchild ... I don't want to rant, but I'm actually a bit frustrated since I came back to Drupal after a while being away (for reasons) and things seem to be the same as they were in Drupal Frontendlandia ... marketing says it all changed but it unfortunately hasn't. Don't get me wrong and this is probably the wrong place to address this but on the otherhand it's also a core thing/theme where alot of effort already went into so why not reusing this great work.
Is it already possible to use/clone Olivero as a starterkit theme? Maybe with a patch since it hasn't made it into Drupal 11 yet.
For Drupal CMS there is the drupal_cms_olivero
theme which itself uses Olivero as a base theme and which is not recommended like the module itself states in drupal_cms_olivero.info.yml
.
# This theme is marked as @internal. It is intended to evolve and change over minor releases.
# Although we are sub-theming Olivero within Drupal CMS, sub-theming Olivero is
# explicitly not supported by Drupal core. This is intended as a stop-gap
# measure to provide great looking content types and components before a more
# robust design system can be implemented.
What is the proposed solution for Drupal CMS and Olivero and the build setup (CSS/JS/img optim) once Olivero got actually cloned? I would like to reuse the the 'menu' with it's a11y features.
Thanks for guidance.
Will there be a Drupal 11 release / version in the foreseeable future? Thanks for clearing things up!
rm -rf web/profiles/drupal_cms_installer/cache
works fine like mentioned in
#3
🐛
Installer is broken in RC2 since release of 11.1.1
Active
by @siramsay