I'm not suggesting you blindly copy my other fixes as I realize they're tailored for me and my use cases specifically. I drastically changed several of the functions that would likely not work within your model. I was only curious about the one that breaks the form that allows you to save your chosen trophies. It's the same link to invoke and save changes to that page.We can make a big discussion out of this if you want, but the tl;dr is that we don't blindly copy-paste suggested bug fixes but rather check the software and code if that is actually fixing the issue and not just bandaging it on the surface, so no errors follow up, similar issues may also be tackled in the same run, it doesn't produce any edge cases and works in all setups, etc. It's a simple matter of quality assurance, and, as previously stated, not holding back one bug fix while we work on the other.
I'm fully accepting that I have not created an add-on for XF so it's likely not as simple as "hey go update your template", but that's why I asked the question. What is it that creating an add-on does that's different than just importing a template, respective to the template error specifically?
Lastly, I know for your paid add-ons it makes sense to not have the source code published but how come you guys don't have this add-on public in github? You're already using it for issue tracking. I would have issued a merge request instead of just pasting it here if I had access to do so.
I want to be clear that I was not attacking you, I just want to understand because from the outside it seems like a simple fix to alleviate a broken feature. You're not obligated to give me the time of day and I appreciate your activity in this thread. Often times developers for companies do not have a direct line to their customers. What seems obvious to us is maybe not obvious to your internal models. I'm sympathetic to that, working in both development and security infrastructure fields in my professional life.