[DBTech] DragonByte Credits 7.3.2

Update highlights​

This version adds a new "Keep credits when the thread is moved" setting for the Thread event, which stops credits from being taken back when a thread is moved to another forum. It can optionally still award credits when a thread is moved into one of the event's forums.

Complete Change Log​

Feature: New "Keep credits when the thread is moved" setting for the Thread event

Update highlights​

This version fixes an issue with the currency donation feature, as well as resolving a couple currency privacy issues.

Complete Change Log​

Fix: Donations no longer fail with an "outside the range allowed for this action" error
Fix: Currencies are now considered unviewable if the user doesn't have the "View" permission
Fix: Currency displays like the postbit now correctly respects the "Self and designated user groups" privacy option

Update highlights​

This version adds support for XenForo Resource Manager and DragonByte Manuals Library to the "Content Access" system that was previously occupied only by threads.

For the XFRM, the resource can be viewed, but downloading (or accessing the external URL) requires the content access payment.
As for DragonByte Manuals, only the description/custom fields can be viewed. Reading or downloading the manual requires the payment.

Furthermore, a few bugs have been resolved.

Complete Change Log​

Feature: Content Access now supports XenForo Resource Manager resource downloads
Feature: Content Access now supports DragonByte Manuals Library manuals
Fix: Paid content is no longer accessible to guests when a Content Access event was configured
Fix: Fix the "All" container content type not working for React/Reacted events
Fix: Fix regression causing content links to no longer appear in the transaction log

Update highlights​

This version fixes an issue with the new React/Reacted event content types added in v7.2.1, as well as further widening the negative balance changes to include all actions taken by a moderator.

Complete Change Log​

Change: Moderators can now delete, restore or approve content, including their own, regardless of the author's credit balance
Fix: Reaction events limited to specific XFRM, XFMG or XenAddons categories now trigger for content in those categories

Update highlights​

This version adds full content type support to the "React" and "Reacted" events, so they can be used with all content types supported by Credits. It also allows for choosing "Any", which would trigger the events even for content types not yet supported by Credits.

Furthermore, a fix has been created for a recent compatibility issue with @Xon's Signup Abuse Blocking (an excellent addon you should also check out!)

Lastly, moderators and other users undoing an event (for example; a moderator deleting a post, or someone removing a reaction) now allow the receiving user's balance to go into the negatives. This was a regression from v6 where such actions were not blocked due to balance issues.

Complete Change Log​

Feature: Add support for additional content types to the React and Reacted events
Fix: Fix compatibility issue with Xon's Signup Abuse Blocking
Fix: Moderators and other users can now remove content even if its author no longer has enough credits to cover the reversal

Update highlights​

This version focuses mainly on bug fixes, but it does contain one new feature; You can now optionally allow credits expiry to take members into the negatives. This can help prevent users racking up expiring credits, spending them all, then not being able to have the credits deducted. You can turn this feature on or off by editing the "Expiry" event in the AdminCP, and it's off by default (to preserve current functionality).

The other notable change is the fact that the "Payment" event where you use DragonByte Credits as your payment profile for other things (such as DragonByte eCommerce purchases, or user upgrade purchases), can no longer place its transactions under moderation. This is to prevent various issues relating to balance calculations.

Beyond that, a bunch of smaller bugfixes have been completed. See the complete changelog for details.

Complete Change Log​

