| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
for performance's sake.
|
| |
|
|
| |
node_revisions which shouldn't be there.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This allows admins to know exactly which version of which files they use. In addition I want to use CVS $Id$ tags in my upcoming security.module to check for possible vulnerabilities. That's not possible if some files simply don't have $Id$s.
Note: I also (mostly) unified the tags to use the "// ID" form instead of "/* ID */", but that's more of a cosmetic issue. I'm not sure whether *.txt files and the stuff in themes/ need tags(?).
|
| | |
|
| |
|
|
|
| |
+ made it possible to specify a subject when submitting a message on the contact form.
+ fixed some bugs/glitches.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Currently the upload module checks two max file sizes. First it checks a global option; if its too big it quits. Then it checks another max file size (or even sizes) related to the roles which a user is in. We can remove the global option since the individual roles are checked.
|
| | |
|
| |
|
|
| |
improve defaults).
|
| |
|
|
| |
(Yay, more PostgreSQL contributors! :))
|
| | |
|
| | |
|
| |
|
|
|
|
| |
(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'.
|
| |
|
|
| |
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.
|
| | |
|
