Forum Replies Created
-
Posts
-
Hey tony, thanks for the note and for checking out our plugin. Happy to answer these questions for you:
On the issue of reminders, assuming you’re speaking about The Events Calendar PRO: the plugin doesn’t actually have a built-in reminder functionality at the moment. That’s a neat idea and something we may implement down the road but we have no plans for it on the immediate roadmap.
When it comes to setting up recurrence patterns: “First Monday of every month” and similar patterns are definitely possible. “Every other Sunday” isn’t, in that wording, but you could probably accomplish the same end goal using our custom recurrence patterns. Have you checked out this post providing a detailed look at recurring events (https://theeventscalendar.com/pro-2-0-a-detailed-look-at-custom-recurrence/)? It may also add some value.
Hope that helps. Let me know if it doesn’t, or if you have other questions,
Hey guys, thanks for your posts and for your interest in the plugin. There isn’t any built-in color coding, though you could certainly modify the CSS as you saw fit. However a user who is active here on the forums created a solid, free add-on that sounds like it would accomplish your goals nicely: http://wordpress.org/plugins/the-events-calendar-category-colors/.
Hope that helps and let me know if you have any other questions here.
Hey roosites. Thanks for the post here. I will definitely leave this open so other users can comment as to what works best for them, but from an official capacity know that this is still on our radar as something a lot of users want to see implemented! We are keeping an eye open for effective ways to implement this as we realize a lot of users would benefit from it. Best of luck finding a solution and my apologies we couldn’t offer more at the moment.
Hey there sanver…thanks for your post. Sounds like if I understand your goal correctly, it can be accomplished with the setting that appears under Events –> Settings on the backend of your site: “Include events in main blog loop”.
That should get you where you need to be, but please let me know if I misunderstood your request. Thanks!Hi Gina. Thanks for the follow-up here, and my apologies for the delay in getting you a reply here…I’ve been out of the office until earlier this week, but wanted to follow-up since it seems like you’re definitely unhappy with our service.
I can tell by reviewing this thread that Julie did her best to help you out here – and while it’s a shame our documentation wasn’t enough to get you sorted (we’re doing our best to restructure that in a way that makes more sense for users), I will say that you might run into some problems trying the solution you mentioned here: modifying files directly in the /resources/ folder will cause your change to be overwritten next time you update the plugin (unless you’ve properly enqueued the new one and dequeued the old one). You would instead want to follow the procedure of a template override, which we’ve detailed in the themer docs. We also have a tag cloud for (which brings in a ton of relevant threads that cover the template override process) from the sidebar on this page.
My apologies that we failed to live up to your support expectations. Please do let us know if we can do more to help you and hopefully improve your experience down the road. If you have any further feedback you’d like to share or want to continue this discussion, don’t hesitate to email me (rob @ tri.be).
Hi guys – Rob here. Just wanted to check in with you: Kelly is unfortunately out this week due to an unexpected situation, so I figured I’d personally step in here to apologize for the fact that this one has slipped through the cracks. I’ve reassigned this ticket to my more technical colleague Brook, who will get you a reply here within 24-hours max.
Thanks for your patience and our apologies for the delay here.
Hi Thomas – Rob here. Just wanted to check in with you: Kelly is unfortunately out this week due to an unexpected situation, so I figured I’d personally step in here to get you an update and to confirm that this sounds like an issue we’ve been working on regarding microformat implementation. That said, I’ve passed it on to my more technical colleague Barry, who will get you a reply here within 24-hours max.
Thanks for your patience and our apologies for the delay here. Please let me know if you need anything else from me.
Hey perthmorrismen! Kelly is out this week due to an unexpected emergency, unfortunately, but I just wanted to follow-up based on your last reply to confirm whether you needed anything else from us here? Let me know what we can do to help better get you sorted.
Hey Schalk. Thanks for the note here; you make a really good point regarding how we can better communicate our planned changes/what exactly the roadmap constitutes. We’ve had a few issues lately with users who – because we’ve agreed at one point that a feature does have a place on the roadmap – are falsely led to believe that this means there’s any sense of timetable or timeline associated with that. This was our failure to communicate properly and I apologize to both you and the other users in this same boat.
To us, getting onto the roadmap means a feature is something that – among the hundreds of requests coming at us from all sides – we see value in, enough to log it in our central ticketing repository and to begin taking exploratory steps towards implementation. I will be completely transparent here and say that’s where this feature sits: we have logged it and are continually noting additional requests as they come through. We see value in it and it is indeed one of the two “priority 1” (top level) tickets we’ve got, given the number of requests we’ve had for it. That said there has been no actual code work done on it, beyond a number of discussions on how it could best be implemented; while I think the argument could certainly be made that this isn’t really what the plugin was designed for to begin with – it’s meant to be a light ticketing service, not a full-fledged event management solution – we also realize how important this is to the community and want to implement it.
That said, if we do implement it, we want to do it right. That means on a codebase that is stable and in a way that can carry over across the different plugins in our ticket framework. This needs to be code that is flexible and can support future codebase changes/tweaks to both the core The Events Calendar and WooCommerce itself.
You raise a really good point on the idea of having it as a third-party plugin. If a user were to design something that worked and were willing to share it, we would – pending a quick code review to make sure it was safe to share with the community – absolutely help promote that so users knew they had a solution until we can find a best course of action. Whether someone were to make it as a free plugin on the dot-org repo or something they sold wouldn’t make any difference on that front.
Out of curiosity: what could we have done to better communicate this to you? Is our use of the term “roadmap” too subjective and not specific enough? While we generally don’t plan out specific features more than a release or two in advance, I can see based on your point here that we made need to be more firm regarding what’s being actively considered/planned and what we’ve literally made progress on and have a timeline to release. I’d welcome your thoughts here so we can make this process smoother – and avoid disappointment – for everyone. Apologies in the interim that we let you down.
Hey Paul, I’m concerned that you’re verging on a level of discourse that is unwelcome here on the forums. I’d like to reiterate that we do have standards regarding the tone here on the forums – and comments like your last one, which for some reason appear to knock the plugin for working as it’s advertised, do little in terms of providing constructive feedback.
Thanks for being more respectful going forward!
To that end, I’m shutting down this thread since it does little to further the level of discourse here on the forums. Paul, you are welcome to reach out to me directly via email (rob @ tri.be) if you’d like to discuss this more.
Hey Paul, what exactly do you want from us here? Rest assured that when we do add these features – and I will reiterate, what you’re requesting are new features, not bug fixes – we will communicate that actively to the community so that folks such as yourself know right away. Beyond that I’m not sure what exactly you’re asking for here?
We try to be pretty clear and up front on the plugin’s product page regarding a few of these limitations. To comment on your points directly:
1. No plugin in the ticket framework supports recurring events. We’re working towards this and once we finish rebuilding recurrence we will port it over to the tickets framework. But this is not a simple tweak or something we can simply implement on the fly. We try to be pretty direct about this with bold text on the product page (http://d.pr/i/nt9U), but if you have suggestions on how we could make it clearer please do let me know.
2. This is actually a built-in behavior of the plugin; purchase confirmations are sent to the admin via WooCommerce.
3. Not sure what exactly you mean here, but if users are buying tickets to an event – say, a January 22 event – and the ticket they’re getting via email suggests any date other than January 22, that’s a problem. (Unless, of course, we’re talking about an event in a recurrence pattern…in which case it isn’t going to function since this plugin does not support recurring events).
4. There is actually an attendee list auto-generated via the plugin, which appears on the backend and which you as a site administrator can review/email/export as you see fit 🙂 Let us know if you need help locating that and we’ll point it out directly to you.Paul, there are literally hundreds of other people using WooCommerce Tickets. They’re able to work within the confines of the current plugin architecture, and understand that – as with any plugin – this is an evolving product that will continue to grow and change over time.
Shy of rebuilding the plugin on-demand, what can we do to help make the plugin more meaningful? It sounds like honestly we should just give you a refund so you can go find a solution that better meets your needs.
Hi Suzy! Thanks for your follow-up here. I can understand that you’re getting slower replies than you might hope for (we try to not commit to anything more frequent than 24-hours turnaround time), we’d really appreciate if you would keep questions in existing threads rather than re-posting them separately.
That said: I’m happy to try and help get you sorted here. I just checked out the screenshot – unless I’m mistaken, that image seems to be getting pulled in through something else theme-side. Can you confirm whether or not the same problem occurs in Twenty Thirteen?
If it’s the byproduct of a problem with your template override. Have you checked the example customization we provide in the themer’s guide (https://theeventscalendar.com/support/documentation/events-calendar-themers-guide/#examples)? It specifically focuses on The Events Calendar, but among the examples there you will find PRO-specific instructions for loading custom styles as well. The widget and how it integrates should all be covered there.
Please let me know if we’re still misunderstood as to the end goal here, and thanks again for your patience so far.
Hey Suzy: the team alerted me to your follow-up here, and I’m happy to try and get you sorted best I can. But to be honest…I’m not really sure what you’re asking us to do here? We can totally try to point you in the right direction on the 2.x to 3.x upgrade but ultimately, customizations will need to be redone and that’s not something we can provide individual guidance on.
I will say that regarding the overrides – it sounds like you’re trying to do separate overrides for the free The Events Calendar (core) and Events Calendar PRO (the premium add-on). Could that be the source of confusion here?
Please let me know if we’re misunderstanding what you’re trying to do.
