| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
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."
|
| | |
|
| | |
|
| |
|
|
| |
when node-level permission were used.
|
| | |
|
| |
|
|
| |
eliminates up to 10 SQL queries (sometimes less) for each non-cached page view on drupal.org. Derived from ccourtne's patch.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The primary goal of this patch is to take the 'custom' and 'path' columns of the block overview page and make them into something understandable. As of Drupal 4.5 'custom' lacked an explanation which wasn't buried in help text and path required dealing with regular expressions.
Every block now has a configuration page to control these options. This gives more space to make form controls which do not require a lengthy explanation. This page also gives modules a chance to put their block configuration options in a place that makes sense using new operations in the block hook.
The only required changes to modules implementing hook_block() is to be careful about what is returned. Do not return anything if $op is not 'list' or 'view'. Once this change is made, modules will still be compatible with Drupal 4.5. Required changes to core modules are included in this path.
An additional optional change to modules is to implement the additional $op options added. 'configure' should return a string containing the configuration form for the block with the appropriate $delta. 'configure save' will come with an additional $edit argument, which will contain the submitted form data for saving. These changes to core modules are also included in this patch.
|
| |
|
|
|
|
| |
TODO:
+ Update Doxygen hook list (if required).
+ Document this in the developer's upgrade section.
|
| |
|
|
|
|
| |
Doxygen documentation and screen output.
Uwe: I dropped the 'iff' chunks as 'iff' stands for 'if and only if'.
|
| |
|
|
| |
only nodes of type 'forum' resulting in the forum overview listing counting all node types as topics; attached patch modifies queries to return counts of only 'forum' type nodes.
|
| |
|
|
| |
child forums.
|
| |
|
|
| |
forum_insert().
|
| |
|
|
| |
module's hands, and move it below the relevant textarea.
|
| |
|
|
|
|
|
| |
+ made the helptext under the 'Explanation or submission guidelines', more the same (blog & story);
+ made the form_set_error() texts consistent when the body of a blog/story does not match or exceeds the specified minimal numer of words.
+ used the $options for form_select() and form_radios() inline like we do in the rest of drupal;
+ made the textarea sizes for the submission pages the same for all node types and also for the 'Explanation or submission guidelines';
|
| |
|
|
| |
shown.
|
| | |
|
| |
|
|
| |
- Patch #10308 by ccourtne: performance improvements: comment statistics are now cached in a new SQL table which significantly improves performance of the forum block and the forum pages. These pages are about 3 times faster now!
|
