| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
|
| |
+ Make bootstrap functionality work with HEAD.
+ Move functions into bootstrap.inc so that statistics_exit() works for cached pages. (Does this close any issues?)
|
| |
|
|
| |
feature. All themes currently support primary and secondary links so page links are now deprecated. Check your contributed modules and update them accordingly.
|
| |
|
|
| |
feature. All themes currently support primary and secondary links so page links are now deprecated. Check your contributed modules and update them accordingly.
|
| |
|
|
|
| |
+ added support for multi-site configurations.
+ tidied up some old cruft and added code comments.
|
| |
|
|
| |
each user's own blog page, similar to the "post new forum topic" link displayed at the top of forum pages. This adds consistency as well as convenience for users.
|
| |
|
|
|
|
|
|
| |
links to the theme instead of the theme having to pull them in using node_link().
TODO:
1. Update theme upgrade instructions in the handbook: node_link() is gone.
2. Remove page_link() just like we removed node_link().
|
| |
|
|
| |
consistency.
|
| | |
|
| | |
|
| |
|
|
| |
comment module use it to extract subjects.
|
| | |
|
| |
|
|
|
|
| |
implemtented it properly per database backend.
Read the manual for pg_escape_string: "Use of this function is recommended instead of addslashes()." Or read sqlite_escape_string: "addslashes() should NOT be used to quote your strings for SQLite queries; it will lead to strange results when retrieving your data."
|
| |
|
|
|
| |
- Caching index statistics
- Minor code cleanup
|
| |
|
|
| |
timestamp into account.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
hostname (eg. posting comments, requesting passwords, sending e-mails). See flood_register_event() and flood_is_allowed() for details.
|
| |
|
|
| |
you can edit.
|
| | |
|
| | |
|
| |
|
|
| |
the configuration file.
|
| |
|
|
| |
fields' unless the throttle module is enabled.
|
| | |
|
| |
|
|
| |
drupal_set_html_head().
|
| |
|
|
| |
permissions into account and could return an incorrect number.
|
| |
|
|
| |
node, redirect him to the main page.
|
| |
|
|
|
|
|
|
| |
+ throttle module: flush cache when the throttle enables/disables
+ throttle module: prevent throttle being enabled by 0 users or guests when disabled
+ system module: remove requirement for statistics.module
+ block module: update help text to reflect access log is no longer required
+ statistics module: throttle is now enabled/disabled, not using levels 0-5
|
| |
|
|
| |
border=0 attribute on the img tag for the site logo.
|
| |
|
|
| |
file handling.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* There are only two throttle levels instead of 5, namely 'enabled' and 'disabled'. This makes it a _lot_ easier to predict when the throttle will kick in. However, if you maintain a module that is throttle-aware, it needs to be updated!
* The throttle mechanism now uses the current number of anonymous users or the current number of authenticated users to kick in. This is a _lot_ more intuitive than the old throttle mechanism.
* The throttle block has been removed -- you can now use the "Who's online" block to determine the good throttle settings.
* Most of the documentation has been removed because it was deprecated.
* It's less code!
|
| |
|
|
|
|
|
|
|
| |
That should improve performance of session handling as well improve
performance of the "Who's online"-block. Drupal.org's sessions table
contains appr. 40.000 sessions on a slow day and rendering the "Who's
online"-block became a performance bottleneck.
This change has yet to be tested on a busy site so things might go wrong.
|
| | |
|
| |
|
|
| |
'authenticated user' role was not assigned to the new user.
|
| | |
|
| | |
|
| |
|
|
| |
menu items.
|
| |
|
|
| |
when node-level permission were used.
|
| | |
|
| |
|
|
| |
consistent with the rest of Drupal. We have a "maintain books" and a "edit own book pages" permission. All other modules have a "create foo" permission. Thus the existing "maintain books" permission should be renamed to "create book pages" and a new "maintain books" permission should be introduced that allows editors to update book pages they haven't created themselves even without having "administer nodes" permission.
|
| |
|
|
| |
eliminates up to 10 SQL queries (sometimes less) for each non-cached page view on drupal.org. Derived from ccourtne's patch.
|
| |
|
|
|
|
|
|
| |
comment_num_all() for each node. Instead, it checks for the availability of the node_comment field, available through the node_comment_statistics table. If updated the Doxygen comments accordingly.
People were using node_title_list() without realizing it would do numereous database queries. This change greatly reduces the number of database queries required to render the node statistics block as well as to render the forum block (coming up next).
If your module is using node_title_list() and you want the number of comments to be shown as title attributes, chances are you have to update your SQL query to join node_comment_statistics.
|
| |
|
|
| |
node_comment_statistics table. Improves performance of the tracker page by facter 10 because it eliminates up to 20 SQL queries.
|
