| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
taxonomy_save_*() functions.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
part of the node system! If you have a module that implements node
types, you'll have to udpate its CVS HEAD version.
We replaced _node_name() and _node_types() by _node(). The new _node()
hook let's you define one or more node types, including their names.
The implementation of the _node() hook needs to:
return array($type1 => array('name' => $name1, 'base' => $base1),
$type2 => array('name' => $name2, 'base' => $base2));
where $type is the node type, $name is the human readable name of the type
and $base is used instead of <hook> for <hook>_load, <hook>_view, etc.
For example, the story module's node hook looks like this:
function story_node() {
return array('story' => array('name' => t('story'), 'base' => 'story'));
}
The page module's node hook module like:
function page_node() {
return array('page' => array('name' => t('page'), 'base' => 'page'));
}
However, more complex node modules like the project module and the
flexinode module can use the 'base' parameter to specify a different base.
The project module implements two node types, proejcts and issues, so it
can do:
function project_node() {
return array(
array('project_project' => array('name' => t('project'), 'base' => 'project'),
array('project_issue' => array('name' => t('issue'), 'base' => 'project_issue'));
}
In the flexinode module's case there can only one base ...
This hook will simplify the CCK, and will make it easy (or easier) to merge
the story and page module.
In addition, node_list() became node_get_types(). In addition, we created
the following functions: node_get_name($type) and node_get_base($type).
|
| | |
|
| |
|
|
| |
Prevents forum topics from getting lost.
|
| |
|
|
|
|
| |
Usernames can now be themed; eg. an icon/avatar could be added.
TODO: update contributed modules + update the migration docs.
|
| |
|
|
| |
TODO: update image module too?
|
| |
|
|
| |
TODO: document the defaults in the PHPdoc comments.
|
| |
|
|
| |
forum icon path. TODO 1: the forum icons should probably be configurable on a per-site or per-theme basis. TODO 2: I spent 5 minutes looking for this setting.
|
| |
|
|
| |
placeholder/check calls, and introduce API for <link> tags.
|
| | |
|
| | |
|
| |
|
|
| |
significantly.
|
| |
|
|
| |
instead of "created term").
|
| | |
|
| | |
|
| |
|
|
|
| |
TODO: we should write down a couple guidelines for these document them in
the PHPDoc code of drupal_set_message()! .
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
editing a forum.
|
| |
|
|
| |
should write guidelines for this -- maybe in the PHPDoc code of the _help hook.
|
| |
|
|
| |
comments
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
track updates/changes.
|
| | |
|
| |
|
|
| |
taxonomy, the title used to change to the current term, but now it always just displays the vocabulary name. I have attached a patch that restores the previous behaviour. It looks like the regression may have been introduced in some changes to theme_forum_display.
|
| |
|
|
| |
multiple instances of a Drupal page appear nested inside of each other when the confirmation of deletion page is displayed.
|
| | |
|
| | |
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
| |
with other blocks.
|
| | |
|
| |
|
|
| |
forums instead of forcing the user to add a taxonomy.
|
| |
|
|
| |
story, and blog and the minimum number of words found in story and blog (blog had a slight bug) into the node module.
|
| | |
|
| |
|
|
| |
business calling theme_page(). Lets have it return the output and then forum_page() can put it in a page.
|
| |
|
|
|
|
| |
set, and it counted nodes with more than 1 comment as multiple nodes).
- Clean up various SQL queries: removing literally inserted data (db_escape_string is evil!), fixing single "%" which should be "%%", fixing integers being compared as strings.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
* Less logic in theme code.
* Encourages use of the menu system.
* Easier to find where a title or breadcrumb comes from in other people's code because there are less places to look. Look in menu and then grep for the appropriate set function. Looking for calls to theme_page() is hard because there are too many of them.
* Very slightly more efficient.
|
| |
|
|
| |
feature. All themes currently support primary and secondary links so page links are now deprecated. Check your contributed modules and update them accordingly.
|
| |
|
|
| |
consistency.
|
| |
|
|
|
|
| |
implemtented it properly per database backend.
Read the manual for pg_escape_string: "Use of this function is recommended instead of addslashes()." Or read sqlite_escape_string: "addslashes() should NOT be used to quote your strings for SQLite queries; it will lead to strange results when retrieving your data."
|
