Not sure if this is a feature request or bug report.

Because drush cc all did not clear the Boost cache I was accustomed to do a rm -rf cache/* to clear the Boost cache. I assumed that everything need to let the Boost cache function would be re-generated as well.

And almost everything is generated again, but not .htaccess. This means that apache will take the default htaccess rules from the Drupal webroot. This is a expiry time of two weeks!

I cannot decide is this is a bug, but two options come in mind:
- Explicitly state in the Boost documentation that people should NOT manually empty the cache directory
- or: re-generate .htaccess when it does not exist

Drush way of clearing Boost cache: clear the cache with the Drush uri parameter.
drush --uri:http://www.yourdomain.com cc all

Comments

Can you clarify: which .htaccess? The one in your web root provided by Drupal? (and that you have to manually edit to insert the boost rules)

"And almost everything is generated again, but not .htaccess. This means that apache will take the default htaccess rules from the Drupal webroot. This is a expiry time of two weeks!"

Sorry, I don't understand. Can you explain more in detail the bug vs expected behavior?

Thanks

Category:bug» support
Status:Active» Postponed (maintainer needs more info)

Category:support» bug
Status:Postponed (maintainer needs more info)» Active

Ah, found it while debugging another issue: for example: ./normal/www.example.org/.htaccess
Sounds like a bug. However, for me, the cache still works even after deleting the .htaccess.

I think calling boost_form_submit_handler(); from function boost_flush_caches() would do the trick? i.e. running the cron does re-create the .htaccess for those directories, via _boost_rmdir().

Issue summary:View changes

typo fix