Forum Replies Created
-
Posts
-
Howdy Martin,
Excellent. I could see how that would not be intuitive. I appreciate the feedback on this.
It is certainly possible to automatically complete those orders. This was actually a common enough request that it graduated from being a snippet to an option in our plugin. If you go to WP-Admin > Events > Settings > Tickets and check the box “Try to set the status of new ticket orders to “complete” automatically” it should do what you want. Does it?
Cheers!
– Brook
Howdy Lars,
I would love to help you with this.
If you are content with just using some CSS to hide that intro test this will be very easy. This CSS will hide it just from the single page:
.single-tribe_events .tribe-events-before-html { display: none; }You could either insert that into your theme’s CSS, or use a plugin like Simple CSS to insert it.
If you wish to fully remove this rather than hiding it though you will need to do a little custom coding. If you override the filter ‘tribe_events_before_html’ to be an empty string when is_single() is trule, then you should be all set.
Does that all make sense? Will that work for you? Please let me know.
Cheers!
– Brook
Howdy David,
I would love to help you with this.
I wonder if this might relate to your theme. Some themes were designed for an older version of The Events Calendar before Attendee Fields were a feature, and need to be updated to support this. Could you try temporarily switching to Twenty Sixteen theme and seeing if the fields popup?
- If they do popup, are there any updates available for your theme? If not you might need to contact the theme author and inquire about when those updates will be available.
- If the fields are still missing in Twenty Sixteen, could you link me to one of the events where you have added these fields, and yet they are missing? Would you mind also grabbing your system information and pasting it here? Make sure to use the ‘Set as private reply’ checkbox to protect your private information from the public.
Cheers!
– Brook
Howdy Martin,
Good question. The tickets themselves actually are part of the products post type, hence why you cannot attach to them.
However that might make things somewhat easy for you. All tickets are already within the WooCommerce shopping cart, but they all have their visibilty set to hidden in Woo. You can change this by bulk editing them from the products page. Further you can make it so that new tickets default to visible instead of hidden by adding this snippet to your site, such as in your functions.php file:
https://gist.github.com/jesseeproductions/5768685acc4cd48cdd81
Does that do what you wanted? Or were you hoping for something different? Were you hoping to have a seperate product page for each ticket or do you like how it links to the events when you select a ticket in Woo?
Cheers!
– Brook
Howdy Robert,
We would definitely like to help you with that. Would you mind opening a new topic dedicated to your issue? In particular if you will share you would share your system information that would be very helpful in this case. You can find the system info by going to WP Admin > Events > Settings, clicking on the “Help” tab, and scrolling down to the ‘System Information’ box.
Reine, sorry if I was unclear. I was saying you should put all of this CSS in your child themes CSS file. There is no need to mess with the tribe events CSS unless you really want to, but that just complicates things on your end if you do.
4. Moving on, is the suggestion of #tribe-events-bar { width:100%; } meant as an alternative to above and if so, do you mean to add it directly to the CSS in the vantage-child theme or tribe-events CSS?
Exactly. That CSS I shared will prevent you from needing to create a theme override. Even if you did create a theme override you will still need to run the CSS I shared, so there really is no need for an override at all.
I’m concerned if I simply change the font of “h2” in the vantage-child theme, I’ll be changing the font of h2 everywhere. I did try adding this to the vantage-child theme but wasn’t successful.
For sure. You can just create a very specific CSS rule to adjust that heading instead of affecting h2s everywhere. This one ought to do it:
.entry-content h2.tribe-events-page-title { font-family: arial; }Again put that in your theme’s CSS file.
Is all that starting to make more sense?
Cheers!
– Brook
Howdy Martine,
I would love to help you with this.
If your goal is to simply hide the Tickets stocks then a little bit of CSS could get you there:
span.tribe-tickets-remaining { display: none; } Similarly to style the + and Minus buttons you could do something like this:.woocommerce .quantity input.plus, .woocommerce .quantity input.minus {
background-color: rgba(225, 20, 36, 0.75);
border: none;
}`Finally hiding the Google/iCal links:
.tribe-events-cal-links { display: none; }However if you wish to completely remove things from the front end instead of just hiding, such as the Stock count, you will need to create an override. Our Themer’s Guide walk you through this process.
Does that help get you to where you want to be?
Cheers!
– Brook
Howdy ,
I would love to help you with this.
This is actually quite easy to do selectively, no coding skills required. 🙂 The steps:
- Edit the event in questions
- Hover over the ticket on the edit page, click “Edit in WooCommerce”
- On the right hand side of the page you will see “Catalog visibility: Hidden” and right next to that you will see the option to Edit. Click that and change the visibility, then hit Update.
And there you go! Do this for any ticket you wish to show up in the store.
Does that all make sense? Will that work for you? Please let me know.
Cheers!
– Brook
I think I understand now. I really appreciate your detailing everything for me.
I actually don’t think you will need any theme overrides to do this. You have already selected the proper template in your settings, now the only thing left is to make your theme’s content container full width. A dash of CSS will do this on the Month, List, and Single event views:
.full-container #primary { float: none; width: 100%; }My other quest was to change the font and sizes for the headings in the events calendar. For my website I use a heading type called “Satisfy” which the events calendar picked up (I would guess as directed). I wanted to override the inherit code to change the titles to a sans-serif. The odd thing is I could do this through Inspect Element but I couldn’t find the file to make a permanent change. I believe I went through these files – removing any changes I made if it didn’t work. There were a number of css files, and I realize I should have asked which one I should use.
If I were you I would not even both overriding those CSS files. The CSS files tend to recieve changes frequently. Everytime we update those in the plugin and you update, suddenly the CSS files you have in your theme are out of date. This usually does not cause a big problem, but maybe some minor oddities here and there.
Rather if I were you I would just insert CSS into your child theme like the above. If you are trying to override a rule like this:
#tribe-events-bar { width:100%; }Then create a new rule in your CSS file that is more specific and it will take effect instead:
div#tribe-events-bar { width:100%; }Simply adding the div element there made this rule more specific and now it takes precedence. No need to override our CSS files and thus no need to integrate their updates into your CSS each time you update the plugin.
Does that sound like it would work? Is that the route you would prefer to go now?
Cheers!
– Brook
You are very welcome. Wish I could be more specific instead of pointing you away. I will this topic open just in case you have any more questions relating to this once you talk to them. Cheers!
– Brook
It was my pleasure! Thanks for getting back.
We do our best to have fast response times! But to be honest it was also a slow night for us so that helps. 🙂
Cheers!
– Brook
Howdy again Fred!
This get a bit more complicated. With just CSS you can override the stretching, but then the image will get cropped instead. See:
#tribe-events-content.tribe-events-single .cmsmasters_single_event_inner .cmsmasters_single_event_img .tribe-events-event-image img{ width:auto; height:auto; }In order to do more than this you will need to modify your theme’s templates. Your theme is explicitly setup to make all event featured images a certain size. Any image that’s not the size will either need to be stretched or cropped. If you are pretty versed in CSS and have a little bit of theming knowhow you can adjust this using a theme override (Themer’s Guide ) Your theme already has these overrides in place so all you will need to is modify them. However since I am not familiar with your theme I can not be more specific than that here.
Hopefully that helps get you pointed in the right direction here, and help you choose which of the available options if any you’re interested in. Please let me know if you have any questions. Cheers!
– Brook
Howdy Adage,
Josh is out this week but I would love to help you with this in the interim.
A- Create a new page for all “Restaurants” venues
If you are most comfortable creating these taxonomies with that plugin Custom Post UI you might checkout the paid version Custom Post UI Extended, which promises to help you display the taxonomies you’ve created. I am not very familiar with this plugin or how well it works with The Events Calendar though.
If you rather a different route Josh’s suggestion of using register taxonomy() is a good route but does require a bit of coding knowhow. However as you will note it allows you to select a slug (url) for the tax to be displayed in, all without needing to but a separate plugin.
B- Add a filter to the events calendar filter bar to may be able to load only events that would take place in one or the other venue categories : for instance, limit the results to the events in Restaurants.
Using a setup like this you can both register a taxonomy and filter with the Filter Bar:
https://gist.github.com/niconerd/cfed2d119cba033d2a4314b215f0ffe8#file-custom_taxonomy_filter-php
Again it will require a decent measure of coding to adapt this to your site, but that is a very solid example of what you’re after.
Does that answer your questions?
Cheers!
– Brook
Howdy Fred,
I would love to help you with this. That’s definitely an issue between your theme and WooCommerce, but that does not mean there is no solution. Have you ever added any CSS to your themes files before? If so it’s just a little dash of that. Add this CSS:
.woocommerce .quantity input.qty{ width:8em; }And you will notice the amount picker is now wide enough to actually show the numbers. Did that do what you wanted?
If you have never added CSS before you might try using Simple Custom CSS.
Does that all make sense? Will that work for you? Please let me know.
Cheers!
– Brook
