[Brook]

For sure! I will send that to you tomorrow. Thanks again.

– Brook

[Brook]

I can definitely do that. I will take care of that tomorrow.

– Brook

[Brook]

I have not found any solutions. I was able to replicate a similar problem, probably the same one, after a week of trying. I do not know what has changed.

I am logging this as a bug for us to do an ongoing investigation into. I have already consulted with our support team a few times, and every one of us is stumped as to why this is happening. Unfortunately that means that there is no solution for the foreseeable future. We will need to keep collecting reports of this bug, and comparing any commonalities between your website and other websites. This will take time.

I am very sorry that I do not have a solution for you, nor can I tell you when a solution will be available. Typically we are able to isolate bugs very quickly, I have only ever seen one other bug that is this hard to debug.

Let me know if you have any more questions. Thank you again for your test install. I was able to glean a lot of information from logging in and examining your settings. My manager requested that I do not change any settings or data, as that is expressly forbidden for legal reasons. But, even without changing anything I was able to glean enough information to replicate this or a similar problem on my own system.

– Brook

[Brook]

Howdy Pasquale,

I am happy to hear that worked.

Brian is spot on. In simple terms the problem you are facing is a side-effect of how WooCommerce itself handles stock counts. When any product is purchased, whether it be tickets or otherwise, WooCommerce has these statuses for their orders. In your case it sounds like the status is Pending payment. As noted in Woo’s documentation there, orders which are pending payment do not reduce the stock count.

There is good reason for that. For example, if Woo reduced stock counts while payment was pending a malicious person could purchase all tickets from your website with bogus payment information. Thus they could make every single ticket and product appear as out of stock, and prevent you from selling anything or getting paid.

For your specific needs, I am not aware of any upcoming changes to our plugin or WooCommerce that will fix things. Most people in your shoes will charge credit cards upon an order, but then refund those orders if the event is cancelled. This does have some drawbacks, but is the typical way of things and it is how WooCommerce is designed to operate. You might be able to modify this behavior, but I am not enough of an expert on WooCommerce to say, I am only an expert on WooCommerce Tickets. You should consult their documentation and support channels if this is something you are interested in modifying.

Does that all make sense?

Cheers!
– Brook

[Brook]

Excellent, I am so happy to hear that. Ta!

– Brook

[Brook]

Howdy Dawn,

I just want to mention something first of all. That widget actually is responsive. Here is an example on our demo site, you can see it changes sizes from desktop to mobile: http://wpshindig.com/event-widgets/

But, the widget is obviously not responsive on your website. Unfortunately this is due to your chosen theme. The theme defines some general things about tables, one of them is it adds a lot of padding around each table column. This drastically increases the size for a 7 column table like a calendar. It also apparently does some other things to increase the size.

You will need to customize your theme to remove or modulate those CSS rules in your theme if you would like to have a skinnier 7 column table like a calendar widget. Right now your theme simply does not allow for tables like the calendar to be any smaller than they are, thus they are essentially not responsive. This might very well require a theme expert to write some custom code for you, and might take them a while to do. The other option of course is to try a different theme.

I wish there was more I could do. Does the above all make sense though? Do you have any more questions?

Cheers!

– Brook

[Brook]

Thanks for bearing with us Jeff. What you want is definitely possible. It’s actually just a simple theme override, and we have a guide for making those here.

The file you want to override is actually in /the-events-calendar/, not the /wootickets/ folder. Here is the full reference: /wp-content/plugins/the-events-calendar/views/tickets/email.php

That file is the entire HTML email that’s send out and it contains the tickets in it. So you can modify any part of that email by overriding this file as per the guide above.

Does that make sense? Are you able to get it working now? Cheers!
– Brook

[Brook]

Howdy Pasquale,

That’s a good question. We do have one function available that can make half of what you want to do easy enough. That is tribe_events_count_available_tickets(). That allows you to easily show how many tickets are still available.I jsut wrote a second function to complement that one, which will show how many tickets have been sold. Copy/paste the following into your theme’s functions.php file, then you can call the new function tribe_events_count_sold_tickets() just like you would the other funciton to show how many tickets have sold.

https://gist.github.com/elimn/bf36f50c7ca2a4e50c9e

Does that all make sense? Does that work for you?
Cheers!

– Brook

[Brook]

I am sorry, I can not see that link you shared. It is a local link to a file on your computer, so only you can see it while you are on your computer.

I am not sure what is happening. Perhaps the wrong .pot file is being loaded? Regardless I think I can make this easy. This zip file contains the update files. There should be not need to update from sources as I have already done that. Zip: community-3-10-pt-BR

Does that file work?

Cheers!

– Brook

[Brook]

Since the topic answer has now been marked and all questions appear answered I am actually going to archive this topic. Please know that if you do need further assistance though we would be happy  to help. Just open a new topic. Cheers!
– Brook

[Brook]

Hello Luciane,

Thanks for your patience. 🙂 I will do my best to pick up where Jami left off. Typically our support for integrations is just an overview of what you need to do, the specific implementation is up to you. This is in part because integrations usually have many small hiccups along the way, even simple things such as a misnamed variable can be nearly impossible to remotely diagnose.

First of all I would undo the last thing you did, replacing that one line with this one:

<?php comment_form(); ?>

It sounds like that new line is not compatible with your theme. So if you delete it, and paste the old one, you will be right as rain on your blog pages again.

But I do have a couple of ideas. You said that you had enabled comments in Events > Settings > General. But, have you also enabled comments on each Event? When you go to Add or Edit an event, there is a box labeled Discussion. And inside of it is a checkbox to “Allow comments”. Both this and the setting mentioned before must be enabled.

If that does not work, have you tried a different page template in Events > Settings > Display? One of the other page templates might show the comments.

Did either of those work?

Cheers!
– Brook

[Brook]

Thank you Kavi! I submitted a patch with your change just now, so it will be included in verion 3.10 of WooCommerce Tickets. I mentioned your contribution in the credits for that version. 🙂

A few other bits of WooCommerce Tickets do still need translating. If you are interested in helping us with those, download this file: tribe-wootickets-de_DE We also have a guide if you have never done translating before. If you do contribute a full translation we will give you a coupon for a free renewal or for a new product of your choosing.

Thanks! Since the problem in this topic is now fixed I am going to archive the topic. If you would like to fully translate the rest using the above file and guide, please open a new topic to submit your update file. Cheers!
– BRook

[Brook]

Thank you so much Oliver! A few of the translations needed some minor tweaks to compile properly such as changing d% to %d. But I made the tweaks and they are all working great now. We are good to go with these now. 3.10 will include all of those updates. 🙂

If you need a coupon code for another plugin or anything let me know. If not, would you mind marking this resolved? Cheers!

– Brook

[Brook]

Howdy again Luciane,

Your link does appear to contain the latest pot file. When I open up pt_BR in Poedit, then on my Windows PC I mouse over the Catalog menu and click “Update from POT file…” When that happens I will see those strings in need of translation as pictured here. With that completed it is ready for translation. 🙂

You can definitely get another year added. No worries there. Let me know if you need anything else. Thanks for offering to do the translation!

– Brook

[Brook]

Howdy Lars,

I see what you mean. One of our translators was kind enough to submit an updated and fixed file for our next release. That will be fixed in 3.10.

I appreciate your taking the time to both report this and mark the topic resolved! It’s worth mentioning that our translation forums are not for support, and thus do not usually get checked daily like the rest of our forums. Hence the delayed response.

Thanks again!

– Brook

[Author]

Posts