quotas and/or export messages
catch - October 6, 2006 - 16:43
| Project: | Privatemsg |
| Version: | 5.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Zen |
| Status: | closed |
Jump to:
Description
Hi,
Our privatemsg table is 10mb, and it'd be handy to have one or both of the following options:
quotas - ideally by role, so the number of private messages can be limited per user.
An export function - where you can download all your pms in a csv file, or hook into the printable page module (so we can warn people then wipe the table).
Is there any move towards either of those?
#1
I have to admit i would be something we could do with too. Ours is growing at an alarming rate :)
#2
Updating version number and thinking of ways to do this.
The quota would have to work when actually sending a private message (plus maybe a "your pm quota is full" message in the index), checking the number of pms associated with both the sender and recipient (because pms will also go in sent items).
So user sends a message, and it checks the number of pms associated with their uid, then checks the number of pms associated with the recipient id, throws out a message if either are over the limit.
Will think some more.
#3
A simple way to have a time based quota. Purge messages older than certain time (say 6 months). That way a cron script can be written to delete all message with age higher than threshold. Not an ideal solution but a good start.
#4
+1
#5
+1
#6
The pm_archive module which has just been committed does auto-archiving of messages older than x. It is new and not very well tested and suffers from a few obvious limitations. Reviews and more importantly, patches are welcome.
-K
#7
Zen, thanks very much for this. We ended up with a very limited custom solution (printing all pms to screen so they can be saved locally). I'll try to upgrade to latest dev snapshot of private messages and review soonish.
#8
Automatically closed -- issue fixed for two weeks with no activity.