Feature: New "Allow balance to go negative" setting for the Expiry event
Change: Saving an event now redirects to the correct currency tab
Change: The Payment event can no longer be moderated, as a purchase cannot wait for approval; any existing moderation setting on it is ignored
Fix: Fixed adding new events not correctly using the currency you're currently viewing
Fix: Credit expiry no longer stalls when expiring credits exceed the user's balance; only the remaining balance is removed unless the new setting is enabled
Fix: Events with a frequency above 1 no longer apply on every trigger after the first when several are triggered at once, such as uploading multiple XFMG media items together
Fix: Applying an event now returns the transactions it saved, instead of an empty list, so integrations can tell whether credits were actually applied
Fix: Paying with the DragonByte Credits payment method no longer completes the purchase when no credits were actually taken, such as when the payment event does not apply to the user or the charge was skipped
Fix: Buying a credit package no longer also awards every other package on the same currency that gives the same amount of credits
Fix: Buying or gifting credits to a user who cannot receive them is now refused before payment, and a payment that could not award, re-add or remove credits is logged as an error instead of a success
Fix: Refunding or reversing a credit purchase now removes exactly the credits that purchase awarded, including any bonus, even if the balance goes negative or the user can no longer earn credits; a purchase still awaiting approval is cancelled instead
Fix: An event's maximum amount no longer caps the amount used by other events triggered by the same action
Fix: Donations and currency transfers are now refused when the amount is outside an event's minimum or maximum, instead of taking a capped amount from the sender while crediting the full amount to the recipient
Fix: Redemption code usage limits can no longer be bypassed by entering a numeric code in another form (such as "1e2" for "100") or by redeeming it in several requests at once, and limits are now counted per event rather than shared with the same code on other currencies
Fix: Unlocking paid content (the CHARGE BB code or content access) can no longer charge the buyer or pay the owner twice when submitted twice at once
Fix: Unlocking paid content is now refused, without charging the buyer, if the buyer's charge would be skipped or limited by an event's minimum or maximum
Fix: Added the missing "You have already unlocked this content." phrase
Fix: An event's maximum number of applications is now counted across all users when "Limit maximum applications per-user" is disabled, instead of always being counted per user
Fix: Spending credits no longer frees up room under a currency's earning cap, so giving credits away can't be used to earn past it, and spending is no longer blocked for users already over the cap
Fix: Rebuilding donation, transfer and purchase transactions no longer applies bonuses, fees and tax a second time, which changed user balances on every rebuild, and donation and transfer rebuilds now only use the event that was originally applied
Fix: Transactions now store fractional multipliers, such as donation amounts or exchange-rate conversions, instead of truncating them to whole numbers
Fix: Unlocking a CHARGE BB code whose content has been deleted no longer causes a server error
Fix: Paid content can no longer be unlocked by users who are not allowed to view the post, thread or other content it belongs to
Fix: Content access can no longer be "unlocked" for content that has no access cost or currency set, or by the content's own author or staff, who can already access it
Fix: The gift purchase page now only accepts an active credit package belonging to the currency being viewed
Fix: Paying with a DragonByte Credits payment profile whose currency has been deleted now shows an error instead of causing a server error
Fix: Currency transfers are now refused when transferring to the same currency, or when either currency has a value of zero or less, instead of farming the event's base amount or causing a server error
Fix: Checking whether a credit package can be purchased no longer causes an error in debug mode when the package is missing its cost or amount settings
Fix: Quoting a post, conversation message or XFMG comment no longer reveals CHARGE BB code content that the quoting user has not unlocked, whatever form the tag's cost is written in
Fix: An event's random addition now adds a random amount between 0 and the configured value, instead of adding the decimal part as a whole number (such as 5–7 for a value of 2.5), and negative values no longer cause an error
Fix: Currencies with transfers out disabled can no longer be transferred from by submitting the transfer form directly
Fix: Deleting content now also cancels its transactions that are still awaiting approval, so they can no longer be approved afterwards, and any credits held for a pending charge are returned
Fix: Merging users now keeps the merged user's transactions, unlocked content and logs, which were previously deleted along with that user, and moves any credits held for pending charges
Fix: Credits from an event with an expiry setting now expire when the transaction was held for moderation and later approved, counted from the time it was approved
Fix: Changing the cost in a CHARGE BB code in an XFMG comment or XFRM resource update now takes effect, instead of the original cost continuing to apply
Fix: Paying with the DragonByte Credits payment method no longer keeps the credits when the purchase fails to complete, and submitting the same payment twice no longer charges or completes it twice
Fix: Deleting a user no longer deletes other users' transactions that the deleted user sent or owned the content for, such as donations they made or reactions to their posts, and their own pending transactions are removed from the approval queue
Fix: Deleting or hiding content whose credits have already expired no longer removes those credits a second time, and no longer fails because the user's balance is too low to cover credits they had already lost
Fix: Buying credits and receiving credits from a sale paid with DragonByte Credits are no longer blocked by the currency's earning cap, which could take a payment without awarding any credits, and they no longer use up the user's allowance for earning credits in other ways
Fix: Expiring credits are now removed from users who can no longer trigger events or are not in the Expiry event's user groups, instead of being skipped and never expiring, and credits in an inactive currency now expire once the currency is reactivated
Fix: The "Content ownership restriction" setting on the content access event now works the same way as for the CHARGE BB code, instead of still paying the content owner when restricted to others' content and blocking every unlock when restricted to own content
Fix: A CHARGE BB code cost written with a decimal comma, such as 2,50, now charges the full amount instead of dropping everything after the comma, which made costs below 1 free for everyone

