Forum Replies Created
-
Posts
-
Hi James. Thanks for the note here! I should say upfront that we don’t have dedicated multisite integration, to the extent that content from sub-site A, B and C cannot filter back to the main network site or vice versa. But so long as you’re cool with that: a developer license should do the trick for you.
We are working on dedicated multisite licensing, but that hasn’t quite been finalized so it’s not ready. If you go to developer we can upgrade you appropriately once that debuts.
Hope this helps. Let me know if it didn’t, or if you have other questions I can help out with. Thanks again!
Hey Ed. Thanks for the follow-up (and for your interest as well). I’m not following what you’re going for here; are you envisioning doing this through template tags, or actually creating an events template that is called in certain circumstances?
Hey there Marlies! Thanks for your note, and for your interest in checking out the plugin. Happy to answer your questions here best I can.
Regarding the random recurrence patterns: as it stands we do have a number of custom recurrence options, and they can allow you to create pretty unique / one-off schedules; but they don’t allow complete random recurrence. This video gives an overview of how it behaves: https://theeventscalendar.com/test-video/. It’s sort of old, as it was recorded for the release of 2.0, but our custom recurrence really hasn’t changed at all for 3.0 so the information presented here still rings true (even if the page aesthetics are a bit different). We are indeed looking for a way to add more truly random recurrence options for the 3.0 lifecycle as well…however those probably won’t be included in the initial 3.0 build.
When it comes to registration: no built in registration component at the moment (though we’ve had a ton of requests for it and will probably end up building something later on). At this point it does require either WooTickets or Eventbrite Tickets to be done effectively.
Hope that helps! If you have other questions, or if I missed anything here, please let me know and I’ll follow-up as needed. Cheers.
Hey there AdrianTO. Thanks for your note, and your interest. To answer your question here: yes, tickets you add as WooTickets within The Events Calendar are set up as products. They will not appear in the frontend cart by default, though.
I’m not sure about the element of adding the items to your cart, largely because that would be a WooCommerce function (our plugin just taps into WooCommerce and makes use of its code to sell tickets). I would bet that if you found a way to make this work for regular products using WooCommerce, though, there shouldn’t be any reason why it wouldn’t work for WooTickets. And if you bought and found it DIDN’T work in WooTickets (despite working fine in WooCommerce), we’d certainly be happy to give you a refund as desired.
Hope that helps. Please let me know if it didn’t, or if you have other questions. Cheers!
Hey Kassie. Thanks for the note, and for your interest in the plugin. This is a really solid idea…unfortunately at the moment we don’t have anything built in that allows for this. I suppose you could find a way to “fake it” using a ticketing add-on, but that seems like it’d be awkward and might not have the desired effect anyway.
That said: we were working on a Conference Manager add-on last year, which we put in the backburner as we finalized Events 3.0 but will likely be resuming sometime this year. When and if that is released, it will accomplish pretty much exactly what you’re going for. I’ll put out a public call for beta testers if we proceed down that route…and you’re naturally welcome to participate if so.
Hope that helps and sorry I couldn’t offer more in the interim. If you’ve got other questions here, or if something I said doesn’t make sense, please let me know and I’ll adjust my reply. Thanks!
Hey there L. Thanks for the note here, and for your interest in our plugins! There aren’t any built-in payment options for the plugin, at this time. Instead we rely on these add-on plugins that each have their own method of handling purchases.
We’ve got two add-ons related to ticketing: Eventbrite Tickets and WooTickets. Eventbrite Tickets handles all payment processing through Eventbrite; this means it’ll work with Paypal or Google Checkout. WooTickets integrates with WooCommerce for payment processing. Out of the box that means Paypal will work, but I know WooCommerce has a number of additional payment gateway add-ons themselves (ie Stripe integration) too.
All that to say: you do have a few options. But none of them are specific to the core calendar, and they will require a ticketing component to work.
That help? Let me know if not, and I can adjust my reply as needed. Thanks again for your interest!
Mike, if you happen to see this…it looks like Matt could benefit from your knowledge! (I just killed the couple of SPAM comments that had made it into this thread, as well).
Hey Matt. Thanks for the follow-up here. Leah’s out this week but I wanted to let you know that we did see this and are taking it into account as we continue these discussions. As our setup stands now you would unfortunately have to pay $250 for the 10 site access tier. While the intent with our unlimited pricing schema is definitely to make per site cost cheaper as the # of sites goes up, I can’t guarantee we’ll be adjusting it in such a way that dev license goes for under $150 for 10 sites. We hope users who are considering a purchase will take into account the idea that you aren’t just paying for the code itself, but also support access for anyone using any of the sites you’re running on (and updates to the plugin on a consistent, usually monthly, basis).
I hope this helps — and if it doesn’t, let me know so I can adjust my response. Otherwise as soon as we’ve got this new pricing scheme established you guys will be the first to know.
Hey Jeff. Sorry to mislead you on the earlier message: in 3.0, there will be a defined URL dropdown. As it stands, in 2.x, you’ll want to take two steps to “fake it”:
1. Configure your Additional Fields like so: http://d.pr/i/32nm.
2. When creating the event, add the hyperlink in HTML: http://d.pr/i/Jm8e.
3. Review on frontend and see it worked: http://d.pr/i/2e3m.Hope that helps and apologies once more for the confusion. Let me know if I can elaborate here or if you have other questions.
Hey Benjamin. Thanks for the note here, and for your words on the plugin. Awesome to hear it has piqued your interest. To address these points:
1. You can definitely set additional fields with the PRO release. You’d actually create a new additional field (in the plugin settings) for “Due Date” or whatever, and would be able to enter that date (in a text input) when configuring the events.
2. Not at this point, unfortunately. But that feature is coming with the 3.0 release we’re releasing soon and have been previewing at https://theeventscalendar.com/events-3-0-preview/.
3. This, too, is on the docket for 3.0 but hasn’t been released in any of the 2.x builds. I actually put out a video preview showing what’s in store for map view the other day. Check it out: https://theeventscalendar.com/the-events-calendar-3-0-preview-map-view/.Hope that helps! If you have other questions, or if I can elaborate at all, let me know. Similarly if you’re interested in trying out the 3.0 beta…we can probably make that happen 🙂 Cheers.
J-P: thank you for taking the time to reply to my last response…I hope it added some value for you, and I really appreciate getting a glimpse into your thought process here. This helps me make a case for this to the team and I’ve relayed it accordingly so we can keep the discussions going here.
We’ll keep you guys posted. And if you need anything else from me at any point along the way, please do reach out to the email address I provided above. Thanks again!
Hey guys. Thanks for the feedback here; Barry passed this along my way and I wanted to respond to give you an “official” overview of where we are with this and why you don’t see attendee names as an option on the current release. Right off the bat let me say thank you for the feedback and for making clear this is something you see value in. We appreciate your feedback and are listening to it: there are a number of high-level discussions going on within the team right now, all related to feedback we received here on the forum, which will drive the future of the product. I did want to clarify some confusion here, though…because when I see terms like “this should be a priority to fix,” it raises a bit of a red flag in my mind as this is by no means a bug. The current functionality is by design and exists as a reminder of this plugin’s purpose: a simple ticketing tool, not a full-fledged events management system.
Since the launch of WooTickets, we’ve had requests for attendee names per-ticket and are looking at the best way to implement it now. We’ve got some more pressing changes to the plugin (an updated/more usable attendee list, and move to an entirely new and more flexible format for the PDF tickets) coming first but this is something that we’ve got on the radar and are actively discussing.
We shipped 1.0 without this functionality for a few reasons. Mainly, as I noted above, our intent was never to make a complete event management solution. (If we did it’d be a much more feature-rich plugin that would unfortunately have to cost substantially more). Instead it is merely a tool for frontend users to buy tickets to events, and for site admins to keep track of who those tickets went to. The idea of different names for attendees is cool, but is tricky since it also verges on being more high-level event management. When I buy a ticket through a web-based ticketing solution like Ticketmaster, I’m not presented with an option to set specific attendee names: I buy the tickets, and can do with them what I wish. But as far as the ticket service and venue are concerned, the tickets I bought are mine (even if technically they’re going to be used by myself, my wife, my cousin, etc…the venue doesn’t really care about this). That was our reasoning as we looked to industry standards with releasing this plugin.
That said, based on user feedback we are definitely looking into what it’d take to implement this. It may not be immediate but it’s one of our more commonly-mentioned feature requests and we want to meet demand in a way that serves your needs, makes sense and is flexible with both The Events Calendar and WooCommerce (the latter of which we tap into heavily for the WooTickets plugin).
All that to say…know that we are listening. I hope this helps and sheds some light on the situation. If it doesn’t make sense, or if you have other questions / comments / complaints, my “door” is always open. Please don’t hesitate to send an email to rob /a/ tri.be and I’ll respond directly from there. Thanks, too, for your support and continued use of The Events Calendar.
We’re actually postponing this. It’ll still happen, but at a yet-to-be-determined later date. Let us know if anyone is still interested and flexible enough to commit. Cheers!
Hey Andrea. That’s odd; can you email your credentials for the site to us, pro /a/ tri.be, and we can check this out for you? Sounds like something is amiss here and I want to make sure we get it sorted as soon as possible. Thanks for your patience on it so far.
