[DBTech] DragonByte Credits

[DBTech] DragonByte Credits [Paid] 7.3.2

No permission to buy (€14.95)
Love this addon!

We only use it to encourage more participation, and give users the ability to show appreciation for each other on our platform.

For the awesome developers, here are some issues we found implementing this addon since yesterday (these are definitely not deal-breakers, we just thought it would be useful for the developers):
  1. When you donate an amount, and have a negative tax, then the Alert shown around this event causes confusion.
    For example: Donating 1000 Merits with a -25% tax would be shown as the following (we like to encourage donating to others as a show of appreciation):
    1767825770798.webp1767825625714.webp
    IMHO it would be better if the Alert message in this case would state "You donated 1000 Merits to ..."

  2. Events for XF Resource Manager can cause an error during [DragonByte Credits: Rebuild transactions]
    (this was tested with [items to process per page] set to 500, 5000 and 50000, and [Delete all transactions...] to all different options, all made the same final error pop up)
    Code:
    Stack trace#0 src\addons\DBTech\Credits\EventTrigger\XFRM\RateHandler.php(105): XF::handlePhpError(2, '[E_WARNING] Att...', 'C:\\Websites\\for...', 105)
    #1 src\addons\DBTech\Credits\EventTrigger\AbstractHandler.php(887): DBTech\Credits\EventTrigger\XFRM\RateHandler->rebuild(Object(DBTech\Credits\XFRM\Entity\ResourceRating))
    #2 src\addons\DBTech\Credits\EventTrigger\AbstractHandler.php(834): DBTech\Credits\EventTrigger\AbstractHandler->rebuildEntities(Object(XF\Mvc\Entity\ArrayCollection))
    #3 src\addons\DBTech\Credits\Job\TransactionRebuild.php(84): DBTech\Credits\EventTrigger\AbstractHandler->rebuildRange(0, 5000)
    #4 src\XF\Job\Manager.php(275): DBTech\Credits\Job\TransactionRebuild->run(8)
    #5 src\XF\Job\Manager.php(205): XF\Job\Manager->runJobInternal(Array, 8)
    #6 src\XF\Job\Manager.php(121): XF\Job\Manager->runJobEntry(Array, 8)
    #7 src\XF\Admin\Controller\ToolsController.php(146): XF\Job\Manager->runByIds(Array, 8)
    #8 src\XF\Mvc\Dispatcher.php(362): XF\Admin\Controller\ToolsController->actionRunJob(Object(XF\Mvc\ParameterBag))
    #9 src\XF\Mvc\Dispatcher.php(264): XF\Mvc\Dispatcher->dispatchClass('XF:Tools', 'RunJob', Object(XF\Mvc\RouteMatch), Object(SV\PasswordTools\XF\Admin\Controller\Tools), NULL)
    #10 src\XF\Mvc\Dispatcher.php(121): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(SV\PasswordTools\XF\Admin\Controller\Tools), NULL)
    #11 src\XF\Mvc\Dispatcher.php(63): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
    #12 src\XF\App.php(2824): XF\Mvc\Dispatcher->run()
    #13 src\XF.php(806): XF\App->run()
    #14 admin.php(15): XF::runApp('XF\\Admin\\App')
    #15 {main}
    Request state
    array(4) {
      ["url"] => string(24) "/admin.php?tools/run-job"
      ["referrer"] => string(50) "https://<domain>/admin.php?tools/run-job"
      ["_GET"] => array(1) {
        ["tools/run-job"] => string(0) ""
      }
      ["_POST"] => array(3) {
        ["_xfRedirect"] => string(60) "https://<domain>/admin.php?tools/rebuild&success=1"
        ["_xfToken"] => string(8) "********"
        ["only_ids"] => string(6) "412482"
      }
    }
Then a simple feature request:
  1. With the event [Donate], give the user the option for a different destination currency, thereby automatically handling the transfer rate and preventing users from giving themselves the destination currency.

    We would love to have this option so people can more easily donate their Merit currency to other currencies like "Chemical knowledge", "Great source for information" and "Very welcoming", so those destination currencies you can only get by donations from other users.

    This way we can get a much better insight into who we could promote to certain user groups like "Chemical engineer", "Senior Member" and "Welcoming committee".
 
Last edited:
Love this addon!

We only use it to encourage more participation, and give users the ability to show appreciation for each other on our platform.

