0

In my Drupal 8 installation profile, I install a theme and a lot of configuration for it. I'm using Features to install blocks/settings/views for it, but when I enable the feature Drupal stops serving ANY CSS files on page loads.

I don't think it's an issue with features, because if I wait long enough, those files will be generated by Drupal and CSS files will load as normal, it's just that Drupal assumes those files already exist.

I have tried:
- drush cr
- clearing the cache manually in the UI
- all of the individual drush cc options
- deleting the contents of all cache_* tables and clearing the cache or drush cr
- turning aggregated css off, clearing caches, turning it back on, clearing caches
- running cron
- running /update.php

...Is there any way I can tell Drupal to generate these files instead of waiting hours for it?

  • If CC is not working right away then the issue is not with Drupal or its caching. I think it might be an issue with features and configuration. Maybe features store some data in configuration instead of cache and that causes this behavior, which means Features have a bug..which is not surprising since they are not stable yet. – user21641 Oct 28 '15 at 16:09
2

A few more things to check when you have issues like this:

  • Any noteworthy issues on the Status page? (admin/reports/status)
  • Does saving the File system page generate any errors? (admin/config/media/file-system) This sometimes indicates permission or ownership issues in the file structure, which could keep the aggregate CSS and JS files from being generated?
  • Have you checked the error log for any noteworthy messages? (admin/reports/dblog)

Clearing the cache is a good place to start, but I see that you already did that. Try checking the error log immediately after clearing the cache to see if anything pops up.

  • It's been so long since I asked this question, but I've had this issue a number of times since. One of the common things that caused it was that a certain block configuration was requiring a vendor library that didn't exist, and I had to run composer drupal-update. Another time, the library DID exist, but PHP's APC was still thinking that it didn't, so I had to do an Apache reload. – RaisinBranCrunch Jun 14 '16 at 21:18
  • Ah, those are definitely good things to check for too. Would either of those problems have shown up in the error log? – davidneedham Jun 15 '16 at 22:09
  • Yes, it did show up in the Apache log, but not in the dblog. They both showed up as the same class not found error, which was deceptive when dealing with APC. – RaisinBranCrunch Jun 17 '16 at 15:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.