Update highlights
I'm proud to present the first Beta version of DragonByte Credits v7, a significant update for functionality and usability!
As you can see by the length of the changelog, this is a large update with many changes, though nothing should change visually for your users - the entirety of the update is concentrated on internal changes to not only make it easier to use for admins (both new and experienced), but also prepare for future updates.
Event Configuration has been updated, with events now hiding certain configuration fields that did not make sense for that particular event trigger.
Event Negation is now handled by reading the transaction log, eliminating the need for you to configure "Negation amounts" per event.
Currency Handling has been improved by eliminating the "Negative currency handling" setting, favouring a more intelligent handling that preserves the functionality of users actually receiving error messages when attempting to be charged (f.ex. buying access to a thread) if they cannot afford it.
Lastly, ground work has been laid for being able to apply certain events, such as reaction events, to more content containers than just a forum post. This functionality will be fully implemented in a future update.
---
If you would like to read a more detailed explanation of the changes in v7, please see this thread: https://www.dragonbyte-tech.com/threads/dragonbyte-credits-v7-extended-release-notes.26918/
Complete Change Log
Feature: Event negation no longer relies on calculating a negation amount
Feature: Add the ability for event triggers to disable taxation from event configuration
Feature: Improved event configuration for added customisability
Feature: The Trophy event now supports selecting "Any" to match any trophy
Feature: The Reply event now supports word/character multiplier, similar to Post event
Change: [BREAKING] Passing the user entity toundoorapplyis now required, otherwise the trigger will not occur
Change: Internal changes to prepare to support more container types than just "Forum"
Change: Moved event trigger code from entities/services to event trigger handler
Change: Use generic "container content type" rather than hardcodingThreadandPostetc checks
Change: Remove unusedForumrelation onTransactionentity
Change: AddContainerContentmethods toTransactionentity
Change: AddContainersupport toPostandThreadentities
Change: Internal changes to reflect smart event negation
Change: Remove "Negative handling" setting from currency configuration
Change: Remove "Negation" settings from event edit forms
Change: Removed "Adjust" event configuration to ensure system integrity
Change: Removed "Taxed user" configuration from Purchase and Redeem event triggers
Change: Removed the ability to set Purchase, [CHARGE] BBCode, and Redeem event triggers as "Charged"
Change: Removed "Event amount" options from Payment Profile event config
Change: Removed Frequency options from Content, Content Access, Donate, Payment Profile, Purchase and Transfer event configs
Fix: Transaction alerts are now deleted when a transaction is negated
Fix: Harden applicable Event Triggers to prevent errors during rebuild
Fix: Fix CLI jobs using incorrect reference
Fix: Fix "Any" selector not working correctly for React/Reacted events
Fix: Fix issue where cache would not rebuild reliably
Fix: Errors are now only shown when negating transactions that would result in a loss of currency
Fix: Fix a potential bug with checking for the existence of certain events
Fix: Validate the reaction selection on save
Fix: Fix "Frequency" options not working in conjunction with "Transactions are moderated"
Update highlights
This version updates the various log pages to allow search criteria to persist when clicking back into the search form.
Furthermore, a fix to the various currency number input boxes will now allow values below0.01(up to 8 decimals).
Complete Change Log
Change: Criteria are now carried over when clicking the Search button in log pages
Fix: All currency input boxes can now use up to 8 decimals
Update highlights
This version improves compatibility with future versions of XenForo by moving certain code calls out of templates. This update is recommended to avoid compatibility issues with the upcoming XenForo v2.3.8 & newer.
Furthermore, a new "Maintenance" page has been added, providing easy access to the various rebuild tasks available in this addon.
The "Post Like" and "Post Liked" event handlers are now disabled, as they no longer apply. Please make sure you use the "React" and "Reacted" event handlers instead.
Lastly, a regression from v6.1.0 has been resolved, by adding support for "Negated" transactions to the AdminCP transaction log. The front-end transaction log is unchanged as it did not suffer from this problem.
Complete Change Log
Feature: Created a new "Maintenance" page for easy access to the "Rebuild caches" options available in this addon
Change: Disable the "Post Like" and "Post Liked" event handlers as they are deprecated
Change: Move database query calls from templates to PHP files
Fix: Fix Negated transactions not showing in the AdminCP
Update highlights
This version contains a significant improvement in how event negations are handled. Rather than inserting a new transaction, where possible, the existing transaction will be updated to be flagged as "negated". Primarily, this means negated events will work correctly with events that have a limit on how often they can be triggered.
Furthermore, internal changes have been made to support upcoming changes in XenForo 2.3.8.
Complete Change Log
Feature: Improved event negation
Change: XenForo 2.3.8 compatibility
Change: Apply content type to additional events
Change: Internal changes to better support the improved event negation
Update highlights
This version primarily fixes an issue with extremely large negative numbers in events such as Taxation. Furthermore, the Daily Credits cron job has an improved activity detection so it should no longer lag behind in certain circumstances.
Complete Change Log
Fix: Use a better method for detecting latest activity for the Daily Credits cron job
Fix: Fix an issue where extremely large negative currency values could trigger server errors
Update highlights
This version changes the way credit expiry works, to avoid a scenario where the user no longer has enough credits to deduct. If negative currency handling is set to "Disallow", expiring credits will now reduce the user's balance by 0 and skip any further expiration events.
Furthermore, a few reported bugs have been resolved.
Complete Change Log
Change: Cap credit expiry to user's max credits when negative handling is set to "Disallow"
Fix: Fix issue when disabling navbar items from the Public Navigation page
Fix: Check whether the adjust event succeeded before printing success message
Fix: Check whether the transfer event succeeded before printing success message
We use essential cookies to make this site work, and optional cookies to enhance your experience.