I've sometimes noticed that cached pages display without themes.

Not sure why, though suspect it could be something to do with caching of these pages being triggered by bots rather than human visitors; I've seen that pages can load differently w bots - albeit only example I'm aware of is that bots don't trigger google analytics.
[otherwise, a quirky server issue at time page is created and cached? Tho server mostly reliable, and wasn't noticing this without Boost.]

CommentFileSizeAuthor
#3 boost-551014.patch1.52 KBmikeytown2

Comments

mikeytown2’s picture

mikeytown2 commented
Title: Theme sometimes AWOL » Theme sometimes AWOL - Need better defaults on install for JS/CSS cache.

This has to do with Drupal and it's love for clearing the css cache. The next version of druapl, 6.14 should have some of this fixed since they accepted a patch I wrote #276615: If users goes to admin/build/themes and does not submit, anon users see cached pages with references to non-existent CSS. How to overcome this is to enable CSS & JS caching. You can enable that in the boost advanced settings. Let me know if this was the issue.

DocMartin’s picture

DocMartin commented

Thanks; just enabled the css and js caching.
On quick check, looks fine; tho previously the cached pages looked fine, took time before I noticed the theme seemed absent. Hopefully this has solved it

mikeytown2’s picture

mikeytown2 commented
Status: Active » Needs review
StatusFileSize
new boost-551014.patch1.52 KB

changed the defaults

mikeytown2’s picture

mikeytown2 commented
Status: Needs review » Fixed

committed

DocMartin’s picture

DocMartin commented

Just had the problem recur
Seems it takes time before cropping up.

I found that theme still AWOL even after disabling Boost; had to delete the Boost cache. Then, pages back to normal appearance.
[oddly, a page in Firefox still looked ok, even tho trouble in Safari and Opera, and I tried deleting Firefox browser cache]

I wonder if something to do with me still having recommended version of poormanscron, not the dev version (after reading advice re not using dev versions of Drupal modules; hoped a new release won't take long). Even though I have Boost set to ignore complete flushes, might the non-dev poormanscron delete the cached js and css , while leaving the .html files for pages?
- I did have quick look in cache folder for css and js, but didn't notice them.

mikeytown2’s picture

mikeytown2 commented

The 1.0 of poormanscron will mess up the cache; there is always a good reason for using a particular version of a module if it is documented.
#512314: premature cache flush when cron run via poormanscron 1.0; latest poormanscron dev fixes issue.

DocMartin’s picture

DocMartin commented

Thanks again; just upgraded to dev version of poormanscron

DocMartin’s picture

DocMartin commented

Looking good since the change to dev of poormanscron

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.