[XenDev] Participation Gate

[XenDev] Participation Gate 1.0.3

No permission to download

MPekel

Member
Licensed customer
MPekel submitted a new resource:

[XenDev] Participation Gate - [XenDev] Participation Gate

[XenDev] Participation Gate​



What is [XenDev] Participation Gate?​


[XenDev] Participation Gate is an advanced engagement add-on for XenForo 2.3 designed to turn passive readers into active participants.

Instead of allowing users to repeatedly open the same discussions without interaction, this add-on introduces a smart participation system that encourages members to reply, engage, and become part of the conversation.

It is...

Read more about this resource...
 
  1. Once the user posts a reply, the thread becomes permanently accessible for that user
- So how can a user reply a relevant post if they can’t no longer see the thread?

- Another classic issue is the user will just hit anything on their keyboard to reply the post as long as they can see the thread again. If the reply post can integrate with the AI API at least we can tell a prompt whether to allow it or put it in moderation
 
@MPekel thanks for the addon works well. It's Alpha but let me know if I can make a donation.

Here's the message I posted:

View quota exceeded.

{username}, you have exceeded your view quota on the {tittle} discussion.

To view this topic again, you must leave a message.

Note: the current system is good but we can no longer see the discussion to be able to reply to it.
 
  1. Once the user posts a reply, the thread becomes permanently accessible for that user
- So how can a user reply a relevant post if they can’t no longer see the thread?

- Another classic issue is the user will just hit anything on their keyboard to reply the post as long as they can see the thread again. If the reply post can integrate with the AI API at least we can tell a prompt whether to allow it or put it in moderation
Thank you, this is really valuable feedback.

You are absolutely right about the main issue: if the thread is fully hidden after the view limit is reached, it becomes much harder for the user to leave a relevant reply because they no longer have enough context in front of them.

That is one of the weak points of the current Alpha logic, and I agree it should be improved.

The second point is also valid: without any quality control, some users may simply type random text just to unlock the thread again. That creates activity, but not meaningful participation.

My current goal with the Alpha version was to prove the core concept first:
  • limit repeat views
  • require participation
  • unlock after reply

Now the next step is improving the participation quality and reply context.

The best improvements would probably be:
  • showing limited thread context instead of hiding everything completely
  • allowing the user to still see the first post or a short preview
  • adding minimum reply requirements
  • optionally sending weak/low-quality replies to moderation
  • and later, possibly integrating AI-based reply validation as an optional feature

So yes, I completely agree with your point:
the current system works, but users should still have enough context to write a meaningful reply.

And thank you as well for the kind words and the donation offer — I really appreciate it. Since this is still in Alpha, feedback like yours is honestly just as valuable because it helps shape the addon in the right direction.
 
@MPekel thanks for the addon works well. It's Alpha but let me know if I can make a donation.

Here's the message I posted:

View quota exceeded.

{username}, you have exceeded your view quota on the {tittle} discussion.

To view this topic again, you must leave a message.

Note: the current system is good but we can no longer see the discussion to be able to reply to it.
Thank you very much for the feedback and for testing the add-on.

You are absolutely right about this point.

In the current Alpha logic, once the user reaches the view limit, the thread is hidden and they are asked to reply in order to unlock permanent access. The problem is exactly what you described: if the discussion is no longer visible, it becomes difficult to write a relevant reply because the user has lost the context.

So yes, the current system works technically, but from a usability point of view it still needs improvement.

A better approach for the next versions will likely be to keep some context visible, for example:

  • showing the first post,
  • showing a limited preview,
  • or allowing the user to see enough of the thread to write a meaningful reply.
Your second point is also very important. Without any quality control, some users may simply type random text just to unlock the thread again. That creates replies, but not real engagement.

Because of that, I also agree that AI-assisted validation or optional moderation could be a very useful future improvement. For example, low-effort or irrelevant replies could be flagged, moderated, or prevented from unlocking access.

At the moment, the main goal of this Alpha version is to validate the core idea first. After that, improving reply quality and preserving enough discussion context will be the next priority.

Also, thank you very much for your kind words and for the donation offer — I really appreciate it. That means a lot.
 
In the meantime, I think that if you allocate a sufficient viewing quota to the group of members affected by the restriction, they will get used to the discussion and will be able to post messages without any problems. In the alpha version, I noticed that if a member posts a quick message and a moderator deletes it, the restriction is reapplied, which is normal.
 
Hello,

After several tests of your addon, we have identified two improvements that would make management more flexible:

Exclusion by forum/discussion: The ability to exclude certain sections (e.g., official announcements or updates) where member participation is not required.

Exclusion of closed discussions: The system should not apply to locked discussions, as members cannot technically post messages to lift the restriction.

Thank you for your work!
 
MPekel updated [XenDev] Participation Gate with a new update entry:

v1.0.2

  • - Option to exclude closed threads from the system
  • - Option to exclude sticky threads from the system
  • - Ability to exclude specific nodes / categories / forums
  • - Ability to exclude specific threads
  • - Manage excluded nodes and threads from the Admin Control Panel
  • - View sticky, closed, and normal threads separately
  • - Manage the list of excluded threads

You can manage these settings from Tools > Participation Gate.

Read the rest of this update entry...
 
Hello, thanks for the update! We’ve tested everything and it’s looking good, except for one specific edge case:

When a member who has lost access to a discussion posts a new message, they automatically regain access to that thread. The message then goes into 'pending approval' (as per our settings). However, if we subsequently delete that message, the user still retains access to the discussion indefinitely. Could you look into preventing this 'auto-grant' of access, or ensure access is revoked if the message is deleted?"
 
Hello, I took the liberty of modifying the Post.php file and now everything works. Also You just need to modify the blocking message to add the validation wait.

@MPekel I send you my post.php file for test
 
Back
Top Bottom