After the recent update from Boost 7.x-1.0-beta1 to 7.x-1.0-beta2

the following errors have appeared on our sites /admin/reports/status page.

boost issue - boa

when visiting -- /admin/config/development/performance we are able to remove the checks from the "cache" options but after "save configuration" the results do not stay.

Our site url does not contain DEV, and both the site and platform are over 24 hours in age and verify cleanly.

Thank you,
Hg

p.s. -- Have read -- http://omega8.cc/speed-booster-cache-boost-and-advagg-108

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

rosso69’s picture

Same problem here. Clean install drupal-7.15 with boost.

omega8cc’s picture

Category: support » bug
Status: Active » Fixed

It is indirectly fixed in BOA HEAD, since we force now $conf['cache'] = 0; for D6 and D7 platforms by default, not only because of Boost, but primarily because of Redis related compatibility/issues.

rosso69’s picture

Funny, i was just reading
https://github.com/omega8cc/nginx-for-drupal/issues/140

Thnx a lot.

HyperGlide’s picture

Thank you. Another reason looking forward to a BOA update :-)

Status: Fixed » Closed (fixed)

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

HyperGlide’s picture

Status: Closed (fixed) » Active

Updated to head in the last 24 hours after #1614162: CRON Not Running on Octopus Satellites, and Individual sites. BOA 2.0.3 was fixed.

Still experiencing the same issue as reported when opened the issue.

omega8cc’s picture

Status: Active » Closed (cannot reproduce)

I can't reproduce this. Please use built-in Boost head version and check if that makes any difference. Maybe you have some overrides which break the logic in the /data/conf/global.inc, no idea.

HyperGlide’s picture

Status: Closed (cannot reproduce) » Active

Working to trouble shoot this issue. Pls advise if should open a new issue.

Looked at /data/conf/global.inc and $conf['cache'] = 0; was set properly.

Complete file is uploaded at http://pastebin.com/FmvhSyes

Disabled bot the purge and Cache Expiration modules. No support.

Thank you,
Hg

omega8cc’s picture

Category: bug » support
Status: Active » Closed (cannot reproduce)
FileSize
100.32 KB
187.8 KB

Just tried it again and I can't reproduce any problems, sorry.

Status

Modules

HyperGlide’s picture

Confirmed. Tried on a stock install and was not an issue.

On site conflict.

Thanks again.

HyperGlide’s picture

Status: Closed (cannot reproduce) » Closed (works as designed)

Disabled the core cache by editing:

/data/conf/global.inc

Line 129

/**
 * Optional extra settings
 *
 */
if (file_exists('/data/conf/settings.global.inc')) {
  require_once "/data/conf/settings.global.inc";
}

if (file_exists('./web.config')) {
  if (file_exists('./core')) {
    $conf['cache'] = 1; // enable hardcoded standard caching - Drupal 8
    $drupal_eight = TRUE;
    header('X-Backend: A');
  }
  else {
    $conf['cache'] = 0; // enable hardcoded standard caching - Drupal 7
    $drupal_seven = TRUE;
    $use_redis = TRUE;
    header('X-Backend: B');
  }
}

Edited $conf['cache'] = 1; // enable hardcoded standard caching - Drupal 7 to 0.

Will this change be over written the next time update BOA? Verify Hostmaster?

Is this a unique ness to our site or standard BOA? Per previous comments and testing on a new install the issue was not reproducible.

Thank you
Hg

HyperGlide’s picture

HyperGlide’s picture

Status: Closed (works as designed) » Active
omega8cc’s picture

Category: support » bug
Status: Active » Needs work

We have switched back to forcing $conf['cache'] = 1; because otherwise it caused conflicts with Redis and also caused remote caches, like CloudFlare to never cache anything, if the first (not-yet-cached in either Boost or Speed Booster) response came with Dupal own no-cache headers caused by $conf['cache'] = 0;

You shouldn't modify this default. If you wish, you can do that either in the override.global.inc or local.settings.php, since changes to global.inc will always be overwritten, and there is no reason to do it.

We may want to silence this warning in Boost, because it is not really harmful, as explained here - see also the Boost author's comment there.

HyperGlide’s picture

Thank you for the follow up.

omega8cc’s picture

Project: Barracuda » Octopus

Moving this to the correct queue, since we can silence it only in the included in Octopus Boost's copy.

omega8cc’s picture

Status: Needs work » Fixed
HyperGlide’s picture

++omega8cc

Status: Fixed » Closed (fixed)

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