Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
autumnwalker Posted October 27, 2016 Posted October 27, 2016 Hello, Is it possible to allow a user who has created a calendar event to delete or hide their own event? I cannot find the permissions to configure this. Thanks!
Adlago Posted October 27, 2016 Posted October 27, 2016 5 hours ago, autumnwalker said: Hello, Is it possible to allow a user who has created a calendar event to delete or hide their own event? I cannot find the permissions to configure this. Thanks! Permissions are made in setting groups. I think all members would be incorrect. Create a new group member. Make permissions calendar for this group. Edit this group result Move those members that you want in this group.
autumnwalker Posted November 1, 2016 Author Posted November 1, 2016 Ah ok - so "content" is calendar invites as well? Got it. Is there a way to separate types of content? e.g. allow users to delete calendar events, but not posts?
Joel R Posted November 1, 2016 Posted November 1, 2016 4 hours ago, autumnwalker said: Ah ok - so "content" is calendar invites as well? Got it. Is there a way to separate types of content? e.g. allow users to delete calendar events, but not posts? Unfortunately, not at this time. Content is treated globally by IPS, so editing and deleting will be applicable to none or all content items. There have been numerous requests in Product Feedback regarding this topic.
Adlago Posted November 1, 2016 Posted November 1, 2016 5 hours ago, autumnwalker said: Is there a way to separate types of content? e.g. allow users to delete calendar events, but not posts? Yes, there is a solution. Follow these instructions: 1. Copy your default theme and rename copy_theme ->'staff_name'. This theme should be permitted only for your staff team. 2. Add in Custom CSS your default theme #elTopicActions{ display:none; }
SteffM Posted November 1, 2016 Posted November 1, 2016 1 hour ago, Adlago said: #elTopicActions{ display:none; } 1. This will leave a security issue since the server side will still handle the request.... 2. Simply unhiding it via chrome dev tools would allow someone to do this without knowing how making requests work
Recommended Posts
Archived
This topic is now archived and is closed to further replies.