loushou

Hey @bradleysp, this does appear to be a bug. I will investigate it and get back to you.

Loushou

Hi @bradleysp (Simon). This sounds like a bug. I will do some research and get back to you.

Loushou

No Documentation: Currently code documentation is sparse, yes. We are working on that.

No Customization: There are many aspects of this plugin that can be customized. If you find that you need to customize something that we have not thought you might, then simply request it, or fork us on github and do a pull request https://github.com/quadshot/opentickets/tree/master .

No Internationalization: We are working on this too.

I hope that we can turn your down vote into an up vote by continuing to act fast and adapt to our new user base on www.ads-software.com. Please keep an eye out for updates that include fixes for these.

Loushou

Awesome! Glad to hear it, and glad I could help!

Loushou

I found another thing that could cause this problem. If you got your version of WooCommerce from github.com by clicking the ‘download zip’ link on the right side column, that zip file contains a non-standard woocommerce plugin folder name. This non-standard name could also be causing this error to pop. For examle, if you download the ‘master’ branch from github using the zip file link I described, then your plugin will be installed at:

/wp-content/plugins/woocommerce-master/

causing the actually plugin bootstrap file to have the name:

/wp-content/plugins/woocommerce-master/woocommerce.php

Our plugin does not currently look for these non-standard plugin folder paths, but will probably do so in a future release now that I know this is a possible way to pop the message. We currently only look for:

/wp-content/plugins/woocommerce/woocommerce.php

The easiest way to solve this problem is to not use the zip downloaded from github, and instead use the WP plugin search feature in your plugin admin page, and install the version they have on www.ads-software.com instead.

Hope this helps,
Loushou

Hey Robert. I was able to see the ‘double reduction’ issue you reported in my environment. A patch has been grouped in the latest release, 1.5.2, to repair that issue.

As for the ‘Check’ payment type having the same issue as the ‘BACS’ payment type, I was not able to reproduce that. It is possible that I may not be using the same payment method though. I was looking through the core payment methods that come with WooCommerce, and I don’t see one named ‘Check’. Because of this, I thought you may be referring to the ‘Cheque’ payment type. My testing used Cheque. If this is not the payment type you were using, then let me know the official name of the payment plugin you are using from the WooCommerce website, and I will see if I can test with that instead.

Your report of this payment method problem did however lead to finding another location where the ticket link was available before it should be, the My Account page. I added a patch preventing that link from appearing on non-completed orders also.

Let me know if this patch solves your issues, and again thanks for reporting them!

Loushou

Hey Robert. Thanks for reporting this. It does sound like a bug. I will do some more investigation into this and get back to you on it.

Thanks again,
Loushou

You are correct bradleysp. In OpenTickets Community Edition, only one price can be assigned to a given event. The seating extension will cover that once it is ready for sale. As of now, only general admission, single ticket price events are possible. Just a reminder, you can sign up for our mailing list on the website to receive notifications when it does become available.

Robert Trevellyan is correct. The ability is built in, and there is no option to turn it on or off. When you click the link in your confirmation email to view your ticket, You can print it from there, or click the link at the top of the ticket to download the pdf. Also as Robert says, there are also links to your tickets on your my account page.

That message is designed to only show if the /wp-content/plugins/woocommerce/woocommerce.php file is not in the ‘active_plugins’ list. Generally speaking that means that the WooCoomerce plugin is not active, which is different from being installed.

My gut instincts are saying that you may have ‘installed’ WooCoomerce, but the plugin may not be ‘active’. Visit your plugins page, and try to ‘activate’ the WooCoomerce if it is deactivated. Even if you are sure about this without looking, double checking only takes seconds, so you may as well.

If that is not the problem, then try deactivating _both_ OpenTickets Community Edition and WooCommerce. Once they are both deactivated at the same time, then reactivate them both, in any order. This will reinitialize any installation steps that could be causing the plugins to not recognize each other.

If you are still having problems, try removing and reinstalling both plugins from www.ads-software.com. Sometimes the installation process may get interrupted, for one reason or another, and cause some initializations to not take place. This should rule that out.

If you are still having problems, then try deactivating all of your other plugins one at a time. If the message goes away after a specific plugin is deactivated, then it is probably causing some sort of conflict, and should be reported here ASAP, so that we can improve compatibility for it.

If none of these steps help, then maybe you and I can hook up, and I can get some sort of access to the installation, and help track this issue down. Or if that is not an option, then we can exchange a comprehensive list of plugins and themes that you are using so that I can setup an identical site on my server, and test out the issue. One thing we really care about is compatibility, so any issues like this should be investigated as soon as they crop up.

Let me know if any of this helps,
Loushou

@dolliv – the most recent release 1.5.1 fixes this issue. Thanks for your help identifying it.

This is an excellent tip.

Hey Christan,

In our recent 1.5.x release, we have included this as a feature. Now if you edit the ‘event calendar’ page in the admin, you will see a metabox below the ‘page attributes’ metabox, labeled ‘Calendar Settings’. You can choose from three options: open the calendar to today’s date, open it to the date of the next published event, or specify the date that you want it to open to. Hopefully this will resolve the issue.

Loushou

Alright. A patch has been applied. Update to 1.5.1. That should resolve the problem immediately. If it is not immediately resolved, simply deactivate and reactivate the OpenTickets Community Plugin after updating, and it will be.

Loushou

Hey there guys,

We released the changes required for the new WooCommerce update. Since then I have tested the issue you are reporting, and I am able to reproduce it on my environment. A patch for this is currently in the works.

Loushou