SMF Development > Applied or Declined Requests

Announce topic to send copy to sender - avoid repeated announcements

<< < (4/5) > >>

igirisjin:

--- Quote ---Personally, I think that all announcements of events by non-moderators should be posted in only 1 forum named something like "Members Events" for all to read. Another forum I belonged to had this special forum and it worked very well. You could divide it by regions or however. And, then only the moderators and higher level people can send event notices if they so choose. This is because spammers are clever and will attack a site by taking advantage of however that feature is coded. Even people who seem ligit can do this.
--- End quote ---

It is used in an events board and newly registered users do not have the permission to enter it or use announce topic - only higher level groups.

Having moderators or only admin use it doesn't work for event groups - they have to be there online all the time to make sure events get sent out - not workable.
Its a simple case of people expecting to get a copy when it is announced. It would a lot of time for admin having to shut people out, explain, try and delete hundreds of emails from the queue... etc etc.
Some events are planned Friday evening so it is needs sending out  People dont log in every day or every few hours to check for new events.

emanuele:
I'm not saying this should not be done (I don't care at all about the single email), I'm just saying that we are controlling how many PMs a member can send in 1 hour and how many members he can put in copy, but we are not checking how many announcements are sent by a single user in any time frame (i.e. a single user can spam any amount of announcements (the only indirect check is the spam flood on the creation of a new post and that's all as far as I can see).

Yoshi:
Maybe a switch for that edit that sends a copy to the sender will work, like "Send a copy to the sender" when announcing a topic?

Although something as Arantor said will wokr out too.

Arantor:
Personally I think it should just be sent to the user anyway, not needing a switch (because I think that's just overly complicating things) and that there isn't really any need to permission-control it either.

Announcing isn't something allowed for all groups by default (unlike PMs) and if you have a member that abuses it, revoke their permission, simple as that. There is no need to make this any more complicated than it already is when all the tools are already available to do the job.

emanuele:

--- Code: ---commit b7a8a438e7135353e8e66be3bc3b8037909977ec
Author: emanuele
Date:   Mon Jul 2 2012

    Let's send the announcement to the announcer too [Topic 478383]

--- End code ---
And:

--- Code: ---commit 926dd292d84f56507ce5f54be8446502a3cc85b4
Author: emanuele
Date:   Tue Jul 3 2012

    Logging the announce action and show a warning when editing the first message of the topic (NOT TESTED) [Topic  478383]

--- End code ---
Though I was too lazy to create yet another info box, so I used a notice message (that says "an error occurred"), well it's in its own branch, so I'm not even sure it will be integrated. :P

Navigation

[0] Message Index

[#] Next page

[*] Previous page