Stark theme actions are not consistent as other themes on non-live workspaces

Created on 27 November 2020, almost 4 years ago
Updated 12 January 2024, 11 months ago

Problem/Motivation

Expected result to enable or uninstall a theme on non-live workspaces:

* The action shall be blocked.
* A message saying "This form can only be submitted in the default workspace."

Test results:

* Claro - good
* Olivero - good
* Stark - error

Steps to reproduce

1. Fresh install Drupal core(9.1.0-rc3) with `Workspaces` module enabled
2. Switch to `Stage` workspace
3. Go to `admin/appearance` and find theme `Stark 9.1.0-rc3`, then click `Install and set as default`
4. A runtime exception will be triggered with 500 error (RuntimeException: This entity can only be saved in the default workspace. in Drupal\workspaces\EntityOperations->entityPresave() (line 124 of core/modules/workspaces/src/EntityOperations.php).)
5. Sometimes you can install the theme, but when you try to uninstall the theme, a runtime exception will be triggered.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Closed: outdated

Version

9.5

Component
Stark 

Last updated 11 months ago

Created by

🇦🇺Australia pandaski

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇳🇿New Zealand quietone

    @pandaski, thanks for reporting this problem

    I tested this on a standard install of Drupal 11 using the steps in the issue summary. I was not able to reproduce the problem. Therefor, I am closing this as outdated.

Production build 0.71.5 2024