Quote:
Originally Posted by takao
I'm getting increasingly frustrated because it appears that rather than looking into this problem, the bug is being passed onto users as though it's our fault when we've (at least, I've) done everything asked *and gone above and beyond* to try to fix it.
|
It takes more energy for me to reply to you here multiple times than it does for me to update a bug report or talk with one of the devs once. It also takes Matt more effort to reply to you twice than to fix any bug here himself.
So we gain nothing by 'passing this on' to you.
Put simply, we fixed this in the release version. So it should work.
Of course, it's always possible a fix did not take.
But what's much more likely is that data did not update properly on the user's (your) end for multiple reasons, out of your and our control. So we'll give you advice based on the probabilities of what is the most likely source of the issue.
If you cannot get things working correctly even after applying the most likely solutions though, then you simply need to tell us that, and then we will look at things on our end again.