Forum Replies Created
-
Posts
-
Hey there Jason. Thanks for this reply; Kelly brought the thread to my attention and I wanted to get you a follow-up.
While we really appreciate you providing some feedback, it seems like this reply is for an issue totally unrelated to the original one Kelly was attempting to help with. While we are always working to optimize the performance of the plugin (and it indeed gets better with each release), it does sound like based on your last reply, you may have broader issues here.
To that end, and more importantly: this response doesn’t meet our community guidelines and unfortunately we’ve decided that your tone is ultimately no longer welcome on the forums. We’ve refunded your purchase price for both plugins you bought, and I’ve emailed you privately with more information as to our rationale. That said, your account here on the tri.be site has been terminated and this thread is being closed down.
Thank you.
Hi Max! Thanks for the follow-up. I’m sorry that I’ve failed to properly communicate our limitations here in my previous note…to that end, it’s also a shame that you’re making assertions that I’d argue aren’t quite fair.
Ultimately: this issue has nothing to do with you being an international user; the Eventbrite Tickets plugin, indeed, works for any country. But what you’re attempting to do is ultimately trying to use the product in a way that is unsupported and is known not to work.
We’ve offered to give you a refund if the current behavior doesn’t meet your needs. I consider this more than fair, as unless I’m misunderstood, we don’t make any claims on our product page that the plugin is meant to behave the way you’re asking. But we cannot support something that goes against how the plugin is designed in the first place.
Please let me know if I’m misunderstood or if you’d like to take us up on that refund. Otherwise I’ll plan on closing this thread at the week’s end if we haven’t heard from you.
Hey maxhenry. Did you end up figuring this out or finding another solution? I’m not sure we’re going to be able to do much else to advise here, based on my last follow-up…
Hey there: it shouldn’t cause a problem, no…basically WooTickets is piggybacking on WooCommerce’s functionality here, so much of the code is handled on their end to begin with.
That said: if you find issues persist in your future testing, definitely open a new thread and we’ll do our best to get you sorted here. Thanks!
Hey there elmalak. Thanks for your post here…Casey and I were just reviewing this and I wanted to see if I could try and help get things sorted here. Unless I’m misunderstood, this sounds to us like it is a conflict specifically with whatever third party plugin you’re using to add the additional button the visual editor.
While Casey has tried to point you in the right direction here best we could, I’m not sure it’d be appropriate to get our developers involved to fix a conflict with this third-party plugin just yet. Would you mind linking us to the dot-org page for that plugin, so we can check it out and see if we’ve got any other threads related to similar conflicts?
That’s about as much as I can offer up at the moment. I’m sorry we can’t do more and I hope you understand where we’re coming from regarding how deep we can or cannot go. If we’re misunderstood as to the source of the problem here, please let us know.
Hey MaxHenry. I’m sorry for your experience so far. While I really wish we could help you out more here, ultimately it does appear – as Kelly tried to explain in her last follow-up – there are limitations to how much we’re going to be able to provide. What you’re requesting is not a bug, but a feature change that impacts overall architecture of the plugin. While I wish we could implement new features/architecture changes whenever they arise (and in a world where time + resources abounded, we would), there are a couple realities we can’t ignore here:
1) Feature tweaks like this can’t be made at the drop of a hat.
2) If we are going to implement architectural changes, we want to make sure a good chunk of the community sees value in it. This is where our UserVoice page comes into play…the most requested features there are what help drive our future product roadmap.While I’d argue that the exchange clearly shows that Kelly has indeed made an attempt to help; I can see your frustration that her attempts to explain the issue fall short of providing a “fix.” But as I noted above, that’s unfortunately the most we can offer up as there isn’t really a quick solution we can provide you.
All that to say: how would you like to proceed? I’m getting the sense this relationship might not work out due to the fact that you still seem a bit displeased. Make no mistake that our messaging is aligned and we have a clear gameplan/system for how we provide support here 🙂 I can understand that you might not be feeling like you’re getting the value you’ve paid for, though, which is why I’m thinking it might make sense for us to provide you a refund. This would allow you to take your funds and put them towards a product that better meets your needs and has support more in line with your expectations.
Hey Max! Kelly passed your note my way, and I wanted to reach out to see if I could try and help get things back on track. The fact that we’ve failed to meet your expectations is a definite bummer, and – above all – tells me that we failed to set those expectations properly early on. While I’m a bit confused to see you make a comment calling the support “so weak” when I don’t see a single other thread you’ve been involved in besides this one, it’s obvious we’ve not served you right here and I apologize for that.
That said, it sounds like the issue here is simply the inability to save tickets being created from within the WP backend. This sounds like it’s something specific to your install (I’m guessing a conflict of some kind) or browser (if you’re using an older version of IE, this could be the cause as well).
We definitely realize that the more international-friendly the plugin is, the better it will be for everyone in the community. So we are invested in getting this sorted if it is indeed a problem with our codebase.
Kelly will continue to attempt troubleshooting this. Is there anything else we could to help make things right for you?
Hi again Cat. Sorry that this had to wait until our deployment yesterday to get accomplished; I realize that was a couple days beyond what was promised and I failed to adequately communicate as much to you.
The docs page was regenerated to include all the latest yesterday, though, and should get you what you need: http://docs.tri.be/Easy-Digital-Downloads-Tickets/. Let me know if I’m wrong or if we can do anything else. Thanks again for your patience so far.
Catrose937: perfect…thanks so much for the follow-up here. This is an oversight on our end! We need to regenerate that docs site again since it appears to not have taken properly when we initially launched. I’ve got the team on this and we should have something up Monday. I’ll comment in here when we do.
In the interim, have you checked whether the inline documentation in the plugin itself helps? you out?
Hey there catrose937. Chris is out today, but I wanted to follow-up here to confirm that he’ll be able to check and see if he has any advice/tips when he’s back (no guarantees though, but we’ll try to do our best).
That said: what was the link you were trying to access for the primer? If it’s 404ing I want to make sure to get that sorted. Thanks in advance!
Hey Robert! Chris is out today, but I wanted to follow-up here to confirm that we’ve identified the issue here and have got it patched for our forthcoming build of EDD Tickets. Expect it to be fixed when you upgrade to the next EDD build (should be released very soon).
Thanks for your patience / support here, and let us know if you need anything else in the interim.
Hey again jfeisabel. Thanks for the follow-up here, and apologies for the delayed reply on my end — you posted just as I’d headed out for the Thanksgiving weekend.
Why don’t you shoot me an email, rob @ tri.be, and I’ll see if I can troubleshoot this for you? I can’t guarantee anything and would need both a set of backend/admin credentials and your written approval that you don’t mind me jumping in and attempting some test imports…but that may allow me to troubleshoot this issue. Thanks again for your patience.
Hey folks. Thanks for the follow-ups here, and to Nenad, I apologize to hear that you’re feeling disappointed with our level of service.
When it comes to planning ahead: we certainly are trying to 🙂 WPML integration is high on our list of features to work towards. But realistically at the moment, we’re focused on stabilizing the codebase (by ridding it of bugs); getting the most widely requested features integrated; and finishing off some of the new plugins we’ve had on the roadmap for 2014.
While we understand there are a ton of folks using WPML, the main issue here is that the changes are ultimately too broad to integrate in one quick swoop. We’re gradually working towards that but ultimately need to have the infrastructure in place before we can begin attempting to integrate/support third-party plugins.
Based on your deadline, I will say – unfortunately, but with certainty – that WPML integration won’t be ready by the time you renew. If I had to guess I’d wager it’s still at least a few months out. If that doesn’t work for you I sincerely wish you the best of luck in finding a solution that better serves your needs.
