Search results

Exactly!

Well, you said; You can prevent "Include thread starter posts" option from triggering when creating a thread, you can limit it to trigger only if post position != 0, I'm talking about the position column in xf_post table. Posts with position 0 mean it's the first post (the thread itself).

Certainly, if there are no restrictions for users with negative credits, then the add-on itself will be useless. For this reason, I mentioned in the above example the ability to restrict access for users who have negative credits when they reach X negative credits.

Yes, the suggested option to give credits to thread author when he reply in his own thread.

Thread event targets posts with position 0 (first post), the "Include thread starter posts" option should exclude posts with position 0.

It's up to site admin he can either make the event charged or not. Even if the "Not charged" option used you still can restrict access for users with negative credits using usergroup promotions. The example below to move users who have less than -5 credits to specific usergroup. Implementing...

A couple of suggestions would make the overlay look better. Display user name through action_user_id column, the creation date of transaction from transaction_date column, and the same for modified credits. The thread URL should redirect the user to post_id of the transaction.

The add-on doesn't support counting thread starter posts, so it would be nice to have an option in the posts event to include thread starter posts in own threads.

The transactions created for posts event get removed automatically if you repeat the rebuild process. Steps to reproduce: Create a post Run rebuild for posts event A new item will be inserted in xf_xs_cs_credits_transaction table Rebuild posts event again The item created in step 3 will be deleted

Posts didn't get added instantly once its posted like threads and must run cron job.

The current behavior of how the add-on deal with negative numbers doesn't support the main idea of this add-on which allow creating custom method for calculating user credits. For example, if user has 2 threads, 1 post and 6 replies, we used a simple method ({threads} + {posts}) - ({reply}) it...

What about adding an option to trigger the event even if the user doesn't have enough credits? Do you mean you can't store negative numbers in the database?

Thread id, post id, reply id or reaction id should be stored in entity_id column not event_id column and event id should be stored in event_id not entity_id.

Yes, it's not a bug. I installed the add-on on my testing board which includes some posts with invalid thread id.

Transactions related to a thread haven't deleted when permanently delete that thread.

As the title says.

Well, can you at least make user criteria and color property support negative numbers? And;

Received reactions didn't get added instantly like posts even when running cron job. You must run rebuild reactions manually.

The add-on missing an option to specify locations where user credits displayed. Profile Postbit

It's possible to make the input field in node permissions support negative numbers just like the credit field in event options? It must support negative numbers since the add-on allows the user to create own method for credits calculation, therefore the user may use a method result in a negative...