I noticed that if I simply type in the domian name in the URL field of my browser, the site redirects to: mydomain.com/cache/normal/mydomain.com/_.html and an unthemed page appears. I am not sure how to troubleshoot this or what to try to fix it.

Comments

bgm’s picture

The name of the file is normal (_.html for the main page).

Can you check:

* if the CSS/JS links in the _.html file are valid?
* is CSS/JS aggregation enabled?
* are you using anything special for CSS/JS aggregation or a CDN?

danny englander’s picture

Hi, thanks for getting back to me on this. Looking into the _.html file, there are 6 aggreegated CSS files and only 4 out of the 6 go to valid files:

<link type="text/css" rel="stylesheet" href="/sites/default/files/css/css_CKoWqiBj9gVXhPuDSnNphuEB0b0J2To76x0pX0EGqn4.css" media="all" /> -- ok
<link type="text/css" rel="stylesheet" href="/sites/default/files/css/css_BqOY1zbUYuBuCl2IC4QWQCesjZsozpaqC14DaEIA0_g.css" media="all" /> -- ok
<link type="text/css" rel="stylesheet" href="/sites/default/files/css/css_fABjJoA4bRJQ17GTm8CqfirZWaE9ISGLZrjauliirTo.css" media="all" /> -- ok
<link type="text/css" rel="stylesheet" href="/sites/default/files/css/css_hDT8ezuoE86KY3p_oDBlA75r9GNQ9zKNHFHFQpQwX7g.css" media="all" /> -- 404
<link type="text/css" rel="stylesheet" href="/sites/default/files/css/css_5_EBsvYf_U3gqgv1Idal1sImw7zcXB1kaIR6NOugp8o.css" media="print" /> -- ok
<link type="text/css" rel="stylesheet" href="/sites/default/files/css/css_uD48GocsG-Otg0qafcNvdWz089qZ2tdfXc1oq8ScU9A.css" media="screen" /> -- 404

Note the two 404's above, the other files simply contain module CSS so I am presume the other 2 have the important Theme CSS that is actually needed to render the theme.

I do have all CSS/JS aggregation enabled. I am not using any special or extra aggregation modules or a CDN.

bgm’s picture

Hi,

This can happen when your CSS files have changed (files added/removed) causing Drupal to re-aggregate the files, but the boost cache did not expire.

The re-aggregation can happen in two cases:

* a module has included a CSS/JS file conditionally (generally does not cause any issues, since the page becomes cached in boost anyway, so the condition applies only when the boost cache is regenerated)
* a CSS file was added to the theme (in which case, Drupal core cache needs to be flushed to become effective).

In other words, more likely the Drupal core cache was flushed, but not the Boost cache.
It might be just a setting, or that the cache could not be cleared (check watchdog messages).

Sorry for the slow response.