| Commit message (Collapse) | Author | Age |
|
|
|
| |
form categories and fixed some small glitches.
|
|
|
|
| |
with '&' in title.
|
|
|
|
|
|
|
|
|
| |
Deprecates the primary_links module.
This patch was much needed. Thanks Richards!
NOTE: if some themers could investigate if there is room for improvement
with regard to theming, that would be awesome.
|
|
|
|
|
| |
Presentation about it:
http://www.acko.net/files/drupal-search-slim.pdf
|
|
|
|
|
|
| |
descriptions.
(Modified the form a bit.)
|
| |
|
|
|
|
| |
forum table.
|
| |
|
|
|
|
| |
improved the database scheme and queries of the block.module.
|
|
|
|
|
|
|
|
|
|
| |
All node revisions were stored in a serialized field in the node table and retrieved for _each_ page view although they are rarely needed. We created a separate revisions table which would be in principle identical to the node table, only that it could have several old copies of the same node. This also allows us to revision-related information, and to provide log entries to non-book pages when a new revision is being created.
TODO:
1. Provide upgrade instructions for node module maintainers!
2. Upgrade modules that implement node types.
3. Provide an upgarde path for revisions. Dependency on the upgrade system.
|
| |
|
| |
|
|
|
|
|
| |
+ made it possible to specify a subject when submitting a message on the contact form.
+ fixed some bugs/glitches.
|
| |
|
| |
|
|
|
|
| |
improve defaults).
|
| |
|
|
|
|
|
|
| |
(Made some improvements as per the suggestions in the issue.)
- Added extended timer implementation.
|
|
|
|
| |
alias of "rss.xml" for "node/feed" was added. This ONLY occurs in updates.inc however - if people grab a fresh 4.5 (or now, 4.6), they are never going to get this added alias. The attached patch adds this INSERT into the default database.* files, adds another update into the updates.inc (so that those who started with a fresh 4.5 or 4.6 will get it via update.php the next time around) and fixes some minor whitespace/style inconsistencies.
|
|
|
|
| |
any more.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
keep track of the user's last access. In turn, this allowed me to:
1. Optimize the "Who's online" block. On drupal.org, the "Who's online"
block requires 32 SQL queries. With this patch, only 2 queries are
left (eliminated 30 SQL queries), and one of the two remaining queries
became appr. 20 times faster.
2. Correct the "Last access" column in the user administration overview
table. The presented data was not accurate, which led to the column
being removed. You can now sort users by 'last access'.
|
| |
|
|
|
|
| |
locale_sources table.
|
| |
|
|
|
|
| |
Who wants to be the maintainer?
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.)
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds folksonomy support to Drupal (named internally as "Free tagging"). In a nutshell, the core difference is the input method: unlike normal taxonomies which are administratively controlled, a "free tagging" vocabulary allows tag creation when the node is submitted. It does this through an text input box, as opposed to a dropdown or selectbox. This patch:
* Removes the useless "Preview form" of a vocabulary.
* Alters the vocabulary table to include a new "tags" column.
* Adds a new "Free tagging" preference on vocabulary creation/editing.
* Modifies the vocabulary overview to support pagers for free tagging vocabs.
The new code integrates tightly with the existing taxonomy code. The only additional processing occurs on node save and edit, where we parse through the tags associated with a node. All other display (and thus, code) remains the same.
|
| |
|
|
|
|
| |
terms are matched, the query would become very slow.
|
| |
|
|
|
|
|
|
|
|
|
| |
spotted that the following fields appear to have incorrect type definitions:
profile_values.fid = int(11)
profile_values.uid = int(11)
These both appear inconsistant with the rest of the database (that I have seen i.e. user tables) where they are defined as int(10). The profile_fields.fid is defined as int(10) also.
|
| |
|
| |
|
|
|
|
| |
forums instead of forcing the user to add a taxonomy.
|
|
|
|
| |
on pages of certain node type.
|
|
|
|
| |
tidied up the taxonomy API a bit. This fixes a number of issues.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
node table. With help from Gerhard.
- Slight addition to INSTALL.txt with regard to PHP versions.
- Updated/reworded some node type descriptions as per Boris' suggestions.
- Adding missing {} around a table name in update.php.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
changes are:
1. Simplified the statistics pages: there are less pages and on the
remaining pages there is a lot less visual clutter (less columns and
better presentation).
2. Reorganized the 'administer - logs' menu: flattened the menu structure
and removed a number of links.
3. Improved performance. Most statistics pages used about 160 slow SQL
queries which made the statistics pages fairly unusable on my system.
The new pages use at least 10 times less SQL queries and render much
faster. They are actually usable.
4. There is now a 'track'-tab on node pages, and a second subtrab on the
user accounts 'track'-tab for people with the 'access statistics'
permission. They can be used to resp. track the node and the user.
This makes the statistics more accessible.
5. Changed the way watchdog messages are filtered. This makes it easier
to introduce new watchdog types.
6. Reworked the statistics module's permissions.
7. Less code: 223 insertions(+), 343 deletions(-).
8. Fixed several glitches: for example, the statistics pages sorted the
'Name' column by user ID instead of by name. Unfortunately, it is
too difficult to backport these to DRUPAL-4-5.
TODO:
1. Review the statistics modules help pages.
2. Help fine-tune the interfaces/views.
NOTES:
1. You'll want to run update.php.
|
|
|
|
|
| |
+ added support for multi-site configurations.
+ tidied up some old cruft and added code comments.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
+ When a comment is posted, a node needs to be re-indexed. Luckily, we can use node_comment_statistics for this easily.
+ When a node is deleted, it should be deleted from the search index as well.
+ The search wipe didn't properly remove links to nodes from the index.
+ Section url was faulty in _help.
+ Minor code rearrangement.
|
|
|
|
|
|
|
|
|
|
|
| |
+ Display 'friendly' name rather than module name in search watchdog
messages.
+ Remove left-over from search_total table.
+ Add index wipe button to the admin
+ Moved the admin to admin/settings/search
+ Prevented menu bug when node modules update the breadcrumb in view
(thanks JonBob).
+ Changed search_total table's word key to PRIMARY.
|
|
|
|
|
|
|
|
|
|
| |
The primary goal of this patch is to take the 'custom' and 'path' columns of the block overview page and make them into something understandable. As of Drupal 4.5 'custom' lacked an explanation which wasn't buried in help text and path required dealing with regular expressions.
Every block now has a configuration page to control these options. This gives more space to make form controls which do not require a lengthy explanation. This page also gives modules a chance to put their block configuration options in a place that makes sense using new operations in the block hook.
The only required changes to modules implementing hook_block() is to be careful about what is returned. Do not return anything if $op is not 'list' or 'view'. Once this change is made, modules will still be compatible with Drupal 4.5. Required changes to core modules are included in this path.
An additional optional change to modules is to implement the additional $op options added. 'configure' should return a string containing the configuration form for the block with the appropriate $delta. 'configure save' will come with an additional $edit argument, which will contain the submitted form data for saving. These changes to core modules are also included in this patch.
|