But first of all, let me apologize for any offenses, I just pointed out two possible explanations for what this add-on is and what its features are, I don't believe I offended anyone but if I did, I'm sorry.
You don't believe that accusing someone of malicious business practices is offensive?
I still don't agree with the fact, being aware of the presence of bugs you still let people buy a 3-months long license (and it's my bad, I forgot I luckily purchased the yearly and not the 3 months license, but I'm sure any other people who'd make the mistake of getting a 3 months license for such add-on would complain sooner or later, so rather than a personal complaint, take it as a potential issue you might have with your customers);
I was not aware of the presence of this bug. I had forgotten about your post, because I was busy upgrading DBTech to XF2.
If you forget something, you're no longer aware of it. Kind of like how you forgot you had purchased a 1 Year license and not a 3 Month license.
As you yourself say; if you're made aware of something once, months ago, you are aware of it forever as you cannot possibly forget anything. Therefore, you were aware that you had purchased a 1 Year license, and you purposefully misrepresented this in your post in order to garner sympathy.
Your logic works both ways
I found it to be hilarious that in order to fix a bug we need all this chaos on here, where it seems it took you probably less than 1 hour to fix it, making me and other people wait months before having this bug fixed;
For the record, by the way, this wasn't actually a bug, something I discovered too late to cancel the release. Cancelable events have these options:
- Exclude amounts
- Exclude entire event
- Prevent the event trigger
If "Prevent the event trigger" is selected, the "not enough points" message comes up. If either of the other two are selected, it does not.
That being said, to prevent misconfiguration, it's probably best to remove the ability to cancel Warning events.
In other words, this was not a bug, this was a misconfiguration on your end.
I could make a very long bug-list for your add-on
Please do, but do try to make the list contain actual bugs in advertised features, not "I think it should work like
this so I'm going to call it a bug"
clicking on the add-on from the left menu in the admin panel you reach a blank page
How is this a bug? What functionality has been advertised on those pages that is now not working?
the impossibility of having the Donate event to trigger only for some groups as you get the error "Sorry, this action is unavailable because a matching Event record was not found. " forcing people to hardcode their templates in order to show the donate tab only to the usergroups you want it to be shown (exposing the site to potential exploits).
This is completely nonsensical. Editing your templates do not expose your site to any potential exploits, that makes absolutely no sense.
Also, this is not a bug. You can feel free to post a feature request @ our site to get a new user group permission for who can see the Donate tab, and it will be looked at for future updates. Unfortunately feature requests from this thread cannot be tracked, because these threads do not contain issue tracking software that allows me to see outstanding feature requests.
Extending my license, altough it would have been a kind gesture from you (I still thank you for your initiative), wouldn't have solved the root problem, and I'm also sure you wouldn't have extended all the other users' licenses as well.
Given that this issue was, in fact, highlighted before today, I would be more than happy to extend the license of customers who would have been eligible to download an update back in April but would no longer be eligible today.
If any such customers are reading this post, please feel free to send me a PM with your DBTech username so that I can investigate.
From my point of view (and many of my friends share the same PoV of me), add-on upgrades should be primarily meant to be done when new features are introduced or when you make minor bug fixes, and not for important/core bug fixes, which shouldn't even exist when dealing with a *production* script, meant to be used on live sites and not for local servers;
So you still believe that it's possible to create a script without bugs. I don't even need to respond to this any further, as anyone with any amount of experience with software development will tell you this is 100% unreasonable. If you keep harping on the point that our software should be bug free, your posts are going to be dismissed as nonsense by everyone reading them.
I'm not, of course, your business consultant nor anything important for you and your projects, I'm just trying to point out some of the problems I personally experienced using your add-on
Did you know that it is actually possible to make addon developers aware of problems (or remind them of previously reported problems) in their add-ons without accusing them of deliberately leaving flaws in the software so that they can charge more for renewals? I know, I was surprised to learn that too.
I'm sorry if I'm bothering you with my messages, and I'm sure I am, but I feel the need to share my experience with this script, as people should be able to read both the good and the bad about anything, especially on internet, before making their decision. Then it's up to them to decide what to believe.
Sure, but it would have been nice to not have you accuse me of malice. Then again, considering your track record with the truth in this thread, I'm not holding my breath about you realising this.
---
I am truly sorry that I forgot about your bug report so that I couldn't either advise you to correct your misconfiguration or make the change I made today in a more timely manner.
Fillip