10.1 - when "Aggregate CSS files" is checked new CSS is not loaded and is missing from sites/default/files/css

Can you please look at the browser console log for errors and post them here?

Do you use nginx? There were notes in the release notes about this if so.

Also adding a related issue

I have the exact same issue on a D10.1 installation. When aggregate css is checked, no new aggregated css files are created if existing (sites/default/files/css) are not deleted.

For example updating header css ends up in having pages previously browsed with the old style and pages browsed for the first time using the updated style.

Thanks for replies. Yes I am using nginx so it looks like the related issue mentioned by larowlan

My hack for now is that if I add new css to an existing file eg nav.css then the new css is ignored but if I rename the file such as newnav.css (and add this new file to mytheme.libraries.yml ) then the new css loads correctly.

@gbotis Are you using nginx?

@cilefen I meant to say there are no errors in the console

And I have now seen the same issue on a third 10.1 site.

Can anyone using nginx verify that the release notes information about adjusting the nginx configuration are accurate?

Our team ran into this issue earlier this week. Drupal was serving stale aggregated assets on a large multisite project serving ~20 sites, each with its own theme. After finding 🐛 Ensure that edge caches are busted on deployments for css/js aggregates Fixed , we decided to update the THEME.libraries.yml file in each site’s theme to either add or change the value of version for the libraries that have been updated since we updated the project to Drupal 10.1. This caused Drupal to serve updated aggregated assets and all sites now receive the expected styles in production.

Alright this seems a duplicate issue.

@cilefen No I am not using nginx