About This File
This plugin will give the admin the ability to choose which reactions each user group will be able to use across the suite. User will see only allowed reactions.
An error message will show up if the user tries to react directly via URL using a non allowed reaction.
Yes, it extends the regular registration screen, which users from social media doesn't use. It would be stupidly easy if it was a app but it's a plugin. I'll take a look in a further version.
What's New in Version 1.0.17:
New features:
Add a new setting to give the admin the ability to add new registered members as a MEMBER in selected clubs when they create the account.
Members will be deleted if the admin deletes the account
Add a new setting: Allow Club Owners to change Club ownership?
Added a button as a template by request.
About This File
This plugin will give admin the ability to choose a group to move the member when a moderator bans this member via Warn System:
Setting:
Choose group where members will be moved to
It already happens when you MOVE an item to a club:
The ENTIRE forum, no. That would be crazy. I see forums with 100,000, 300,000, 500,000 ... topics. If only each topic has 3 replies, it would be huge resource usage. I won't do that.
Open applications\cjcontact\sources\Contact\Contact.php and find:
$member = \IPS\Member::load( $this->department->member );
Change to:
$member = \IPS\Member::loggedIn()->member_id ? \IPS\Member::loggedIn() : \IPS\Member::load( $this->department->member );
It will use the logged in member as topic author if it's a registered user and the member chosen in department settings if it's a guest.
I never used Patreon so not sure I'm replying what you asked. This app has a donation goal. By default it requires a goal (per category):
When submitting a project:
I never used Patreon so not sure what you're talking about.
You didn’t understand. The issue is PERMISSION, like John Doe trying to create a topic in a forum where he can’t. That is the problem.
So now you say: “I will choose a proper forum”. Then I say: you’re not alone; more 53 clients uses this resource so there’s a HUGE chance of someone set up it wrongly, which will result in support request, bad review... you know, all the drama involved. So most likely I won’t add this.
But easy enough to show you how to do it. I’ll post the edit tomorrow then you do in your install.
You want a setting to make one chosen member always be the topic author?
Sorry, you want the form submitter to be the topic author? That can bring an issue: the class post checks permission when creating a topic and will fail if the author hasn't permission to do so. The topic will not be created.