- Issue created by @bsnodgrass
I have a project with a local dev environment and a production environment using 6.0.0-beta1. Originally we had installed 5.1 version on this project and have upgraded a number of times, perhaps this is an issue resulting from multiple upgrades of the theme. This included use of the core Color module as well as the contrib Color module (now uninstalled).
We ran into an issue where css changes were not being fully deployed to the production environment as expected.
We verified the theme config settings were deployed using drush cim and all settings in the UI were matching between local development and production. However, the changed settings were not applied.
Upon further investigation, we found a "themesettings-dxpr_theme.css" file located in web/sites/default/files/dxpr_theme/css/
This file had the same permissions as other files in that folder. Once we modified these permissions we were able to save the dxpr-theme
and have our theme configuration work as expected.
I may manually install a fresh instance of the theme to see if I have the same result and to compare what I have to a clean install.
The Theme README.md states the following:
[WARNING2] Save theme settings form after updating theme CSS
Because DXPR Theme integrates with the color module, changes to its CSS may
not immediately take effect.
When the theme is configured with custom colors in the theme settings form
the color module will save a copy of the recolored theme CSS files inside
the Drupal files folder. When updating the theme CSS files in the theme
folder these changes might not take effect because the browser is loading
the copies of the theme's CSS files from the files folder. To fix this you
have to save the theme settings form so that the color module will create
new copies of the theme's CSS files that include your latest changes.
Now that the color module is no longer used, is it necessary to have this file (themesettings-dxpr_theme.css) or other files saved in sites/default/files/?
Active
6.0
Code