Currently adding a venue can only be done by the admin. This is not very useful because we cannot know what venues users want to add. Users should be able to post venues.
Some people just get too riled up and type before thinking. They keep posting new replies. For such situations it would be very valuable to have a post flooding limit. So that the user cannot keep posting replies one after the other. This would force the member to wait a certain time or to wait...
@NixFifty
I am seeing the following warnings in Google Search Console:
Missing field "eventAttendanceMode"
Missing field "offers"
Missing field "eventStatus"
Missing field "performer"
Missing field "organizer"
I don't think this has been fixed. Please address this. As you may know a lot of...
Reassign a ticket reply to another user. For example: a user opens a ticket as a guest, then creates an account. I can reassign the ticket to the new account, but not the replies the user made.
It occurs frequently that a Report requires member communication. It would be useful to have the following functionality:
Open Ticket for the Reporter from the Report. Add an 'Open Ticket' function to the report.
Open Ticket for the Reported Member from the Report. Add an 'Open Ticket'...
This one is becoming quite urgent. We frequently get sensitive and personal information in tickets which falls under the GDPR. If we would ever get hacked and the ticket contents leaks then this would not only be a disaster in itself, but we would also be liable for millions in fines. That would...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.