I invite you to post here any question, bug report or feature request you would like to add in next releases.
If you need some help about Forum tags, take a look at the Boardcode FAQ. Before posting check up if your enquiry is not already included. Please, stick and respect the few Forum Rules.
Instead of using a "Purge Messages" through admin panel, why not limit the number of messages per user?
For example, in Invision Power Board forum, there is a meter telling you how full your PM folders are: "Your folders are 24% full"
You can limit it by the number of letters, or perhaps the number of messages, I don't know how it works. When they are full, they cannot send or receive PM's so they will have to delete some of it themselves. I just don't want to purge all people's PM's, they might get mad at me, because they might have important PM's stored there.
Thanks.
The administrator has disabled public write access.
Re:Number of messages limit 2007/01/30 02:21
Aclaina Admin
Posts: 903
Hi Rob,
Actually, when you purge messages, you're just deleting messages that are permanently deleted. Let's explain it a bit with an example:
You receive a message that was sent to you and to 3 other users. You delete this message and it shows in your trash. You delete it from trash and message won't be displayed for you anymore... But what happens to the other 3 users message? When you delete a message in Missus, the message is not completely deleted but "stated" as deleted by "you", not for the other 3 users, do you get what I mean? If I pemanently delete the message, the other users won't be able to actually see it. And the message is not duplicated in database either, to save space. So a state machine is used to determine the message state for each user.
Now, when you're purging messages you're actually deleting those messages that have been permanently deleted by both the sender and the receptors. I'll include a separate purge to delete messages by time because is needed, I can see my Missus table is longer than 400 KB in my database just because ppl never delete their messages. So I personally need that feature, but separated from the other purge.
Cheers!My components never has bugs... It just develops random features
The administrator has disabled public write access.
Re:Number of messages limit 2007/01/30 11:25
Rob
Newly Born Kitty
Posts: 4
Thanks, now it makes more sense (or most of it). But I think you might need to reword "Purge Messages" to something else, maybe "Purge Deleted/Trashed Messages" ??
Yes, I also agree about the timed purges, because I was also wondering about the database, so as not to overload it. I still think that limiting number of messages would also work, but then again I'm not the programmer.
The administrator has disabled public write access.
Re:Number of messages limit 2007/02/05 03:06
Aclaina Admin
Posts: 903
Hi Rob,
Rob wrote: Thanks, now it makes more sense (or most of it). But I think you might need to reword "Purge Messages" to something else, maybe "Purge Deleted/Trashed Messages" ??
Right! Sometimes I need help with my english, because I can't find the right words to express myself. (Or I misspell them)
Rob wrote: Yes, I also agree about the timed purges, because I was also wondering about the database, so as not to overload it. I still think that limiting number of messages would also work, but then again I'm not the programmer.
User have a limit of messages (you can set it in the config) and they can't receive new messages unless they erase some of them. But you're right about a percentage or a message displaying the Inbox status.
Cheers!My components never has bugs... It just develops random features
The administrator has disabled public write access.
Re:Number of messages limit 2008/05/09 13:21
Nils Ally
Newly Born Kitty
Posts: 2
Any "auto-purge" after "x" amount of days?
The administrator has disabled public write access.
All components and modules in this site are registered in Joomla! Developer and are protected under the GNU General Public License.
Development and support are just available until Mambo 4.5.3, these components will no longer be developed for Mambo future versions.
(Or I misspell them)