Update highlights​

This version brings the biggest update to addon integrations in Credits' history, alongside continued improvements to the Rebuild feature.

Continuing the work from Beta 1, the rebuild feature no longer offers the option to reset currency values to 0 (balances would always be recalculated anyway), and in its place it now offers an option to reset only rebuildable data.

A change from Beta 1; the Balance rebuild jobs now always run after rebuilds, to avoid having to worry about catching every case the balances have been affected. If this turns out to be disruptive, I'm open to changing it in future versions

With that out of the way; DragonByte Credits now features integration with all of Bob's excellent add-ons, as well as integration with all other DragonByte addons!
The full changelog describes all events, but here's a quick list of addons now supporting integration:

• DragonByte eCommerce
• DragonByte Reviews
• DragonByte Social Groups
• DragonByte Shop
• [XenAddons] Article Management System
• [XenAddons] Classified Ads System
• [XenAddons] Glossary System
• [XenAddons] Knowledge Base System
• [XenAddons] Link Directory integration
• [XenAddons] Review Management System
  [XenAddons] Showcase
• [XenAddons] Ticket System
• [XenAddons] User Blog System

In addition, over 20 smaller bugs have been identified and fixed. Please see the full changelog for details.

Complete Change Log​

Feature: DragonByte eCommerce integration: Product, Product Rate/Rated, Product Release, Product Download/Downloaded and Purchase events
Feature: DragonByte Reviews integration: Subject, Review/Reviewed and Review Comment/Commented events
Feature: DragonByte Social Groups integration: Group, Join Group/Group Joined, Discussion, Message and Discussion Reply events
Feature: DragonByte Shop integration: Item and Item Rate/Rated events
Feature: [XenAddons] Article Management System integration: Article Rating, Article Rated
Feature: [XenAddons] Classified Ads System integration: Ad, Answer, Answered, Comment, Commented, Feedback, Feedback Replied, Feedback Reply, Feedbacked, Item, Offer, Offered, Question, Questioned
Feature: [XenAddons] Glossary System integration: Comment, Commented, Glossary, Term
Feature: [XenAddons] Item Management System integration: Answer, Answered, Item, Page, Question, Questioned, Review, Review Replied, Review Reply, Reviewed, Series, Update, Update Replied, Update Reply
Feature: [XenAddons] Knowledge Base System integration: Article, Helped, Helpful Vote, Page
Feature: [XenAddons] Link Directory integration: Answer, Answered, Click, Clicked, Comment, Commented, Item, Question, Questioned, Rate, Rated, Rating Replied, Rating Reply
Feature: [XenAddons] Review Management System integration: Answer, Answered, Check-in, Check-in Comment, Check-in Commented, Event, Event Comment, Event Commented, Item, Location, Location Comment, Location Commented, Question, Questioned, Review, Review Replied, Review Reply, Reviewed
Feature: [XenAddons] Showcase integration: Comment, Commented, Item, Page, Rate, Rated, Rating Replied, Rating Reply, Series, Update, Update Replied, Update Reply
Feature: [XenAddons] Ticket System integration: Staff Comment, Ticket, Ticket Message
Feature: [XenAddons] User Blog System integration: Blog, Blog Entry, Blog Page, Comment, Commented, Entry Page, Rate, Rated, Series
Feature: Transaction rebuild: Only delete rebuildable data
Change: Transaction rebuild: Removed "Reset all currencies to 0" option
Change: Transaction rebuild: Rename parameters
Change: Transaction rebuild: Always run the two balance rebuild jobs, even if only one content type is rebuilt
Change: Updated XFRM and XFMG phrase text
Fix: Fix missing alert opt-out phrases
Fix: XFMG Rate/Rated handlers no longer throw errors
Fix: Properly update the [NF] Calendar integration to match the schema change in v7.1
Fix: Hard-deleting a thread now correctly undoes any events applied to the deleted posts too
Fix: Fix removing content tags deducting more credits than intended
Fix: Fix removing attachments deducting more credits than intended
Fix: Setting Interest, Taxation or Paycheck intervals to 0 will no longer infinite loop
Fix: The Donate event no longer has the possibility of removing credits from one user without also applying it to the other user
Fix: The Transfer event no longer has the possibility of removing credits from one currency without also applying it to the other currency
Fix: The "Thread ID" setting on the Post and Reply events no longer prevents the event from ever triggering
Fix: Fix incorrect amount listed in the Transfer alert
Fix: Fix typo in Transfer event triggering code
Fix: If a reversed Purchase transaction is restored, the purchased currency is now correctly reinstated
Fix: Fix the reference ID for tags
Fix: The Poll event trigger now only retriggers if the number of responses changes
Fix: Fixed the "Include guest event triggers" setting for the "Visit" event trigger
Fix: Fix a SQL error when rejecting a transfer
Fix: Reassigning content could leave the previous owner's credits intact
Fix: Editing conversation messages no longer generates extra credits
Fix: Purchase and Redeem rebuilds replay the log instead of re-checking today's event settings
Fix: Editing the first post re-credits only when the post and thread are visible
Fix: The Thread event now correctly only reverses the thread credit when the deleted post is the first post
Fix: XFRM Update event trigger once again works correctly
Fix: Add additional checks to the Payment handler to prevent race conditions

