Posted by FreeFox on February 7, 2008 at 6:24pm
Jump to:
| Project: | Chatblock |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi, is it possible to have some kind of administration in the box? e.g. A clear chatbox would be nice.
Thanks.
Comments
#1
Do you mean like a particular user (an admin user) could clear all of the chatblock messages from the database using a button? Could you be more specific please?
Thanks,
Dave
#2
Thanks for the quick response.
Yes that is what i meant. The possibility to give a certain role an extra button beside the [Send] button to clear the full chat.
I noticed too that it would be very helpful if there were two other possibilities:
- Deny chatting for certain users, I mean typing text to the chat. But they should still be able to read. I know the access has view and post access settings but I mean some kind of blacklist. All user behave except a few so ...
- When typing text in the input box and you press the enter key quickly then you can post the same text again and again (spamming). So maybe a filter to prevent the same user to send the same text within xx seconds
That are the most important things I miss now.
Thanks for the nice module.
Jan
#3
Regardless of where the button is, I would also like to have some kind of "Clear Chat" option, since I don't have access to the database to do it manually on one site I'm building.
#4
A small extra button beside the [Send] button with the code "TRUNCATE TABLE `chatblock`" would do the trick I guess. Maybe an entry in the settings page to define which roll can see this button.
Dwees could you please implement this?
Thanks in advance
Jan
#5
Yeah this is crucial. I'll try and work this into the next release.
#6
Manual DB cleanup will be in the first stable release. But D5 will be no longer pursued unless anyone else wants to do that.
#7
The feature has been implemented and will be available with latest dev snapshot.
#8
Automatically closed -- issue fixed for 2 weeks with no activity.