[Brook]

Excellent! Thanks for sharing the code, it’s simply beautiful.

Please let us know if you ever need anything else. Cheers!

– Brook

[Brook]

Howdy Sengwai,

That portion of things would be handled by a third party plugin. However, depending on what you need that functionality might be built-in to WooCommerce for all product types (including tickets). For example, if you simply wanted to issue a coupon code to your agents/wholesalers, when they checkout with tickets in their cart they can input the coupon code and get the discount. Or if you want specific users to get a discount without codes, you would need to rely on WooCommerce plugin that offers such functionality.

Will that work for you? Please let me know.

Cheers!

– Brook

[Brook]

Excellent! Happy to be of assistance. Thanks for getting back. Ta!

• Brook

[Brook]

Howdy again,

Thank you for clarifying.

That list should be up to date. I just grepped for any new capabilities within Event Tickets and my database, and I am not seeing any.

What sort of capabilities were you hoping to see? RSVPs are not a traditional Custom Post Type like Events, Organizers, or Venues, so they are treated differently. But, we welcome feedback on how you hoped to use it, it might be something we could add in the future.

In the meantime if you are simply trying to prevent RSVPs from working if the user is not logged in, the function is_user_logged_in() might could do the trick.

Does that answer your question perhaps?

Cheers!

– Brook

[Brook]

My pleasure! Here I will answer them one by one:

I’m curious about the update process you refer to when you say manually and simultaneously. You seem to be indicating that to update the core calendar plugin followed by the ticketing plugin could cause issues. So what is best practice? Do I disable current ticketing plugin altogether, then update calendar, then install new ticketing plugin? Or do I update to new ticketing plugin first. Please clarify the steps you recommend since I’m keen to ensure I don’t get problems once I upgrade.

Sorry if I was unclear here. The best method for updating is the usual WordPress way. In your WP Admin click Updates (takes you to example.com/wp-admin/update-core.php), select the plugins you want to update, and click update. The best “order” for updating is to do them all at once. Typically people click “select all” to select everyone of their plugins that has an update available, and they hit update. This does them all at once.

I assume that the fact that the existing ticket sales are stored in woocommerce itself means disabling and deleting existing ticketing plugin will not lead to loss of sales information? Will existing events still show the same amount of unsold tickets when the update is complete?

Updating the plugin, disabling, or even deleting the plugin, does not remove your data. Upgrading from WooCommerce to Event Tickets Plus will also save your data.

I’m wondering if rsvp can somehow be used in lieu of waiting lists? If an event is sold out are people still able to rsvp in version 4 of the plugin?

That’s an interesting usecase. You definitely could use RSVPs this way. RSVPs have a separate stock count than tickets, so even if the actual tickets are sold out RSVPs would continue to be available for people to register. You could even rename the RSVP to waitlist if you wanted, using some fairly minor PHP customizations.

Does that answer all your questions?

• Brook

[Brook]

Thanks for marking the answer correct. I am going to archive this topic since it’s resolved.

Cheers!

– Brook

[Brook]

Howdy Terri,

Just an update. I was unable to open your database. I have tried a number of things but my server keeps crashing when I try to. I believe your version of MySQL is incompatible with my own. I am going to contact Brian and see if he can still open it up and investigate further. I will get back to you on the result.

Thanks very much for your patience! Sorry this is taking longer than I’d like.

• Brook

[Brook]

Howdy Nucreative,

Thanks for being so thorough in detailing the issue. I would love to help you with this.

The Filter Bar on the front end will continue to show any options that are still selected for an event in your calendar. When you delete an option for a field the calendar does not go through your database and delete every mention of that option from the events in your database. The reason is because some people don’t want it to do that, and would be very alaramed at the calendar deleting their data.

However you canedit the events that still have that old option, change their setting, and cause the option to fully disappear from the Filter Bar. To do this select the now defunct option in the Filter Bar and get a list of all events that have that option selected. Edit the event, select a different option, and hit save. Do this for each event. And you’re all set!

Does that all make sense? Will that work for you? Please let me know.

Cheers!

– Brook

[Brook]

Howdy Raul,

I am sorry this is giving you trouble. That is indeed a bug in our calendar, and one we are currently writing a fix for. It looks like it will be included in the next release of Pro. So here in a short bit you will get notified that a new version is released. After downloading the new version of The Events Calendar it you might need to edit the problem event, select the proper date, and hit save. But once you do that it will be working.

