| Commit message (Collapse) | Author | Age |
|
|
|
| |
db_query_range()
|
| |
|
| |
|
| |
|
|
|
|
| |
there is more than one vocabulary
|
| |
|
| |
|
|
|
|
| |
improved performance)
|
|
|
|
| |
taxonomy property
|
|
|
|
| |
improvements.
|
| |
|
|
|
|
| |
improvements for the vocabulary/term forms.
|
|
|
|
| |
more confusing 'categories'
|
|
|
|
| |
removed some whitespace.
|
| |
|
| |
|
|
|
|
| |
'content' as appropriate
|
|
|
|
| |
removed some trailing whitespace.)
|
|
|
|
| |
form labels and descritions for consistency
|
|
|
|
| |
term was selected
|
|
|
|
| |
description on term pages and feeds, but only if there was one term, not more
|
| |
|
|
|
|
| |
standardize on a common format in taxonomy help text when describing different use cases
|
|
|
|
| |
functionality by introducing menu_set_item() (for consistency in function naming), thus fixing a regression in the current development code. Also fixing some misuse of menu_set_location() by using drupal_set_breadcrumb() instead.
|
|
|
|
| |
source code and messages printed
|
| |
|
| |
|
| |
|
|
|
|
| |
.schema files into .install files to prevent mistakes.
|
|
|
|
| |
feature from schema API: load/save records based upon schema.
|
|
|
|
| |
queries, setting a best practice to avoid vulnerabilities
|
| |
|
|
|
|
| |
usable for freetagging vocabularies
|
| |
|
|
|
|
|
|
|
|
|
| |
mortals (including rename of actions.module to trigger, but keeping the actions themselfs).
Complete previous history of actions module:
- #148410 by jvandyk: added rewrite of the actions module!
- #155986 by Uwe: fixed typos.
- #155828 by Eaton, pwolanin and jvandyk: let actions live even if actions.module is not turned on
|
| |
|
|
|
|
| |
taxonomy_select_nodes()
|
|
|
|
| |
we dont need a counter
|
|
|
|
| |
Oracle and DB2. Also a performance improvement. (Correct version this time.)
|
|
|
|
| |
Oracle and DB2. Also a performance improvement.
|
| |
|
|
|
|
| |
in taxonomy_vocabulary_load.
|
| |
|
|
|
|
| |
terms.
|
| |
|
|
|
|
| |
'Save' to compliy with the desktop metaphor and actually tell what the button does ('we know it submits the form, but what it does?')
|
|
|
|
| |
only one term.
|
| |
|
| |
|
|
|
|
| |
topics to be custom node types.
|