Closed jbickar closed 10 years ago
@mistermarco plz review
What do you think of using DRUPAL_CACHE_PER_PAGE instead? (haven't tested)
I can test. The difference is probably negligible, given the content of the block.
https://api.drupal.org/api/drupal/includes!common.inc/constant/DRUPAL_NO_CACHE/7
"For simple blocks (notably those that do not perform any db query), where querying the db cache would be more expensive than directly generating the content."
variable_get() - which is what's used to generate the content of that block - doesn't query the database.
On 7/31/14, 3:54 PM, Marco Wise wrote:
What do you think of using DRUPAL_CACHE_PER_PAGE instead? (haven't tested)
— Reply to this email directly or view it on GitHub https://github.com/Stanford/WMD/pull/121#issuecomment-50829514.
cache per page works. You can see it on https://swsblog.stanford.edu
Thanks so much JB!
On sites with caching enabled, we have had a lot of user confusion about where they get redirected to after login. This alleviates that confusion by not caching the WMD login block (so the destination is always the current page).