| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This makes it easier to use JavaScript (e.g. Google Adsense) inside blocks.
|
|
|
|
| |
This makes it easier to use JavaScript (e.g. Google Adsense) inside blocks.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
I rewrote part of the patch to improve the themability of the block, as
well as its default look. I also left out the 'Recent posts' for now and
shuffled some code around.
|
| |
|
|
|
|
| |
'<div id=menu>'.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
book are of type 'book'.
|
|
|
|
| |
of roles.
|
| |
|
| |
|
| |
|
|
|
|
| |
vocabularies.
|
| |
|
| |
|
|
|
|
| |
patch.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Drupal's existing caching mechanism doesn't perform well on highly dynamic websites in which the cache is flushed frequently. One example is a site that is under attack by a spambot that is posting spam comments every few seconds, causing all cached pages to be flushed every few seconds. Loose caching immediately flushes the cache only for specific users who have modified cached data (whether or not they are logged in), delaying the flushing of data for other users by several minutes.
(I rewrote the help text a bit and made minor changes to the code comments.)
|
| |
|
| |
|
| |
|
|
|
|
| |
invokes to deal with the body of the node, but afterwards it only uses the teaser to generate the feed. So the nodeapi hook should be called with teaser processing in mind. This simple patch fixes that.
|
| |
|
| |
|