404 for new events

Hey there morespinach. Thanks for the follow-up here, and for providing links to the threads at WordPress.org that also convey your concern here. I can totally understand your frustration and the fact that you’re feeling increasingly out of options here. Right off the bat I will say that if you’re interested in pursuing a refund so you can move onto another solution that better meets your needs, that offer is on the table no-questions-asked. Just shoot an email to pro (@) tri.be with a link to this thread and we’ll get a full refund processed for you from there.

It’s clear we failed you on a number of points here, too. The fact that it wasn’t clear what we do and don’t support on WordPress.org, along with how often we hit the forums there, was one of those. Our policy is that we review WordPress.org once a week and in doing so provide a quick pass reviewing issues purely for bugs. If bugs are reported, we attempt to recreate them in as stripped down a stock environment as possible. If we can’t, then we generally move on.

Which leads us to point 2 in terms of our failure: I get the sense after reviewing those threads that we mistakenly wrote this off as a caching issue…when I’m not fully convinced it is. (My guess is that Brook was unable to recreate, our general baseline for checking/logging/following up on bugs.). But I’m also of the mindset that we may have done so too hastily here – it just doesn’t seem like a coincidence that there would be so many voices reporting this issue, unless something was up. As to why we’re consistently unable to recreate it…that I cannot say. But to me it’s worth having the team take another look at this and attempt to get a definitive answer one way or another.

All that to say: we appreciate your patience so far. While I do ask that we all make an effort to keep a professional and polite tone – in the same way I wouldn’t walk into a customer’s office and start yelling at them, I ask that our customers keep a cool and collected demeanor here on the forums – I can also totally understand why you’re frustrated and want to do right by you. While I will caution that I can’t guarantee we’ll be able to get this issue sorted for you – if it turns out there is a conflict of some kind, for example), know that – if this is legitimately a bug in the plugin codebase – we are committed to patching it for you.

Since Barry is out the rest of the week, I’ve asked another colleague to review the context of those other threads and follow-up from here to try and keep this moving for you. If you do have an admin account you would be willing to set up and send over privately so we could attempt to troubleshoot for you (and you do so with the understanding that you’re going to want to backup before we go in there, since we can’t be held accountable for any problems perceived to have been caused by our exploration)…that’d be awesome.

But like I said: if you are just ready to move on and would like the refund, that’s fine too. Either way I want to do right by you…so just let me know your preferred course of action and we’ll take it from there. Thanks again for your feedback and for helping us get better. If you have feedback or other thoughts that you’d like to relay to me privately, know that I’m always available directly at rob (@) tri.be.

morespinach,
We’re definitely sorry that you weren’t able to resolve the problem, but as @rob stated above, just email us at pro(at)tri.be with a link to this thread and we’ll get your refund processed ASAP. In the mean time, I’ll go ahead and close out this thread.

Thanks! 🙂

-Casey-