Forum Replies Created
-
AuthorPosts
-
Geoff
MemberHey Jamie and thanks for following up!
Are you saying the Events Calendar Pro version would still not allow you to add additional fields on the booking?
Unfortunately, no. The additional fields are purely for you on the back-end to display information about the event on the front-end. Any additional fields collecting during checkout would need to be collected by the eCommerce plugin which, in this case, would be WooCommerce. Even then, that information would have to be hooked into events somehow, which can get tricky.
The good news is that we have started working on the ability to do exactly this and are currently starting the testing period for it. I don’t have a firm release date for you, but we are expecting it in a matter of weeks rather than months, if all goes well in testing.
I hope this helps–did you have any other questions about how the ticket process works that I can help with? Let me know know and I’d be happy to answer as best I can. ๐
@Brian, thanks for reaching out as well. We do have aย new user primer specifically for WooCommerce Tickets. Give that a go and please feel free to open a new thread of your own here in the forums if you have any questions from there.
Cheers!
GeoffGeoff
MemberYou’re the genius for making it work! Thanks for following up and letting me know it worked–I’m so glad all is working smoothly. ๐
Geoff
Geoff
MemberHey there, PG!
Shoot, sorry that doesn’t quite do the trick. Unfortunately, there is no way to selectively choose to hide the information from events. In other words, all settings are global and cover them all.
You could take an approach of targeting the CSS snippet to specific events. Then again, that would be quite a hassle to manage in the long term.
Sorry I don’t have a concrete solution for you here. One thing you mentioned was the idea of a shortcode and–while I’m not quite sure how that would work–we are in the thick of thinking about how shortcodes on The Events Calendar can and should work outside of the ones we already have. If you have a moment, I’d really appreciate you sharing your idea on the feature request for shortcodes so we have more input on how what that should look like.
Do you have any other questions about meta boxes? Let me know and I’d be happy to help as best I can.
Thanks,
GeoffOctober 23, 2015 at 7:02 am in reply to: Removal of fields from "Add Event" page – on the front end and the back end… #1017237Geoff
MemberHey there, Marc!
Awesome, I’m so glad that worked. ๐
Shoot, I’m actually not aware of how to change the field labels without touching core code, which I really wouldn’t recommend. Sorry about that!
I’m going to go ahead and close this thread since we’ve gotten pretty past the subject of the original question. If you still have any questions, though, please do open up a new thread and we’d be happy to help you there as best we can.
Cheers!
GeoffGeoff
MemberHelloย Tomasz and thanks for getting in touch!
You’re right: the setting you mentioned will only have an impact on the main posts query if that query is on the homepage.
You can, however, add snippets to add events to your other queries as well. ย For example, here is a way to add events to anywhere the main query is called in your templates:
add_action( ‘pre_get_posts’, events_in_main_query’ );
function events_in_main_query( $query ) {if ( ย $query->is_main_query() ) {
$query->set( ‘post_type’, array( ‘post’, ‘tribe_events’) ); return $query;
}}
You can use that as a model for modifying other existing queries, or wrap it in a conditional statement that targets specific templates or pages.
Does this help? Please let me know. ๐
Cheers!
GeoffGeoff
MemberThat’s interesting! I actually wonder if the two are connected in some way.
Let’s first try flushing permalinks without changing the URL structure. In other words, head to Settings > Permalinks and simply hit the Save button. That won’t change the settings, but will flush things out.
Then try the other steps from there and let’s see what we find.
Thanks!
GeoffGeoff
MemberHi Judy,
Sorry, it doesn’t look like the forum thread you mentioned was linked but I’d be happy to look at it if you want to send it over.
In the meantime, I noticed that the snippet you shared makes a call for the category slugs, but it appears the category names are used instead. So, for example, a category with the name “Investment Reseach” would likely have a slug ofย investment-research. Try checking the URL slugs for your categories and replacing them in the snippet accordingly to see if that makes a difference.
Thanks!
GeoffGeoff
MemberMy pleasure and thanks for following up!
Geoff
MemberOh, gotcha! Thanks for clarifying.
Yeah, that’s possible for sure. Add this to your theme’sย style.css file and it should do the trick:
#tribe-events-content form, .tribe-events-event-meta { display: none; }Thanks!
GeoffGeoff
MemberHi Paul,
Good question. There is no way to hide those areas in the event editor right out of the box without touching core code. However, I wonder if using Advanced Custom Fields might help here, since it provides the ability to hide fields from the post editor and supports custom post types. Definitely worth a look.
Would that possibly work? Let me know and I’d be happy to answer any other questions about hiding those fields as best I can. ๐
Thanks!
GeoffGeoff
MemberRock on, so glad that helped! Thanks for following up and letting me know. ๐
Geoff
MemberAwesome! Thanks for following up and confirming everything. So glad this helped out. ๐
October 22, 2015 at 8:39 am in reply to: Need to know features available in PRO before purchase #1016935Geoff
MemberHi Renee and thanks for getting in touch! I’m stoked you’re looking at PRO and I hope it’s a solid fit for you. ๐
Here’s a screenshot of a customized Upcoming Events List Widget that displays both the featured image and the excerpt.
And, here’s another one of the options you have on the back end to modify the widget right out of the box.
Does this help show you what you’re looking for? Please let me know. ๐
Cheers!
GeoffGeoff
MemberHey Ian,
Good question. I have note used any bulk discount plugins with WooCommerce Tickets and am not sure which one you’re trying, but this one might do the trick:
We do offer a full refund on purchases within 30 days, so if bulk discounts don’t seem to be compatible with the plugin and you’d like to return it, you would totally be able to.
Give that a shot and let me know if you have any other questions about ticket discounts–I’d be happy to help as best I can.
Cheers!
GeoffGeoff
MemberHey Ian! See you asked the same question over here in another thread. I’ll go ahead and close this one out and see you there. ๐
Cheers!
Geoff -
AuthorPosts