For the awesome developers, here are some issues we found implementing this addon since yesterday (these are definitely not deal-breakers, we just thought it would be useful for the developers):
  1. When you donate an amount, and have a negative tax, then the Alert shown around this event causes confusion.
    For example: Donating 1000 Merits with a -25% tax would be shown as the following (we like to encourage donating to others as a show of appreciation):
    View attachment 332231View attachment 332230
    IMHO it would be better if the Alert message in this case would state "You donated 1000 Merits to ..."

  2. Events for XF Resource Manager can cause an error during [DragonByte Credits: Rebuild transactions]
    (this was tested with [items to process per page] set to 500, 5000 and 50000, and [Delete all transactions...] to all different options, all made the same final error pop up)
    Code:
    Stack trace#0 src\addons\DBTech\Credits\EventTrigger\XFRM\RateHandler.php(105): XF::handlePhpError(2, '[E_WARNING] Att...', 'C:\\Websites\\for...', 105)
    #1 src\addons\DBTech\Credits\EventTrigger\AbstractHandler.php(887): DBTech\Credits\EventTrigger\XFRM\RateHandler->rebuild(Object(DBTech\Credits\XFRM\Entity\ResourceRating))
    #2 src\addons\DBTech\Credits\EventTrigger\AbstractHandler.php(834): DBTech\Credits\EventTrigger\AbstractHandler->rebuildEntities(Object(XF\Mvc\Entity\ArrayCollection))
    #3 src\addons\DBTech\Credits\Job\TransactionRebuild.php(84): DBTech\Credits\EventTrigger\AbstractHandler->rebuildRange(0, 5000)
    #4 src\XF\Job\Manager.php(275): DBTech\Credits\Job\TransactionRebuild->run(8)
    #5 src\XF\Job\Manager.php(205): XF\Job\Manager->runJobInternal(Array, 8)
    #6 src\XF\Job\Manager.php(121): XF\Job\Manager->runJobEntry(Array, 8)
    #7 src\XF\Admin\Controller\ToolsController.php(146): XF\Job\Manager->runByIds(Array, 8)
    #8 src\XF\Mvc\Dispatcher.php(362): XF\Admin\Controller\ToolsController->actionRunJob(Object(XF\Mvc\ParameterBag))
    #9 src\XF\Mvc\Dispatcher.php(264): XF\Mvc\Dispatcher->dispatchClass('XF:Tools', 'RunJob', Object(XF\Mvc\RouteMatch), Object(SV\PasswordTools\XF\Admin\Controller\Tools), NULL)
    #10 src\XF\Mvc\Dispatcher.php(121): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(SV\PasswordTools\XF\Admin\Controller\Tools), NULL)
    #11 src\XF\Mvc\Dispatcher.php(63): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
    #12 src\XF\App.php(2824): XF\Mvc\Dispatcher->run()
    #13 src\XF.php(806): XF\App->run()
    #14 admin.php(15): XF::runApp('XF\\Admin\\App')
    #15 {main}
    Request state
    array(4) {
      ["url"] => string(24) "/admin.php?tools/run-job"
      ["referrer"] => string(50) "https://<domain>/admin.php?tools/run-job"
      ["_GET"] => array(1) {
        ["tools/run-job"] => string(0) ""
      }
      ["_POST"] => array(3) {
        ["_xfRedirect"] => string(60) "https://<domain>/admin.php?tools/rebuild&success=1"
        ["_xfToken"] => string(8) "********"
        ["only_ids"] => string(6) "412482"
      }
    }
Then a simple feature request:
  1. With the event [Donate], give the user the option for a different destination currency, thereby automatically handling the transfer rate and preventing users from giving themselves the destination currency.

    We would love to have this option so people can more easily donate their Merit currency to other currencies like "Chemical knowledge", "Great source for information" and "Very welcoming", so those destination currencies you can only get by donations from other users.

    This way we can get a much better insight into who we could promote to certain user groups like "Chemical engineer", "Senior Member" and "Welcoming committee".
Hi there,

Can you please repost these 3 things @ my site in the appropriate sections (first two as bug reports and the third in the Suggestions sub-section)?

This site does not have any bug tracking possibilities so they will get lost in time by posting here.

Thanks!
 
Hi there,

Can you please repost these 3 things @ my site in the appropriate sections (first two as bug reports and the third in the Suggestions sub-section)?

This site does not have any bug tracking possibilities so they will get lost in time by posting here.

Thanks!
Thank you for picking this up!

And of course I'll report these things on your site, being a software solution architect myself I fully understand this optimized workflow. :).

I'll do that when I get home again from work today, it's quite the busy time with new year kicking off.
 
Am i really waiting 6 years for Resource Manager update so you could get resources for credits (not only charge per download) before i buy this add-on? lol
Guess its never gonna happen.
 
