| Commit message (Collapse) | Author | Age |
|
|
|
| |
a separate table. (Today's critical bugfix #1.)
|
|
|
|
| |
with "sticky" or "promote to front" checked.
|
| |
|
|
|
|
| |
user' role to authenticated users. Fixed glitch with udpate path.
|
|
|
|
| |
upgrade path for incorrectly set up databases)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
modules, themes.
|
|
|
|
|
|
|
| |
1. "int(10)" -> "int", fixed typo in index name [pgsql change only]
2. added defaults for uid and hostname (needed for both)
3. postgres supports "DROP column" syntax
4. added missing DELETEs for new table in poll_delete() and poll_update()
|
| |
|
|
|
|
| |
to fix utf-8 problems and improves consistency with PostgreSQL.
|
|
|
|
|
|
|
| |
- When user #1 creates an account (we can assume this happens only once), system.module's schema version is set to the latest availiable.
- system_get_files_database() now includes a 'schema_version' child of each file object.
- That new information is re-saved when Drupal re-populates the system table.
- An array of newly-enabled modules is built, module_list() is reloaded, and the schema versions of each newly-enabled module are set to the most recent availiable. If the schema version is already set (presumably from a previous installation) it is not changed.
|
|
|
|
|
|
| |
installed sites.
There are a number of small optimizations we could add; like, we should never do more lookup queries than the number of unique URL aliases in the database. When the size of the static cache equals the number of unique URL aliases in the database, we can stop doing lookups. I think this could be implemented with a 2-line change. Takers?
|
|
|
|
| |
definition files need to reflect this.
|
| |
|
| |
|
|
|
|
| |
in strict mode.
|
|
|
|
| |
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.
|