Darkwaltz4
Former Developer
I am rewriting a key part of the core, because here is whats happening:
vBCredits used to keep track of exactly how many credits you had as it went through producing a page. The problem was, it did it all selfishly, and any addons that changed the currency amounts on the database might be overwriting the direct database editing of integrated addons (like say, buying something in vbshop).
My current solution to that was to keep a backup value of your currency on the userinfo, and when it comes time to save to the database, it saves the difference vs the direct amount, to preserve any changes to the database that happened by something else.
What this bug report has uncovered though, is that vb sometimes has multiple copies of the userinfo flying around, and will swap them in and out of play in between vbcredits' attempts to update. The result? Now my own updates are getting lost So vbcredits trips up and is doing extra math trying to compensate behind the scenes, but as you can see, it isnt adding up and isnt recording to the transaction log about it.
So, this is taking forever, because this was a complicated and central part of the core. The good news though, is that you are forcing me to actually get to the bottom of a session issue whereupon i never really liked or trusted the bandaid that i originally came up with to fix it
**the post preview thing is a minor, unrelated issue that i will address separately after this
Thank you as usual, for your patience.
vBCredits used to keep track of exactly how many credits you had as it went through producing a page. The problem was, it did it all selfishly, and any addons that changed the currency amounts on the database might be overwriting the direct database editing of integrated addons (like say, buying something in vbshop).
My current solution to that was to keep a backup value of your currency on the userinfo, and when it comes time to save to the database, it saves the difference vs the direct amount, to preserve any changes to the database that happened by something else.
What this bug report has uncovered though, is that vb sometimes has multiple copies of the userinfo flying around, and will swap them in and out of play in between vbcredits' attempts to update. The result? Now my own updates are getting lost So vbcredits trips up and is doing extra math trying to compensate behind the scenes, but as you can see, it isnt adding up and isnt recording to the transaction log about it.
So, this is taking forever, because this was a complicated and central part of the core. The good news though, is that you are forcing me to actually get to the bottom of a session issue whereupon i never really liked or trusted the bandaid that i originally came up with to fix it
**the post preview thing is a minor, unrelated issue that i will address separately after this
Thank you as usual, for your patience.