- Issue created by @aanjaneyam
- π¬π§United Kingdom aanjaneyam
Just wondering if we also have to run the following commands as they are not described in the documentation like other bootstrap themes like Barrio do.
npm install gulp compile
- π¬π§United Kingdom aanjaneyam
By current version you mean version 6.0.0? If it is then is it possible to upgrade from 5.2.1 to 6.0.0 or it will need a fresh install.
- π¬π§United Kingdom aanjaneyam
Version 6.0.0 is still in beta. Is there anything we could do to resolve the issue in the current version 5.2.1.
- πΊπΈUnited States jimmb
I have done a fresh install of DXPR 6.0 as per https://dxpr.com/hc/documentation/learn-dxpr-theme/low-code-theme-custom...
And then added a sub-theme as per https://dxpr.com/documentation/creating-dxpr-theme-drupal-9-subtheme#Use...
And now when viewing /web/themes/custom/company_dxpr_theme/css/ --> the "dxpr_theme_subtheme.css" file is empty. So it does look to me like this bug has not been fixed in 6.0.0 ...
Another thing that's odd is that the custom CSS file name is different than the custom subtheme's machine name. For example, the custom subtheme is named: company_dxpr_theme
And yet the actual CSS file within that directory is called: dxpr_theme_subtheme.css
Shouldn't this be: company_dxpr_theme.css (?)
I don't really have a strong opinion on it, but was thinking maybe this is part of the reason why this bug is happening. At the least, it seems worth mentioning that it *seems* like the custom subtheme's CSS file should be named consistently with the name of the custom subtheme itself.
- Status changed to Closed: works as designed
12 days ago 6:14am 5 September 2025 - π§π¦Bosnia and Herzegovina drale01 Sarajevo
This is not a bug.
dxpr_theme_subtheme.css
is intended only for manual custom styles and is not written to by Theme Settings.
Theme Settings generate a separate file insites/default/files/dxpr_theme/css/themesettings-<subtheme>.css
, which works as expected.We already updated the
README.md
in version 6.0.7 and will update the rest of the documentation accordingly. Now that this issue is closed, please review the contribution record.
As a contributor, attribute any organization helped you, or if you volunteered your own time.
Maintainers, please credit people who helped resolve this issue.