Dear maintainer,
i managed to get it working.
The Drupal Status still complains about .htaccess not being okay. Can or should it do something about this. But the HTML Code shows that the pages are cached through boost.
thanks in advance
regards
ChrisZZ
Comments
Comment #1
chriszz commentedjust changed the title
Comment #2
bgm commentedIt complains because we use a standard configuration for boost and it disregards some of the settings in admin/settings/performance/boost.
Normally, you should be able to change some settings and copy-paste a new set of rewrite rules in your .htaccess, but since that .htaccess is common to all the sites in the platform, it does not really make sense, so the rewrite rules are put in the site vhost.
This issue is a bit related to:
* #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 just 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. 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?
Comment #3
bgm commentedClosing request as duplicate of #1027362: Boost module should hide admin sections when running in Aegir