1. 16 Mar, 2010 1 commit
    • Jeffery To's avatar
      Fixed IE7 prompting the user to download OpenSearch description xml after... · fa1262f5
      Jeffery To authored
      Fixed IE7 prompting the user to download OpenSearch description xml after login (for a private site)
      
      Flow:
      1. Browser (IE7) is redirected to the login page.
      2. Browser reads the page, sees OpenSearch descriptions, tries to
         download them. Each request gets recorded by SN as the page the user
         should be redirected to after logging in (returnto).
      3. User logs in, then gets redirected to the returnto action, which is
         an OpenSearch description.
      
      The OpenSearch descriptions aren't sensitive so making them public in a
      private site should be okay.
      
      (I recall fixing this in 0.8.x... :-( )
      fa1262f5
  2. 03 Mar, 2010 3 commits
  3. 02 Mar, 2010 2 commits
  4. 31 Jan, 2010 1 commit
    • Evan Prodromou's avatar
      Add a robots.txt URL to the site root · dc622464
      Evan Prodromou authored
      Adds a robots.txt file to the site root. Defaults defined by
      'robotstxt' section of config. New events StartRobotsTxt and
      EndRobotsTxt to let plugins add information. Probably not
      useful if path is not /, but won't hurt anything, either.
      dc622464
  5. 28 Jan, 2010 5 commits
  6. 14 Jan, 2010 1 commit
  7. 12 Jan, 2010 1 commit
  8. 18 Dec, 2009 1 commit
  9. 17 Nov, 2009 1 commit
    • Brion Vibber's avatar
      Fix ticket 1816: Database errors recorded as "Array" · 3d6a55a4
      Brion Vibber authored
      PEAR error backtrace lines are now correctly formatted as strings in debug log, roughly as debug_print_backtrace() does (but with argument values swapped out for types to avoid being overly verbose).
      
      Todo: exceptions and PEAR error objects should log backtraces the same way; right now it doesn't look like exceptions get backtraces logged.
      
      Todo: At one line per line, it's potentially tough to figure out what backtrace goes with what event if traffic is heavy; even if not heavy it's awkward to jump back into a log file after grepping to find the backtrace. Consider using a random per-event ID which can go in the log output -- bonus points for exposing the error ID to users so ops can track down actual error details in logs from a user report.
      3d6a55a4
  10. 13 Nov, 2009 1 commit
  11. 05 Nov, 2009 2 commits
  12. 30 Oct, 2009 1 commit
  13. 03 Oct, 2009 2 commits
  14. 23 Sep, 2009 1 commit
  15. 19 Sep, 2009 3 commits
  16. 17 Sep, 2009 1 commit
  17. 16 Sep, 2009 3 commits
  18. 14 Sep, 2009 5 commits
  19. 13 Sep, 2009 1 commit
  20. 26 Aug, 2009 1 commit
  21. 25 Aug, 2009 3 commits