@Andrew - That is great, but there is "understanding" an issue and "communicating" about it- they are two different things. That is why people on the forums often talk about Boonex staff doin "drive by postings" - they will say something about an issue, leave it unresolved, and not return for weeks or sometimes months. Perhaps they are still working on it, but we have no way of knowing that - we aren't mind readers.

With the particular issues I was trying to see more get addressed, my last communication with Alex was when he incorrectly said it was fixed after trying it with a guest account on my system. I pointed out that this was not correct and showed him why, but got no answer to that or a few other messages. I then contacted my agent Mike who was responsive, but he said two different developers there wouldn't tell him any thing about it either. After that I just tried to get the ticket to correctly show that this was not "fixed" - posting it on your new disputes board - but again no communication. With your staff saying it was fixed, and the ticket falsely saying it was fixed - how could I assume anything other than you either weren't listening or didn't get it?

So that is fantastic if you are really listening more than it seems, and especially if you are incorporating some of the wonderful fixes and enhancements that have been done by the community, but the "hard evidence" we have didn't give any reason to know that.

On the particular but that has concerned me, one of the other members here has contacted me about this issue and already seems to have some ideas of how it can be fixed so hopefully he will be able to figure this out and help your staff out. Like everyone, I look forward to the release of the new version.