SMF Development > Feature Requests
Announce topic to send copy to sender - avoid repeated announcements
Arantor:
That way lies madness... what happens if you want to reannounce a topic after a major change, say after a week? Then you'll need to implement a setting to figure out after how much time to purge that setting.
As opposed to just sending the sender an email.
emanuele:
--- Quote from: Arantor on June 05, 2012, 03:16:30 PM ---It's not actually an option, as per the above query, it actually expressly just filters out the sending user.
--- End quote ---
Well, I was thinking more along the line: in the function Post LEFT JOIN a log table where is recorded if the topic has been "announced" and if it has been already announced don't show the checkbox (and to be consistent repeat the LEFT JOIN in Post2 too), not in that query in particular.
Arantor:
So you announce a topic. Under that logic you will never be able to announce that topic again, not even if - say - it's rules and you update them with new information.
There's no solution in that scenario for ever allowing users to re-announce a topic, and setting up some kind of 'you can announce it again in x days' will invariably cause more confusion than the current setup.
emanuele:
Exceptions are the rules here! :P
Honestly I really think a sort of limit is necessary: give the announce topic permission to regular users means you are giving spammer the ability to spam all your members by email with a single post (don't know if this is the case, but I feel it's likely to be) and it will come from your forum.
I wouldn't see as terrible to limit the announce of each topic to 1 for everybody except admins (of course from that in the future people will ask for a permission, but at that time I'll not be interested in forum any more so it will not be my problem! :P)
Anyway, if you want to change the rules you can always write a new topic and announce the new topic.
igirisjin:
People often re-announce topics that have important updates - its useful.
Great for club event management and flexible enough to limit it (only member groups) using permissions.
Its just that all the effort made to inform people about correct usage doesn't seem to work. Easy to label people 'dumb' but its more a case of they are too lazy to read anything and basically don't care. Using it like a mailing list (which they expect) that sends out a copy to everyone would go a long way to avoid misunderstandings by users ... 'user-proof' specifications :)
I will try the edit anyway - thanks for that!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version