Update highlights​

This version brings significant overhauls to the transaction rebuilding feature, aimed at improving reliability and general functionality.

Historically, the rebuild feature has had two significant problems:
1. Rebuilding with the "Truncate" option enabled is destructive, as it deletes transaction data that cannot be recovered
2. Rebuilding without the "Truncate" option inserted duplicated transaction records which would significantly upset the credits balances

v7.2 takes the first step towards resolving these problems by eliminating number two on that list. Rebuilding without "Truncate" now deletes duplicate transactions that may have been inserted by past rebuilds, as well as recomputes the "Balance" column for each transaction entry, and finally updates the user's balance to match the new balance indicated by the transaction log.

In other words: after a fresh rebuild, the transaction log's balance is taken as the source of truth for what a user's spendable balance should be. This results in the transaction log and the user's spendable balance actually agreeing (I know, what a concept that is ).

If you have in the past used the "Adjust" feature to correct balance drift, you can use the new Adjust log in the AdminCP to delete such entries (or any other adjust entry), then rebuilding again (without "truncate") and the corresponding transactions will also be removed.

The upcoming v7.2 beta versions will further improve on the rebuild feature by correctly identifying old deleted content and removing those transaction log entries, for more content types than just the adjust log.

---

The most noticeable change in v7.2 is the fact that currency input boxes now use the correct amount of decimals for their inputs. If your currency is configured to use 0 decimals, you should no longer see 50.00000000 etc.

Complete Change Log​

Feature: Adjust log
Feature: Ability to rebuild user balance directly from the transaction log
Feature: Transaction Balance and User Balance can now be rebuilt via CLI
Change: Currency input boxes now clamp to the correct amount of decimals
Change: Update requirements for addons Credits integrates with
Fix: Transaction rebuilds are much more robust
Fix: Fix rebuilding [XenAddons] Article Management System "Comment" and "Comment" handlers
Fix: Fix incorrect table data affecting new installs using the [NF] Calendar integration
Fix: Fix config flags in the Adjust event being dropped unexpectedly
Fix: Transaction filtering now redirects to a shareable link

Update highlights​

This version contains a couple of bugfixes as well as a new feature; the ability to automatically prune transactions older than X days. The cumulative balance is kept, so calculations continue to work.

Complete Change Log​

Feature: Automatically prune transaction log (default: disabled)
Fix: Fix incorrect job being queued after the upgrade to Beta 3
Fix: Fix race conditions with Conversation Message, Post, Reply and Thread event handlers

This add-on has been hotfixed to address an issue affecting all front-end pages while this add-on is enabled. This issue was caused by additional security measures introduced in XenForo 2.3.13.

The latest version has been patched, and can be downloaded at no additional cost. If you are running an older version and you are unable to upgrade for whatever reason, please let me know the exact version you are running and I will apply the hotfix accordingly.

Note: Both the latest Beta version and the latest Stable version of this add-on has been hotfixed.