| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
character and causes problems in CSS.
|
| | |
|
| |
|
|
|
| |
- Converted the Bluemarine theme from XTemplate to PHPTemplate.
- Moved the the Pushbutton theme and the Xtemplate engine to the contributions repository.
|
| | |
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
| |
name contains a quote.
|
| |
|
|
| |
problematic. The line creates a unique index for sid. But, sid is already a primary key so doesn't need a unique index on it. Let alone, the syntax is wrong due to wrapping the table name in {}'s. This patch removes the line.
|
| | |
|
| |
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
| |
a number of topics in block setting. This is a bit confusing since configuring one blockshould not affect another block. Fixed some indentation as well.
|
| | |
|
| |
|
|
|
|
| |
1. Removed a duplicate line from the changes to update.inc.
2. Excluded the session.inc changes: they did not make sense to me.
3. Excluded the search related changes in the node and search module. According to Steven these are not correct.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
forums instead of forcing the user to add a taxonomy.
|
| | |
|
| |
|
|
| |
on pages of certain node type.
|
| | |
|
| | |
|
| |
|
|
| |
"/blog/52/feed".
|
| |
|
|
|
|
| |
type) configuration page.
Modified the patch to remove some redundant code, to translate strings, and to better use the menu system.
|
| |
|
|
| |
the nodes.
|
| |
|
|
| |
primary key.
|
| |
|
|
| |
tidied up the taxonomy API a bit. This fixes a number of issues.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
We added a 'severity' column to watchdog():
watchdog($type, $message, $link) --> watchdog($type, $message, $severity, $link);
* Specify a severity in case you are reporting a warning or error.
* The $link-parameter is now the fourth parameter instead of the third.
TODO: document this in the upgrade guide.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
