1. 15 Jun, 2015 1 commit
  2. 26 Mar, 2015 1 commit
  3. 10 Nov, 2014 1 commit
  4. 22 Sep, 2014 1 commit
  5. 24 Jul, 2014 1 commit
    • Tobias Zeuch's avatar
      New plugin as user-message system to multiple recipients · b7606a0a
      Tobias Zeuch authored
      
      
      Bug 1246702: This is a plugin that replaces the current user notifications with a
      message system for multiple recipients.
      
      - The plugin redirects calls to sendmessage.php and inbox.php.
      - New Usermessages are stored in a separate table from the userrelation, where there
        is also kept track of whether the notification has been read or deleted.
      - Messages aren't deleted from the database, until all participantas (sender and all
        recievers) delete it.
      - The plugin comes with an outbox that shows messages that have been sent by the
        logged in user.
      - Both inbox and outbox show new messages and old messages alike.
      
      Note that the code is at pre-release state:
      The message-count per user is kept up to date with database-triggers, as is done for
      the old system.
      For this new system, you might not want to install it on a productive system or it
      might mess up your message count when you deactivate the plugin.
      
      Change-Id: I586af86266b5fb0e2d676bd1401b7d879d0122ef
      Signed-off-by: default avatarTobias Zeuch <tobias.zeuch@kic-innoenergy.com>
      b7606a0a
  6. 14 Oct, 2013 1 commit
  7. 19 Jul, 2013 1 commit
  8. 13 Feb, 2012 1 commit
    • Richard Mansfield's avatar
      Get unread message count from user table (bug #854403) · 60167828
      Richard Mansfield authored
      
      
      Also keeps the count in the $USER object up to date whenever the
      user deletes or reads a notification.
      
      When new notifications are generated for a live user by another user,
      or on cron, the logged-in user's unread count is reloaded from the
      database into the session either on hitting the inbox, or whenever
      $USER is committed for some other reason.
      
      The code to reload the background fields on commit of the LiveUser
      object has been changed to ensure that it still works at upgrade time,
      where the 'reload' column doesn't exist in the user table yet, but
      *does* exist in the User object.
      
      Change-Id: I9c9a81bf77d0927352902dee0d989d6122757b47
      Signed-off-by: default avatarRichard Mansfield <richard.mansfield@catalyst.net.nz>
      60167828
  9. 13 May, 2011 1 commit
  10. 06 Sep, 2010 1 commit
  11. 03 May, 2010 1 commit
  12. 30 Apr, 2010 2 commits
  13. 15 Sep, 2009 1 commit
  14. 23 Jul, 2009 1 commit
  15. 25 Jun, 2009 1 commit
  16. 25 Mar, 2008 1 commit
  17. 16 Feb, 2008 2 commits
  18. 28 Jan, 2008 2 commits
  19. 04 Dec, 2007 1 commit
  20. 20 Nov, 2007 1 commit
  21. 22 Aug, 2007 1 commit
  22. 20 Aug, 2007 1 commit
  23. 17 Aug, 2007 1 commit
    • Nigel McNie's avatar
      Change to how table names are specified in SQL queries. · 250cf34d
      Nigel McNie authored
      Now, table names (and other identifiers that could be confused with SQL kewords), should be put into SQL like this:
      
      SELECT * FROM {artefact}
      
      The braces are matched and expanded by DML now to include the prefix and be properly quoted, which means that tables like 'view' and 'group' don't need renaming (and nor should they, there's little reason why we should rename tables to get around such constraints).
      
      This has removed a whole bunch of $prefix = ... and get_config('dbprefix') stuff, which makes things a little simpler yet again.
      250cf34d
  24. 22 Jun, 2007 1 commit
  25. 31 Jan, 2007 2 commits
  26. 25 Jan, 2007 1 commit
  27. 24 Jan, 2007 1 commit
  28. 04 Jan, 2007 1 commit
  29. 18 Dec, 2006 1 commit
  30. 04 Dec, 2006 1 commit
  31. 23 Nov, 2006 1 commit
  32. 22 Nov, 2006 1 commit
  33. 13 Nov, 2006 2 commits