1. 30 Nov, 2005 1 commit
  2. 29 Nov, 2005 1 commit
  3. 24 Nov, 2005 1 commit
  4. 22 Oct, 2005 1 commit
  5. 08 Oct, 2005 1 commit
  6. 07 Oct, 2005 1 commit
    • Dries's avatar
      - Patch #29465: new form API by Adrian et al. · 7e1527ee
      Dries authored
        TODO:
        + The contact.module was broken; a new patch for contact.module is needed.
        + Documentation is needed.
        + The most important modules need to be updated ASAP.
      7e1527ee
  7. 18 Sep, 2005 1 commit
  8. 12 Sep, 2005 1 commit
  9. 31 Aug, 2005 1 commit
  10. 17 Aug, 2005 1 commit
  11. 15 Aug, 2005 1 commit
  12. 11 Aug, 2005 1 commit
  13. 29 Jul, 2005 2 commits
  14. 19 Jul, 2005 1 commit
  15. 18 Jul, 2005 1 commit
  16. 17 Jul, 2005 1 commit
  17. 13 Jul, 2005 1 commit
  18. 29 Jun, 2005 1 commit
  19. 22 Jun, 2005 1 commit
  20. 07 Jun, 2005 2 commits
    • Dries's avatar
      - Patch #1898 by Djun: more book module improvements including but not limited · c5031621
      Dries authored
        to OPML export functionality, better code comments, better help texts, etc.
      c5031621
    • Dries's avatar
      · 1474632a
      Dries authored
      - Patch #24135 by Moshe: made it possible to ban visitors based on hostname/IP.  Banning visitors can either be done from the 'access control' pages, or directly from the statistics pages.  This feature is very convenient to block badly behaving crawlers.
      1474632a
  21. 06 Jun, 2005 1 commit
  22. 26 May, 2005 1 commit
  23. 14 May, 2005 1 commit
  24. 12 May, 2005 1 commit
    • Dries's avatar
      · 2b7f504d
      Dries authored
      - Added the ability to track page generation times in the statistics module.
        (Made some improvements as per the suggestions in the issue.)
      
      - Added extended timer implementation.
      2b7f504d
  25. 05 May, 2005 1 commit
  26. 04 May, 2005 1 commit
  27. 24 Apr, 2005 1 commit
  28. 18 Apr, 2005 2 commits
  29. 15 Apr, 2005 2 commits
  30. 11 Apr, 2005 1 commit
    • Dries's avatar
      - Patch #19298 by Jeremy: loose caching! · e3d62d90
      Dries authored
      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.)
      e3d62d90
  31. 08 Apr, 2005 1 commit
  32. 31 Mar, 2005 1 commit
  33. 07 Mar, 2005 1 commit
  34. 05 Mar, 2005 1 commit
  35. 27 Feb, 2005 1 commit
  36. 02 Feb, 2005 1 commit