1. 31 Mar, 2005 1 commit
  2. 20 Mar, 2005 1 commit
    • Dries's avatar
      · 5ad5f28c
      Dries authored
      - Patch #19009 by chx: fixed a bug with comment replies letting one access nodes.
  3. 18 Mar, 2005 1 commit
  4. 16 Mar, 2005 2 commits
  5. 12 Mar, 2005 1 commit
    • Dries's avatar
      - Patch #18692 by Goba: old comments (comments for nodes having no entry in... · a16e5d24
      Dries authored
      - Patch #18692 by Goba: old comments (comments for nodes having no entry in the history table anymore) are counted as new comments, since the timestamp retrieved from the history table is used to check for new comments (which is 0, if an entry was not found). This patch sets the timestamp used to check for new comments to the NODE_NEW_LIMIT value at least (which is when the history table was/should have been pruned).
  6. 10 Mar, 2005 1 commit
    • Dries's avatar
      - Patch #18676 by frjo: When anonymuos users are allowed to add comments there... · 2ec787df
      Dries authored
      - Patch #18676 by frjo: When anonymuos users are allowed to add comments there are a required e-mail field. This field are, as far as i can see, not shown publicly. A user asked me about this and after confirming that it is not shown publicly I added a description that inform the users of this.  I have included a patch that add the description "The content of this field is kept private and will not be shown publicly". This is the same description that is used by the profile module.
  7. 03 Mar, 2005 1 commit
  8. 27 Feb, 2005 1 commit
  9. 12 Feb, 2005 1 commit
    • Dries's avatar
      - Patch #17208 by asimmonds: help text fixes: · 5b7ecb86
      Dries authored
          - permissions menu link updates in a number of modules help
          - anchor link fix in distributed auth help
          - "my account" link fix in user help
          - spelling correction in tracker.module help
      - I also changed 'admin/access/perms' to 'admin/access/permissions'.
  10. 11 Feb, 2005 1 commit
  11. 01 Feb, 2005 1 commit
  12. 31 Jan, 2005 1 commit
  13. 30 Jan, 2005 1 commit
  14. 29 Jan, 2005 1 commit
  15. 27 Jan, 2005 1 commit
    • Dries's avatar
      - Patch #16253 by Goba: this simple and straightforward patch adds the ability... · 467dbdc4
      Dries authored
      - Patch #16253 by Goba: this simple and straightforward patch adds the ability to define different types of markers (while retaining the old default behaviour of the new and required markers to look the same). Someone with enough time on his hands might be able to partition the new marker to a real new marker and a changed marker (since node_is_new() returns TRUE even if nodes changed, and not only when they are new). This is the base on which the new patch can be worked though.
  16. 24 Jan, 2005 1 commit
  17. 19 Jan, 2005 1 commit
  18. 17 Jan, 2005 1 commit
  19. 16 Jan, 2005 1 commit
    • Dries's avatar
      · 971a0e24
      Dries authored
      - Patch #14731 by chx: made it possible to rewrite node queries.
  20. 12 Jan, 2005 2 commits
  21. 09 Jan, 2005 2 commits
    • Dries's avatar
      - Updated two watchdog calls. · df6fe902
      Dries authored
    • Dries's avatar
      - Patch #13260 by UnConeD: watchdog module improvements. · 64b100d1
      Dries authored
        We added a 'severity' column to watchdog():
          watchdog($type, $message, $link) --> watchdog($type, $message, $severity, $link);
          * Specify a severity in case you are reporting a warning or error.
          * The $link-parameter is now the fourth parameter instead of the third.
        TODO: document this in the upgrade guide.
  22. 31 Dec, 2004 1 commit
    • Dries's avatar
      - Patch #14917 by UnConeD/Steven: · 1dbe0dc2
      Dries authored
      1) The different types of search, which used to be radio button options in the search form, are now subtabs of "search" (default "search/node"). This seems better from a UI point of view, but also has another advantage: modules which implement a custom search form (flexinode, project) can add it as a subtab of search. This means that all search forms will be located in the same place, and also without needing an extra api call to search.module.
      2) The current code was a bit hackish, as the indexing of comments along with nodes was hardcoded in node.module. Instead, I created a nodeapi operation "update index" which allows modules to add more data for a node that is being indexed. Comments are now indexed using this mechanism and from comment.module, which is a lot cleaner.
      3) The search results format was also hardcoded to include "N comments". I replaced this with a nodeapi operation "search result" and moved the comment code to comment.module where it belongs. This op is quite useful, as for example I also modified upload.module to add "N attachments" to a search result if any are present.
  23. 29 Dec, 2004 1 commit
  24. 23 Dec, 2004 1 commit
  25. 20 Dec, 2004 1 commit
  26. 15 Dec, 2004 1 commit
    • Dries's avatar
      - Patch #13907 by Neil: less ways to set the page title. · 2b17b3a9
      Dries authored
         * 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.
  27. 11 Dec, 2004 2 commits
    • Dries's avatar
      · 260f8866
      Dries authored
      - Fixed typo: db_queryd() -> db_query()
    • Dries's avatar
      · d61e7a66
      Dries authored
      - Bugfix: make sure to update the node_comment_statistics table when a node is updated.
  28. 07 Dec, 2004 1 commit
    • Dries's avatar
      · 60352821
      Dries authored
      - Refactored the queue module: removed the queue module's field from the node table.  With help from Gerhard.
      - Slight addition to INSTALL.txt with regard to PHP versions.
      - Updated/reworded some node type descriptions as per Boris' suggestions.
      - Adding missing {} around a table name in update.php.
  29. 02 Dec, 2004 1 commit
  30. 29 Nov, 2004 2 commits
  31. 21 Nov, 2004 2 commits
    • Dries's avatar
      - Patch #13263 and #13265 by arnab: added word-based truncation and made the... · b442fad0
      Dries authored
      - Patch #13263 and #13265 by arnab: added word-based truncation and made the comment module use it to extract subjects.
    • Dries's avatar
      · fa978390
      Dries authored
      - Patch 13180 by chx: renamed check_query() to db_escape_string() and 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."
  32. 15 Nov, 2004 1 commit
    • Dries's avatar
      · 9979acea
      Dries authored
      - Patch #12783 by Stefan: various small consistency/usability improvements.
  33. 31 Oct, 2004 2 commits
    • Dries's avatar
      - Patch #11875 by Neil Drumm: block module configuration improvements. · b3adcf05
      Dries authored
      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.
    • Dries's avatar
      - Patch #12232 by Steven/UnConed: search module improvements. · 8daed9cb
      Dries authored
      1) Clean up the text analyser: make it handle UTF-8 and all sorts of characters. The word splitter now does intelligent splitting into words and supports all Unicode characters. It has smart handling of acronyms, URLs, dates, ...
      2) It now indexes the filtered output, which means it can take advantage of HTML tags. Meaningful tags (headers, strong, em, ...) are analysed and used to boost certain words scores. This has the side-effect of allowing the indexing of PHP nodes.
      3) Link analyser for node links. The HTML analyser also checks for links. If they point to a node on the current site (handles path aliases) then the link's words are counted as part of the target node. This helps bring out commonly linked FAQs and answers to the top of the results.
      4) Index comments along with the node. This means that the search can make a difference between a single node/comment about 'X' and a whole thread about 'X'. It also makes the search results much shorter and more relevant (before this patch, comments were even shown first).
      5) We now keep track of total counts as well as a per item count for a word. This allows us to divide the word score by the total before adding up the scores for different words, and automatically makes noisewords have less influence than rare words. This dramatically improves the relevancy of multiword searches. This also makes the disadvantage of now using OR searching instead of AND searching less problematic.
      6) Includes support for text preprocessors through a hook. This is required to index Chinese and Japanese, because these languages do not use spaces between words. An external utility can be used to split these into words through a simple wrapper module. Other uses could be spell checking (although it would have no UI).
      7) Indexing is now regulated: only a certain amount of items will be indexed per cron run. This prevents PHP from running out of memory or timing out. This also makes the reindexing required for this patch automatic. I also added an index coverage estimate to the search admin screen.
      8) Code cleanup! Moved all the search stuff from common.inc into search.module, rewired some hooks and simplified the functions used. The search form and results now also use valid XHTML and form_ functions. The search admin was moved from search/configure to admin/search for consistency.
      9) Improved search output: we also show much more info per item: date, author, node type, amount of comments and a cool dynamic excerpt à la Google. The search form is now much more simpler and the help is only displayed as tips when no search results are found.
      10) By moving all search logic to SQL, I was able to add a pager to the search results. This improves usability and performance dramatically.