I did not know there was an outstanding bug. You can choose whether or not to believe me on that, but I recently went through all my add-ons and marked all those add-ons with outstanding bugs as "Unmaintained" until those bugs were fixed. This add-on was NOT marked with the prefix, so you should assume that I did not consider that there were any outstanding bugs.
When the report was made at the end of February by a customer of XenForo, my assumption was that they must have uninstalled an old version of XenForo. I was wrong not to investigate this, and I apologise for this.
When this issue was raised again yesterday by a customer of Waindigo, I realised that I made a mistake in not properly investigating the report at the end of February, found that there was a bug (that may have come into the add-on at a later date since the last related bug fix was released). I immediately released a bug fix and issued instructions as to how to restore Resource Manager.
I believe it is the responsibility of owners of forums to make sure that their sites are properly backed up. That it took
@Sunka 34 days to recover lost data shows how irresponsible it was not to back up that data and I do hope lessons have been learned. That being said, I am incredibly sorry that my oversight has caused so much trouble for some people and I do hope that my delay in responding over the last few weeks hasn't caused any more problems.
Now to the issue of my slow response in the past to this issue, I don't believe there is any reasonable excuse for this. An issue which was reported in August was not even acknowledged until a fix was released at the beginning of November. I did have an employee working with me at the time, but I am responsible for his actions (or inaction). I did also have a wedding to plan at the time, and I see that the bug release was made on 10th November, just 9 days after my wedding and only a couple of days after returning from honeymoon. I don't remember my thoughts at the time, but this suggests that by November I had recognised how important it was to resolve this issue. I'm very sorry that this wasn't acknowledged sooner.