If you don't use the "Frequency" option for any of your events then it may be safe to do so. I would recommend backing the table up before doing anything with it.
I want to clarify one thing about xf_dbtech_credits_transaction.

You mentioned that it may be safe to empty this table if the Frequency option is not used for any events.

In my setup, I use DragonByte Credits 5.0.3 together with DragonByte Shop 6.0.4.
I checked my event settings, and Frequency is set to 1 everywhere (as far as I understand, this is the default value).

So my question is: if Frequency = 1 on all events, does that mean the Frequency feature is effectively not being used, and would it then be safe to:
  • purge old rows from xf_dbtech_credits_transaction by date, or
  • fully clear this table after making a backup?
I only want to reduce the size of the transaction log table, not affect user balances or event logic.
 
question is: if Frequency = 1 on all events, does that mean the Frequency feature is effectively not being used, and would it then be safe to:
  • purge old rows from xf_dbtech_credits_transaction by date, or
  • fully clear this table
Yes, if Frequency is 1 and all the other values in the advanced options are left at default, it is safe to purge old rows as the only purpose then is to display the history.
 
DragonByte Tech updated [DBTech] DragonByte Credits with a new update entry:

7.0.0 Beta 1

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...

Read the rest of this update entry...
 
Are you referring to the Suggestion thread type? I don't believe a specific integration for that has been implemented yet.
For the question thread type. When a user upvotes or downvotes, there should be a credit. Is this option available in the new update so i can upgrade?
 
DragonByte Tech updated [DBTech] DragonByte Credits with a new update entry:

7.0.0 Beta 2

Update highlights​

This version contains a couple of fixes discovered during Beta 1, including a regression from v6 that would prevent events like Daily Activity etc from executing.


Complete Change Log​

Fix: Fix an issue where certain events would never be executed (regression from v6)
Fix: Work around an issue where the step buttons in number boxes would use scientific notation

Read the rest of this update entry...
 
DragonByte Tech updated [DBTech] DragonByte Credits with a new update entry:

7.0.0 Gold

Update highlights​

As there have not been any significant breaking issues discovered during beta, v7 is now Gold 🎉

This version fixes an issue with certain background events such as Daily Activity, as well as fixing an issue with number input boxes.


Complete Change Log​

Fix: Fix an issue where certain events would never be executed (regression from v6)
Fix: Work around an issue where the step buttons in number boxes would use...

Read the rest of this update entry...
 
DragonByte Tech updated [DBTech] DragonByte Credits with a new update entry:

7.0.1

Update highlights​

This version fixes a regression where the credits cron job would get stuck - and even blocking other cron jobs - if the "Daily activity" event was enabled. This has also been hotfixed in v7.0.0, so if you are affected you can re-download the existing version if you don't want to upgrade.

Another regression from v6 has been identified with XFRM uploads, and this has also been corrected.


Complete Change Log​

Fix: Remove debug...

Read the rest of this update entry...
 
DragonByte Tech updated [DBTech] DragonByte Credits with a new update entry:

7.1.0 Beta 1

Update highlights​

This version adds two major new integrations; [XA] AMS - Article Management System and [NF] Calendar!

For the AMS, the following events are available:
  • Article
  • Article Comment
  • Article Commented

For Calendar:
* Event Occurrence (only works with non-recurring events!)

The event occurrence lets you award credits to people who RSVP'd to a given event. You can choose which RSVP status is included.

Furthermore, a...

Read the rest of this update entry...
 
DragonByte Tech updated [DBTech] DragonByte Credits with a new update entry:

7.1.0 Beta 2

Update highlights​

This version makes improvements to the [NF] Calendar integration by adding a link to the event in question for the transaction log entry, as well as fixing a server error on the transaction log on pages where such entries were shown.

Furthermore, a few internal changes were made to better support 3rd party add-ons integrating with Credits.


Complete Change Log​

Feature: Add link to the [NF] Calendar event in the transaction...

Read the rest of this update entry...
 
DragonByte Tech updated [DBTech] DragonByte Credits with a new update entry:

7.1.0 Beta 3

Update highlights​

This version brings a few very important changes to transactions.

First of all, using Credits as a payment profile in eCommerce will now pay out the currency spent to the product owner (or the business profile owner, for Classifieds orders), via a new "Paid" event. This event allows you to tax the incoming amount as well.

The second, and arguably the most important, change is that currency amounts spent on events that are moderated will now be...

Read the rest of this update entry...
 
Back
Top Bottom