Forum Replies Created
-
Posts
-
Hey Paul: awesome to hear your devs were able to customize the plugin to your liking! This is usually the route we request users go when they want to modify the core behaviors of the plugin in a customization-minded fashion, and I’m glad to hear your dev was able to build out these additional components you wanted.
As for “lighten up”…I’d like to think I’m plenty light already 🙂 I am a tad disappointed that you still continue to view these feature requests as bugs/lacks of implementation – when we’ve spent a whole lot of time that could have been better spent helping other customers trying to explain in great detail as to why these things are absolutely feature requests. Valid feature requests, to be sure, but feature requests nonetheless. If your developer has a solution that addresses one of these feature requests and they would like to post that on our UserVoice page, we would be happy to review it and consider implementing something along those lines (with appropriate credit to you, of course!) if it passes code review in a subsequent release. But UserVoice, rather than the forums, is the appropriate venue for these suggestions.
I just want to reiterate that we do have guidelines/standards here on the forum. While I’m sorry you view this as “bullying buyers,” it certainly isn’t intended as such: it’s setting expectations regarding what is and what isn’t allowed here at the forums. While in the past I might have sugarcoated it a bit, frankly we’re reaching a point where continually repeating how we define feature requests vs bug reports for you isn’t getting us anywhere. And when I view this thread and a few of the ones you’ve posted previously, they do come across as fairly hostile and verging on disrespectful…enough that members of the team have brought your threads to me and asked I get involved directly.
Paul, I hate to pull this card, but ultimately: this is our house….you’re a guest in it. Still a welcome guest, at the time being, but a guest nonetheless. If you aren’t going to abide by our rules going forward we’re going to be forced to send you on your way. I hope this makes sense and that we’ll see some forthcoming UserVoice reports from you!
Hey Lars: thanks for the elaboration, and my apologies for the misunderstanding. Sadly I’m not seeing that on my local environment either. The filter panel needs to be expanded – it is collapsed by default – and when it does it takes up the entire window until selections are made.
Regarding those two sites you provided here: I found that the EssexMums URL didn’t actually allow me to see the filters at all. Whenever I hit the button to Show Filters nothing expanded and the page didn’t react. On your site that you sent over via private message it doesn’t look like Filter Bar is still active at all?
Hey Paul: hope you’re well. Barry brought this thread to my attention and I wanted to chime in. I recall an email exchange a few months back where I think we were pretty clear about resetting your expectations and attitude here on the forums. Comments like “maybe you should pay my developer to fix your plugins” really serve no one, and add no value to the discussion. Frankly, they just take time to reply to that could be better spent helping users who are struggling with legitimate problems. Both of the items you mentioned here – recurrence in WooCommerce Tickets, and the inclusion of additional attendee data on the backend attendee list – are feature requests, not bugs or missing functionality, and it is misleading to suggest otherwise.
It doesn’t look like you actually need help in this thread, so we’re going to close it unless we’re misunderstood there. Thanks for your understanding and please do feel free to shoot me an email if you feel differently.
Hey Lars. I have spent some time over the past couple days checking this out, and I tested on a couple of the standard themes we use for testing (Twenty Thirteen and Twenty Fourteen) on my local test site. It looks like the button you’re referencing is handled fairly gracefully across the board:
* Twenty Thirteen, landscape: https://cloudup.com/cOZbnjs8vch
* Twenty Thirteen, portrait: https://cloudup.com/c8mZcRcCo4r
* Twenty Fourteen, landscape: https://cloudup.com/cFjD2ONedip
* Twenty Fourteen, portrait: https://cloudup.com/c6stywu2fDxAs you can see there, this is looking pretty good across the board – which makes me think there’s something regarding the theme’s responsive layout that is perhaps not quite in line with the core WordPress themes’ standards of doing things. Have you raised this concern with the theme dev as well? The fact that it looks good in both the most recent WP themes should be useful in helping them see that their theme is registering something differently. (If they have feedback on how we could update the plugin in a way that integrates with their theme better while staying in line with WordPress standards, we are totally open to it).
Hope that helps and sorry I couldn’t offer more in the short-term. Please let me know if you have other questions or thoughts on this.
Hey Kevin. Just a heads up that Kelly has left the team for at least the next few months, so I’m happy to take this over for you. It sounds like you’re sorted at this point…correct? Let me know if not or if we can do anything else for you in this thread.
Totally; if you have a localhost environment, you can install and test the plugin locally. Do you already have a license? If so, you can download it from going to Account Central -> Downloads here on the tri.be site and can select 3.5 from the dropdown there.
Hey alexhammerstein. Thanks for the follow-up here. You make some great points, and I appreciate you summarizing these issues.
As I mentioned in my last note there is definitely a hotfix coming very soon (sometime today) which should address #1, 4 and 5 from your list. #s 2 and 3 are new to me and not something we’re seeing widespread reports of, so I would wager that those are related somehow to your specific environment. While I see you say that you find it hard to believe these are related to configurations, the fact is that if these really were problems impacting everyone we’d have both caught those in our pre-launch QA and would have seen a flood of reports on them since launch. If you’re willing to post them as separate threads we’ll do our best to get you sorted — and get those logged as bug tickets if we can confirm they’re legitimate problems in the codebase.
Thanks in advance!
Hey folks, thanks for your feedback and comments here. We appreciate the feedback and apologize that some of you have encountered difficulties with the new codebase. We’re here to help as best we can.
That said, it is sort of concerning to see these remarks…we’ve had thousands of users apply the update to 3.5 so far without any significant issues, so if I were a betting man I’d wager there was something on your specific environments that is causing conflicts. Not to say it isn’t something we can help with; but I caution against dramatic blanket statements that don’t factor in realities of the upgrade and plugin development process. Comments about “releasing updates before they are ready”, for example, are ignoring the fact that we spent literally dozens of hours QAing this release before it shipped. Sadly there is no way to catch everything…particularly fringe situations that impact only some users. We release knowing the community will report certain issues to us that arise in use cases we don’t test for, and we’ll patch those as quickly as possible.
The admin panel issue, as Casey alluded to, is something that is impacting a small percentage of users and we’re looking to apply a hotfix for now (as you can see by this thread, the solution has already worked for one user: https://theeventscalendar.com/support/forums/topic/3-5-freezes-out-admin-area/#post-126782). If there are other items that exist on your radar please pose those as separate threads, with specific steps to recreate, and we’ll do our best to get those sorted. Comments like this which skew the broader community’s perception – after all, many users have had no problems with this new build – aren’t particularly productive for anyone.
Thanks, and please don’t hesitate to reach out to me directly ([email protected]) if you have further feedback or questions here.
Hey Lars! It looks like Casey attempted to point you in the general direction for you to display the organizer name in the tooltips, but you haven’t yet tested these suggestions? Or are we misunderstanding and your question is that you can’t find out how to do this via the dev docs resource Casey linked to.
Sounds like this is ultimately a customization, after chatting with Casey – are you saying that the answer provided here (https://tri.be/support/forums/topic/add-orgaziner-to-calendar-detail-overlay/#post-123480) didn’t help point you in the right direction? What about that code is giving you problems?
Hey Cloud Genius! Kelly’s no longer with us for the time being, so I’ve taken on this thread. Do you just want to test in a “staging” environment? Somewhere other than your own test site?
OK Lars, thanks. I’m going to ask a colleague of mine with a more technical mind to take a look and attempt to help you troubleshoot here. Thanks for your patience!
Hi Stephen! Thanks for the note here, and for your patience in waiting as we work through the queue to get you a reply. We do have a number of users running our plugin who are also using WooThemes’ Canvas — in fact we’ve been working with Woo on a handful of plugin/theme conflicts recently and have taken a few steps with them to specifically/officially integrate the two codebases. It looks like specifically in our 3.1 release we added code to better integrate the two.
That said, I have seen reports of users facing conflicts since then. While it looks like in most cases they were able to work through their issues with our support staff, I will caution that it does seem our plugin won’t integrate 100% “out of the box” with Canvas at this time.
Hope that helps and sorry I couldn’t offer more. If you have other questions do let us know!
Hey Judy, as Brook noted in his reply to your other thread, we recognize this as a bug and are working to patch it. Thanks for your patience!
Hey Lars. Just wanted to give you a heads up: I’m seeing that locally on my iPhone too. We are shipping some new responsive layouts for the calendar that I’m hoping will carry over into Filter Bar nicely and ensure it integrates relatively smoothly in mobile situations like that. Can you let me know if these persist after you update to 3.5 next week, and we can try to get it sorted if there are problems from there? Thanks!
Hey esteban! Hope you’re doing well. Just wanted to give you a heads up that we’ve received this, but pretty much all of the support team is out today besides me. I’m jumping in to let you know that I have prioritized this for the team when everyone is back Monday, and we’ll get you a response ASAP at that time.
My apologies for the delay, and thanks for your patience in the interim. We’ll do our best to point you in the right direction here next week!