Does that all make sense? Will that work for you? Please let me know.

Cheers!

– Brook

[Brook]

Howdy Neal!

Good question. Event Tickets Plus and Events Calendar Pro (the new version of Woo Tickets) is probably what you are looking for. Recurring events with tickets are ideally suited for courses, where a person will signup once for the entire 6 week course and make a single purchase to cover the entire time. You will create one weekly recurring event and tell it to end after 6 weeks, then attach a ticket to the whole thing.

What’s not yet supported by recurring events is when you want people to purchase an individual recurrence (which isn’t typical with “courses”). So say instead of a course you are doing a concert 6 weeks in a row in the same stadium, and you want it setup so that someone can purchase a ticket for only 1 of the 6 weeks. We do not yet support this, but it sounds like that won’t apply to you anyways.

Does that all make sense? Will that work for you? Please let me know.

Cheers!

– Brook

[Brook]

Howdy colewebdev,

Thanks for taking the time to report this. That “error” is actually not much of an error at all, which is why at the top of the validator you will see a big green “This document was successfully checked as well-formed XML!”.

You can see this error in all WordPress feeds, including the calendar. It’s basically a part of WordPress. If you try validating the base WordPress feed you will see the error there too. In order to fix this error WordPress itself will need to be patched. I believe the WordPress devs have no intention of fixing it for a variety of reasons, one of which is that it’s harmless.

So you should be all set. Assuming Constant Contact can import events in the method your are trying, then you are good to go.

Does that all make sense? Does that address your issue? Please let me know.

Cheers!

– Brook

[Brook]

Howdy Timothy,

That is not currently possible. We discussed adding that feature while we were speccing this out, but were not sure how much demand there would be. It is good to know you would be interested. Would you mind making this an official feature request on UserVoice (feature suggestion page for The Events Calendar)? From there we can point anybody else requesting to that page, and thus rank this feature on our roadmap.

Does that answer your question?

Cheers!

– Brook

[Brook]

Howdy Rgaller,

I would love to help you with this. I am not quite sure I follow. Are you referring to a shortcode (which require square brackets [] ) or perhaps a line of CSS (which uses curly braces like that {} )? We have never had a shortcode like that, nor would that make sense as CSS. So I am a bit lost as to what you were doing before that broke now. If you can elaborate, share a screenshot, or anything it will be helpful. Once we’re on the same page I’ll do my best to help.

Cheers!

– Brook

[Brook]

Howdy David,

I would love to help you with this. Based on your description I believe what you are trying to hide is the event details area. You can do that with this CSS:

div#tribe-events-content div#tribe-mobile-container {
display: none;
}

That what you’re looking for?

Cheers!

– Brook

[Brook]

Howdy Jenny,

Thanks for giving that a whirl. I was able to determine the cause of this a short while back, and test out a solution.

The warnings are generated because text was input into the Event Cost field instead of a number. Perhaps you were in 3.11 or under version of the calendar when you added this event, and instead of typing a number into the field text was input instead. Or, sometimes this happens when importing an event via CSV and you set the Event Cost field to a string of text instead of a number.

To fix this you will need to find all events which have text in that field and change them to a number. To do this enmasse you can run some MySQL commands, perhaps from PHPMyAdmin. To get a list of all events which have this issue you could run the following SQL in your WordPress database:

SELECT * FROM wp_postmeta
WHERE
meta_key=’_EventCost’ AND
meta_value!=” AND
concat(”, meta_value * 1) != meta_value

You could then edit them on a case-by-case basis. If you wish to convert many of these at once you can run some SQL update commands. For instance the following will change everywhere that the word “Free” was typed in to the Event Cost field to the number 0, since 0 is treated as free in The Events Calendar.

UPDATE wp_postmeta SET meta_value=’0′
WHERE meta_key=”_EventCost” AND meta_value=”Free”

If you wish to instead remove the cost value from all of the problem events, run this:

UPDATE wp_postmeta SET meta_value=”
WHERE
meta_key=’_EventCost’ AND
meta_value!=” AND
concat(”, meta_value * 1) != meta_value

Please note, there is always some risk with running SQL commands on your database. It is always a good idea to make a database backup before dabbling with your data.

You can avoid MySQL entirely ig you prefer, especially if there are only a few events affected. Just edit those events, scroll down to the cost field, and change it to a number. Hit save, and the event is fixed.

Again I am sorry for the errors. Does that make sense? Please let me know.

• Brook

 

[Author]

Posts