This is more an issue for the boost module itself, but we cannot propose a patch until the provision module provides a method to detect that we are running in Aegir.

Opening an issue here nontheless since it is an issue for provision_boost.

See: #1027358: Set a variable in settings.php so that modules can check whether the site is in Aegir

Comments

j0nathan’s picture

j0nathan commented

Hi,
Are we talking about admin/settings/performance/boost here?
I would prefer a default configuration than disabling access to that configuration page, especially if I want to change values (ex.: Default maximum cache lifetime, Statically cache specific pages/Pages).

j0nathan’s picture

j0nathan commented

Also, that page provide a button to clear Boost's Database & File Cache.
But I opened a feature request: #1118152: "Clear Boost's Database & File Cache" through drush
What about people that cannot use drush on an Aegir hosting?

bgm’s picture

bgm commented

@j0nathan: running "verify" on the site will flush the cache. #1026114: Clear the cache boost on verify (ex: after a migration/clone)

Yes, I'm proposing to restrict admin/settings/performance/boost. We should propose a patch to boost to hide parts which cannot be changed in Aegir (ex: anything that affects how the .htaccess is generated).

j0nathan’s picture

j0nathan commented

Seems fine to me.

bgm’s picture

bgm commented

To reformulate the issue. Taken from duplicate request: #1200534: Drupal Status still complains about .htaccess not being okay :

Related issues:

* #976066: use boost_admin_generate_htaccess() to generate the rewriterules in the site vhost
* #1027362: Boost module should hide admin sections when running in Aegir
* #1027358: Set a variable in settings.php so that modules can check whether the site is in Aegir

Some leads to resolving this:

* provision_boost could set the boost configuration so that it reflects the htaccess used in the vhost. (obvious cons: changing a setting in admin/settings/performance/boost will make the warning appear again)

* ideally, imho, is that the boost module be "aware" of Aegir, and hide some sections, warnings. This is possible now thanks to #1027358: Set a variable in settings.php so that modules can check whether the site is in Aegir. However, it is a bit intrusive to the boost module. Alternatively, make a boost_aegir module that does a hook_alter_form on the boost admin forms. (requires a separate module for that, but not a big deal)

* document the issue in the README, project description page, etc.

Any other ideas, suggestions?